linux-stable.git/drivers/input, branch v3.18.24

Input: evdev - do not report errors form flush()

2015-10-07T14:12:48+00:00

[ Upstream commit eb38f3a4f6e86f8bb10a3217ebd85ecc5d763aae ]

We've got bug reports showing the old systemd-logind (at least
system-210) aborting unexpectedly, and this turned out to be because
of an invalid error code from close() call to evdev devices.  close()
is supposed to return only either EINTR or EBADFD, while the device
returned ENODEV.  logind was overreacting to it and decided to kill
itself when an unexpected error code was received.  What a tragedy.

The bad error code comes from flush fops, and actually evdev_flush()
returns ENODEV when device is disconnected or client's access to it is
revoked. But in these cases the fact that flush did not actually happen is
not an error, but rather normal behavior. For non-disconnected devices
result of flush is also not that interesting as there is no potential of
data loss and even if it fails application has no way of handling the
error. Because of that we are better off always returning success from
evdev_flush().

Also returning EINTR from flush()/close() is discouraged (as it is not
clear how application should handle this error), so let's stop taking
evdev->mutex interruptibly.

Bugzilla: http://bugzilla.suse.com/show_bug.cgi?id=939834
Cc: 
Signed-off-by: Takashi Iwai 
Signed-off-by: Dmitry Torokhov 
Signed-off-by: Sasha Levin

Input: usbtouchscreen - avoid unresponsive TSC-30 touch screen

2015-08-27T17:25:45+00:00

[ Upstream commit 968491709e5b1aaf429428814fff3d932fa90b60 ]

This patch fixes a problem in the usbtouchscreen driver for DMC TSC-30
touch screen.  Due to a missing delay between the RESET and SET_RATE
commands, the touch screen may become unresponsive during system startup or
driver loading.

According to the DMC documentation, a delay is needed after the RESET
command to allow the chip to complete its internal initialization. As this
delay is not guaranteed, we had a system where the touch screen
occasionally did not send any touch data. There was no other indication of
the problem.

The patch fixes the problem by adding a 150ms delay between the RESET and
SET_RATE commands.

Cc: stable@vger.kernel.org
Suggested-by: Jakob Mustafa 
Signed-off-by: Bernhard Bender 
Signed-off-by: Dmitry Torokhov 
Signed-off-by: Sasha Levin

Input: synaptics - add min/max quirk for Lenovo S540

2015-07-21T01:12:44+00:00

[ Upstream commit 7f2ca8b55aeff1fe51ed3570200ef88a96060917 ]

https://bugzilla.redhat.com/show_bug.cgi?id=1223051#c2

Cc: stable@vger.kernel.org
Tested-by: tommy.gagnes@gmail.com
Signed-off-by: Peter Hutterer 
Signed-off-by: Dmitry Torokhov 
Signed-off-by: Sasha Levin

Revert "Input: synaptics - add min/max quirk for Lenovo S540"

2015-07-21T01:12:44+00:00

This reverts commit e73268af3e137b1f69d0f82d80aa88e0e8c7cbbe.

Seems like an incorrect merge on my end, will pick the upstream
version again next.

Signed-off-by: Sasha Levin

Input: pixcir_i2c_ts - fix receive error

2015-07-04T03:02:32+00:00

[ Upstream commit 469d7d22cea146e40efe8c330e5164b4d8f13934 ]

The i2c_master_recv() uses readsize to receive data from i2c but compares
to size of rdbuf which is always 27. This would cause problem when the
max_fingers is not 5. Change the comparison value to readsize instead.

Fixes: 36874c7e219 ("Input: pixcir_i2c_ts - support up to 5 fingers and
hardware tracking IDs:)

Cc: stable@vger.kernel.org
Signed-off-by: Frodo Lai 
Signed-off-by: Dmitry Torokhov 
Signed-off-by: Sasha Levin

Input: elantech - fix detection of touchpads where the revision matches a known rate

2015-07-03T16:34:37+00:00

[ Upstream commit 5f0ee9d17aae628b22be86966471db65be21f262 ]

Make the check to skip the rate check more lax, so that it applies
to all hw_version 4 models.

This fixes the touchpad not being detected properly on Asus PU551LA
laptops.

Cc: stable@vger.kernel.org
Reported-and-tested-by: David Zafra Gómez 
Signed-off-by: Hans de Goede 
Signed-off-by: Dmitry Torokhov 
Signed-off-by: Sasha Levin

Input: synaptics - add min/max quirk for Lenovo S540

2015-07-03T16:34:36+00:00

[ Upstream commit 7f2ca8b55aeff1fe51ed3570200ef88a96060917 ]

https://bugzilla.redhat.com/show_bug.cgi?id=1223051#c2

Cc: stable@vger.kernel.org
Tested-by: tommy.gagnes@gmail.com
Signed-off-by: Peter Hutterer 
Signed-off-by: Dmitry Torokhov 
Signed-off-by: Sasha Levin

Input: elantech - fix absolute mode setting on some ASUS laptops

2015-05-17T23:12:05+00:00

[ Upstream commit bd884149aca61de269fd9bad83fe2a4232ffab21 ]

On ASUS TP500LN and X750JN, the touchpad absolute mode is reset each
time set_rate is done.

In order to fix this, we will verify the firmware version, and if it
matches the one in those laptops, the set_rate function is overloaded
with a function elantech_set_rate_restore_reg_07 that performs the
set_rate with the original function, followed by a restore of reg_07
(the register that sets the absolute mode on elantech v4 hardware).

Also the ASUS TP500LN and X750JN firmware version, capabilities, and
button constellation is added to elantech.c

Cc: stable@vger.kernel.org
Reported-and-tested-by: George Moutsopoulos 
Signed-off-by: Ulrik De Bie 
Signed-off-by: Dmitry Torokhov 
Signed-off-by: Sasha Levin

Input: synaptics - do not retrieve the board id on old firmwares

2015-04-17T00:11:35+00:00

[ Upstream commit b57a7128be24062b5b5b26032b7cd58f1651547e ]

The board id capability has been added in firmware 7.5.

Cc: stable@vger.kernel.org
Signed-off-by: Benjamin Tissoires 
Acked-by: Hans de Goede 
Signed-off-by: Dmitry Torokhov 
Signed-off-by: Sasha Levin

Input: synaptics - handle spurious release of trackstick buttons

2015-04-17T00:11:35+00:00

[ Upstream commit ebc80840b850db72f7ae84fbcf77630ae5409629 ]

The Fimware 8.1 has a bug in which the extra buttons are only sent when the
ExtBit is 1.  This should be fixed in a future FW update which should have
a bump of the minor version.

Cc: stable@vger.kernel.org
Signed-off-by: Benjamin Tissoires 
Acked-by: Hans de Goede 
Signed-off-by: Dmitry Torokhov 
Signed-off-by: Sasha Levin