- 24 Feb, 2012 4 commits
-
-
Dmitry Torokhov authored
On m68k: drivers/input/misc/twl4030-vibra.c:175:5: warning: "CONFIG_PM" is not defined We should use #ifdef instead of #if and also check CONFIG_PM_SLEEP instead of CONFIG_PM. Reported-by:
Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by:
Dmitry Torokhov <dtor@mail.ru>
-
Heiko Stübner authored
Commit 509f87c5 (evdev - do not block waiting for an event if fd is nonblock) created a code path were it was possible to use retval uninitialized. This could lead to the xorg evdev input driver getting corrupt data and refusing to work with log messages like AUO-Pixcir touchscreen: Read error: Success sg060_keys: Read error: Success AUO-Pixcir touchscreen: Read error: Success sg060_keys: Read error: Success (for drivers auo-pixcir-ts and gpio-keys). Signed-off-by:
Heiko Stuebner <heiko@sntech.de> Acked-by:
Dima Zavin <dima@android.com> Signed-off-by:
-
Chris Bagwell authored
Signed-off-by:
Chris Bagwell <chris@cnpbagwell.com> Signed-off-by:
-
Akio Idehara authored
ALPS touchpad detection fails if some buttons of ALPS are pressed. The reason is that the "E6" query response byte is different from what is expected. This was tested on a Toshiba Portege R500. Cc: stable <stable@vger.kernel.org> Signed-off-by:
Akio Idehara <zbe64533@gmail.com> Tested-by:
Seth Forshee <seth.forshee@canonical.com> Signed-off-by:
-
- 03 Feb, 2012 1 commit
-
-
Igor Murzov authored
From 2d5a38a56453421e82428155f4b00303f3fb19b2 Mon Sep 17 00:00:00 2001 From: Igor Murzov <e-mail@date.by> Date: Wed, 1 Feb 2012 03:11:53 +0400 Subject: [PATCH] Input: i8042 - add Lenovo Ideapad U455 to 'reset' blacklist Lenovo Ideapad U455 needs to be in the reset quirk list for its touchpad's proper function. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=40672Signed-off-by:
Igor Murzov <e-mail@date.by> Signed-off-by:
-
- 01 Feb, 2012 5 commits
-
-
Che-Liang Chiou authored
serio_raw_read now returns (sometimes partially) successful number of bytes transferred to the caller, and only returns error code to the caller on completely failed transfers. Signed-off-by:
Che-Liang Chiou <clchiou@chromium.org> Signed-off-by:
-
Henrik Rydberg authored
Add a section which defines the input device properties and provides guidelines on how to use them. Signed-off-by:
Henrik Rydberg <rydberg@euromail.se> Reviewed-by:
Chase Douglas <chase.douglas@canonical.com> Reviewed-by:
Jussi Pakkanen <jussi.pakkanen@canonical.com> Signed-off-by:
-
Felipe Contreras authored
And trivial whitespace fixes. Signed-off-by:
Felipe Contreras <felipe.contreras@gmail.com> Signed-off-by:
-
Heiko Stübner authored
A struct device parameter is used in the enable and disable callbacks to distinguish between different gpio_keys devices. Platforms that don't use these callbacks may not include struct device at all, as seen on arch/arm/mach-s3c2410/mach-n30.c Signed-off-by:
-
Heiko Stübner authored
Commit 509f87c5 (evdev - do not block waiting for an event if fd is nonblock) created a code path were it was possible to use retval uninitialized. This could lead to the xorg evdev input driver getting corrupt data and refusing to work with log messages like AUO-Pixcir touchscreen: Read error: Success sg060_keys: Read error: Success AUO-Pixcir touchscreen: Read error: Success sg060_keys: Read error: Success (for drivers auo-pixcir-ts and gpio-keys). Signed-off-by:
-
- 11 Jan, 2012 5 commits
-
-
Jussi Pakkanen authored
Some bcm5974 trackpads have a physical button beneath the physical surface. This patch sets the property bit so user space applications can detect the trackpad type and act accordingly. Signed-off-by:
-
Dmitry Torokhov authored
If serio_raw_write was always returning number of bytes successfully sent to serio port and never signalled error condition to the caller. Change it so that for completely failed transfers appropriate error code returned to the caller (partially successful writes still return number of bytes transferred). Reported-by:
-
Dmitry Torokhov authored
Commit 8c1c10d5 attempted to signal POLLHUP | POLLERR condition when polling disconnected device, unfortunately it did not do it quite correctly. Reported-by:
-
Che-Liang Chiou authored
Signed-off-by:
-
Dmitry Torokhov authored
Recent conversion to module_platform_driver() went a bit too far and converted not only drivers that used platform_driver_register() but also ones using platform_driver_probe(), breaking them in process. Reported-by:
-
- 09 Jan, 2012 1 commit
-
-
Dmitry Torokhov authored
-
- 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:
Linus Walleij <linus.walleij@linaro.org> 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 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:
-
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:
Mark Brown <broonie@opensource.wolfsonmicro.com> 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:
Rakesh Iyer <riyer@nvidia.com> Acked-by:
Stephen Warren <swarren@nvidia.com> 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:
-
- 29 Dec, 2011 1 commit
-
-
Tai-hwa Liang authored
Fixing wrong register offset which is used to retrieve the number of buttons attached to the hardware. 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:
-
- 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 2 commits
-
-
Tai-hwa Liang authored
Make sure that mutex is released upon register writing failure. This fixes boot freezing observed on ARM based OLPC (http://dev.laptop.org/ticket/11357). Signed-off-by:
-
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 2 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:
Ping Cheng <pingc@wacom.com> Signed-off-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:
-
