linux-stable.git/drivers/input/touchscreen, branch linux-3.10.y

Input: ili210x - fix permissions on "calibrate" attribute

2017-02-10T10:03:32+00:00

commit b27c0d0c3bf3073e8ae19875eb1d3755c5e8c072 upstream.

"calibrate" attribute does not provide "show" methods and thus we should
not mark it as readable.

Signed-off-by: Dmitry Torokhov 
Signed-off-by: Willy Tarreau

Input: wacom_w8001 - w8001_MAX_LENGTH should be 13

2016-08-21T21:22:42+00:00

commit 12afb34400eb2b301f06b2aa3535497d14faee59 upstream.

Somehow the patch that added two-finger touch support forgot to update
W8001_MAX_LENGTH from 11 to 13.

Signed-off-by: Ping Cheng 
Reviewed-by: Peter Hutterer 
Cc: stable@vger.kernel.org
Signed-off-by: Dmitry Torokhov 
Signed-off-by: Willy Tarreau

Input: ads7846 - correct the value got from SPI

2016-06-07T08:42:53+00:00

commit 879f2fea8a5a748bcbf98d2cdce9139c045505d3 upstream.

According to the touch controller spec, SPI return a 16 bit value, only 12
bits are valid, they are bit[14-3].

The value of MISO and MOSI can be configured when SPI is in idle mode.
Currently this touch driver assumes the SPI bus sets the MOSI and MISO in
low level when SPI bus is in idle mode. So the bit[15] of the value got
from SPI bus is always 0. But when SPI bus congfigures the MOSI and MISO in
high level during the SPI idle mode, the bit[15] of the value get from SPI
is always 1. If bit[15] is not masked, we may get the wrong value.

Mask the invalid bit to make sure the correct value gets returned.
Regardless of the SPI bus idle configuration.

Signed-off-by: Andrey Gelman 
Signed-off-by: Haibo Chen 
Signed-off-by: Igor Grinberg 
Signed-off-by: Dmitry Torokhov 
Signed-off-by: Willy Tarreau

Input: usbtouchscreen - avoid unresponsive TSC-30 touch screen

2015-08-10T19:20:30+00:00

commit 968491709e5b1aaf429428814fff3d932fa90b60 upstream.

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.

Suggested-by: Jakob Mustafa 
Signed-off-by: Bernhard Bender 
Signed-off-by: Dmitry Torokhov 
Signed-off-by: Greg Kroah-Hartman

Input: usbtouchscreen - separate report and transmit buffer size handling

2013-12-20T15:45:08+00:00

commit 4ef38351d770cc421f4a0c7a849fd13207fc5741 upstream.

This patch supports the separate handling of the USB transfer buffer length
and the length of the buffer used for multi packet support. For devices
supporting multiple report or diagnostic packets, the USB transfer size is now
limited to the USB endpoints wMaxPacketSize - otherwise it defaults to the
configured report packet size as before.

This fixes an issue where event reporting can be delayed for an arbitrary
time for multi packet devices. For instance the report size for eGalax devices
is defined to the 16 byte maximum diagnostic packet size as opposed to the 5
byte report packet size. In case the driver requests 16 byte from the USB
interrupt endpoint, the USB host controller driver needs to split up the
request into 2 accesses according to the endpoints wMaxPacketSize of 8 byte.
When the first transfer is answered by the eGalax device with not less than
the full 8 byte requested, the host controller has got no way of knowing
whether the touch controller has got additional data queued and will issue
the second transfer. If per example a liftoff event finishes at such a
wMaxPacketSize boundary, the data will not be available to the usbtouch driver
until a further event is triggered and transfered to the host. From user
perspective the BTN_TOUCH release event in this case is stuck until the next
touch down event.

Signed-off-by: Christian Engelmayer 
Signed-off-by: Dmitry Torokhov 
Signed-off-by: Greg Kroah-Hartman

Input: usbtouchscreen: ignore eGalax/D-Wav/EETI HIDs

2013-12-04T18:57:18+00:00

commit ae2aa3a512fa5f50f67feba9e66bc2efb394bd63 upstream.

The HID driver now handles these devices, regardless of what protocol
the device claims it supports.

Signed-off-by: Forest Bond 
Acked-by: Dmitry Torokhov 
Signed-off-by: Jiri Kosina 
Signed-off-by: Greg Kroah-Hartman

Input: cyttsp - fix swapped mfg_stat and mfg_cmd registers

2013-06-06T05:46:37+00:00

The command and status register in the driver were swapped with
respect to the order specified in the datasheet (CY8CTMA140).
Confirmed with Cypress that the order in the datasheet is correct.

Signed-off-by: Matthias Kaehlcke 
Acked-by: Javier Martinez Canillas 
Signed-off-by: Dmitry Torokhov

Input: cyttsp - add missing handshake

2013-06-06T05:46:34+00:00

For the devices that has blocking with timeout communication, these
extra handshakes will prevent one timeout delay in startup sequence

Tested-by: Ferruh Yigit  on TMA300-DVK
Signed-off-by: Ferruh Yigit 
Acked-by: Javier Martinez Canillas 
Signed-off-by: Dmitry Torokhov

Input: cyttsp - fix memcpy size param

2013-06-06T05:46:30+00:00

memcpy param is wrong because of offset in bl_cmd, this may corrupt the
stack which may cause a crash.

Tested-by: Ferruh Yigit  on TMA300-DVK
Signed-off-by: Ferruh Yigit 
Acked-by: Javier Martinez Canillas 
Cc: stable@vger.kernel.org
Signed-off-by: Dmitry Torokhov

Input: egalax_ts - ABS_MT_POSITION_Y not reported well

2013-05-06T03:13:10+00:00

The egalax_ts touchscreen modul not report ABS_MT_POSITION_Y proper.
As result it may be, that upper software levels only receive x coordinates well.

Signed-off-by: Heiko Abraham 
Cc: stable@vger.kernel.org
Signed-off-by: Dmitry Torokhov