- 31 Jan, 2012 3 commits
-
-
Ping Cheng authored
And add two new data formats. Tested-by:
Chris Bagwell <chris@cnpbagwell.com> Reviewed-by:
Ping Cheng <pingc@wacom.com> Signed-off-by:
Dmitry Torokhov <dtor@mail.ru>
-
Ping Cheng authored
Tested-by:
-
Masanari Iida authored
Correct spelling "connetced" to "connected" in pcf8574_keypad description in drivers/input/misc/Kconfig. Signed-off-by:
Masanari Iida <standby24x7@gmail.com> Signed-off-by:
-
- 23 Jan, 2012 7 commits
-
-
Rakesh Iyer authored
Enable keypress interrupt to support wakeup from low power state. Signed-off-by:
Rakesh Iyer <riyer@nvidia.com> Signed-off-by:
-
Rakesh Iyer authored
Add support for Tegra30 by correcting definitions. This is necessary to make driver useful in Tegra30. Signed-off-by:
Stephen Warren: <swarren@nvidia.com> Signed-off-by:
-
Mark Brown authored
We don't actually care if the device has been runtime suspended immediately so we can just drop the reference without waiting for any state change to be implemented. This may allow us to avoid some suspend/resume cycles and is a bit more friendly to the rest of the system. Signed-off-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by:
-
Dmitry Torokhov authored
Convert the driver to standard spilt model arch-specific code registers platform device to which driver code can bind later. Also request IRQ immediately upon binding to the device instead of doing this when serio port is being opened. Acked-by:
Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by:
-
Dmitry Torokhov authored
Convert driver to use dev_pm_ops instead of legacy PM infrastructure. Also make 'open' a bool since it is really a boolean. Signed-off-by: -
Dmitry Torokhov authored
Also proper guard for system suspend/resume methods is CONFIG_PM_SLEEP, not CONFIG_PM. Acked-by:
Linus Walleij <linus.walleij@linaro.org> Signed-off-by:
-
Dmitry Torokhov authored
Because we are using platform_device_probe() to register the driver we do not need to assign driver's probe method. We also can mark ske_keypad_probe(), together with ske_keypad_chip_init(), as __init instead of __devinit. Acked-by:
-
- 05 Jan, 2012 7 commits
-
-
Naga Radhesh authored
This adds two missing kerneldoc entries for the TC3589x keypad driver. Signed-off-by:
Naga Radhesh <naga.radheshy@stericsson.com> Reviewed-by:
Srinidhi Kasagar <srinidhi.kasagar@stericsson.com> Signed-off-by:
-
Dmitry Torokhov authored
Acked-by:
Marek Vasut <marek.vasut@gmail.com> Signed-off-by:
-
Dmitry Torokhov authored
Instead of manually create and handler kernel thread switch to threaded IRQ and let kernel IRQ core manage thread for us. Acked-by:
-
Dmitry Torokhov authored
Let compiler figure out which ones makes most sense to inline. Acked-by:
-
Dmitry Torokhov authored
Add __devinit/__devexit sections annotations so parts of code could be discarded after completing driver initialization. Acked-by:
-
Dmitry Torokhov authored
So that it has proper symlink to the containing module in sysfs. Acked-by:
-
Dmitry Torokhov authored
Instead of using legacy PM interfaces switch to using dev_pm_ops. Acked-by:
-
- 30 Dec, 2011 8 commits
-
-
Dmitry Torokhov authored
Several protocol initialization routines can fail after they set up psmouse methods, such as reconnect and disconnect. This may lead to these stale methods used with different protocol that they were intended to be used for and may cause unpredictavle behavior and/or crashes. Make sure we start with a clean slate before executing each and every protocol detection and/or initialization routine. Reported-by:
Paul Fox <pgf@laptop.org> Acked-by:
Tai-hwa Liang <avatar@sentelic.com> Acked-by:
-
Dima Zavin authored
If there is a full packet in the buffer, and we overflow that buffer right after checking for that condition, it would have been possible for us to block indefinitely (rather, until the next full packet) even if the file was marked as O_NONBLOCK. Cc: Jeff Brown <jeffbrown@android.com> Signed-off-by:
Dima Zavin <dima@android.com> Signed-off-by:
-
Dima Zavin authored
Signed-off-by:
-
Dima Zavin authored
Without this, it was possible for the reader to get ahead of packet_head. If the input device generated a partial packet *right* after the reader got ahead, then we can get into a situation where the device is marked readable, but read always returns 0 until the next packet is finished (i.e a SYN is generated by the input driver). This situation can also happen if we overflow the buffer while a reader is trying to read an event out. Signed-off-by:
-
Jianchun Bian authored
This patch adds a driver for PIXCIR's I2C connected touchscreens. Signed-off-by:
Jianchun <jcbian@pixcir.com.cn> Acked-by:
Henrik Rydberg <rydberg@euromail.se> Signed-off-by:
-
Mark Brown authored
When runtime power management is enabled put the Samsung keypad driver into suspend mode with wakeups disabled whenever the device is open but a key is not actually been pressed. As well as saving a trivial amount of power this will support the use of SoC wide idle modes which put the entire device into a retention mode and use explicit wakeup sources to exit. Since not all of the interrupt controllers used with the driver support set_irq_wake() (though they all do the right thing) and there's a nasty WARN() when we disable wake after failing to enable it keep track of the current wake status from runtime PM and only disable wake if we managed to enable it; I'm not entirely sure why this doesn't affect the existing uses of the API in the driver. System suspend is unaffected as the driver core will runtime resume any suspended devices prior to system suspend. Signed-off-by:
-
Rakesh Iyer authored
Tegra kbc cannot detect exact keypress causing wakeup in interrupt mode. Allow wakeup keypress to be reported for certain platforms. Signed-off-by:
-
Olof Johansson authored
This adds a simple device tree binding to the tegra keyboard controller. Also, mark the default keymap as __devinitdata since it is not referenced after boot. Signed-off-by:
Olof Johansson <olof@lixom.net> Signed-off-by:
-
- 28 Dec, 2011 1 commit
-
-
Heiko Stübner authored
Some displays from AUO have a so called in-cell touchscreen, meaning it is built directly into the display unit. Touchdata is gathered through PIXCIR Tango-ICs and processed in an Atmel ATmega168P with custom firmware. Communication between the host system and ATmega is done via I2C. Devices using this touch solution include the Dell Streak5 and the family of Qisda ebook readers. The driver reports single- and multi-touch events including touch area values. Signed-off-by:
Heiko Stuebner <heiko@sntech.de> Signed-off-by:
-
- 24 Dec, 2011 3 commits
-
-
Heikki Krogerus authored
This will improve the output of the sensor. Signed-off-by:
Heikki Krogerus <heikki.krogerus@linux.intel.com> Signed-off-by:
Kirill A. Shutemov <kirill.shutemov@linux.intel.com> Signed-off-by:
Alan Cox <alan@linux.intel.com> Signed-off-by:
-
Heikki Krogerus authored
This also changes the devname parameter delivered to request_threaded_irq() from "mpu_int" to "mpu3050". Signed-off-by:
-
Olof Johansson authored
Adding invn,mpu3050 as the initial id. Signed-off-by:
-
- 23 Dec, 2011 1 commit
-
-
Tai-hwa Liang authored
- Add documentation for the Cx/Dx hardware release; - Fix wrong register offset for retrieving button information; - Document programming sequence for page register R/W; - Document a couple of supported gesture IDs. Signed-off-by:
-
- 12 Dec, 2011 8 commits
-
-
Jason Gerecke authored
The Cintiq 24HD has three LEDs on the left side of the tablet and three LEDs on the right side of the tablet. Switching to LED 0, 1, or 2 will enable the top, middle, or bottom LED for the respective side. Switching to LED 3 turns off the LEDs on the respective side. Signed-off-by:
Jason Gerecke <killertofu@gmail.com> Reviewed-by:
-
Jason Gerecke authored
Adds support for the Cintiq 24HD. There are two quirks about this model that haven't been seen in prior tablets. First, a second touch ring is present on this display; it is being exposed via the ABS_THROTTLE axis. Second, three capacitive buttons at the top of the unit are available; though physically a touch strip, we report the use of these buttons with generic KEY_ events. Signed-off-by:
-
Courtney Cavin authored
This driver adds support for Sharp's GP2AP002A00F proximity sensor. The proximity is measured as a binary switch, i.e. an object is either detected or not detected. Hence, this driver is implemented as a switch that reports SW_FRONT_PROXIMITY. Reviewed-by:
Datta Shubhrajyoti <shubhrajyoti@ti.com> Signed-off-by:
Courtney Cavin <courtney.cavin@sonyericsson.com> Signed-off-by:
Oskar Andero <oskar.andero@sonyericsson.com> Signed-off-by:
-
Axel Lin authored
These symbols are not used outside it's driver so no need to make the symbol global. Signed-off-by:
Axel Lin <axel.lin@gmail.com> Acked-by:
Michael Hennerich <michael.hennerich@analog.com> Acked-by:
-
Axel Lin authored
This patch converts mc13783-pwrbutton to use the module_platform_driver() macro which makes the code smaller and a bit simpler. Also staticise mc13783_pwrbutton_driver which is not used outside this driver so no need to make the symbol global. Signed-off-by:
-
Dmitry Torokhov authored
Register input device last so that we do not have to reset input device pointer after calling input_unregister_device(). Signed-off-by: -
Dmitry Torokhov authored
Signed-off-by: -
Dmitry Torokhov authored
Signed-off-by:
-
- 01 Dec, 2011 2 commits
-
-
Dmitry Torokhov authored
Having module device table based on PNP id produces the following warning: CC drivers/input/touchscreen/htcpen.o drivers/input/touchscreen/htcpen.c:50: warning: 'pnp_ids' defined but not used This happens because it is not a PNP driver, bit rather ISA driver and pnp_ids table is not used anywhere. To fix this issue let's switch to DMI-based module table instead, Reported-by:
-
Jonathan Cameron authored
This variant was introduced in i2c: boilerplate function for byte swapped smbus_write/read_word_data This also has the side effect of ensuring any errors from the i2c read and no longer mangled. Signed-off-by:
Jonathan Cameron <jic23@cam.ac.uk> Acked-by:
-
