litmus-rt-imx6.git/drivers/input/touchscreen, branch master LITMUS^RT and MC^2 V1 support for the i.MX6 processor family. Input: tsc2007 - add device tree support. 2014-04-16T13:58:15+00:00 Denis Carikli denis@eukrea.com 2013-11-19T19:56:04+00:00 ea88b2a6c41c87ce11eb309536baa416c72ee7f2 Signed-off-by: Denis Carikli <denis@eukrea.com> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> 
Signed-off-by: Denis Carikli <denis@eukrea.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
ENGR00277223-1 input: port elan touch driver to 3.10 kernel 2014-04-16T13:01:35+00:00 Robby Cai R63905@freescale.com 2013-08-29T05:44:37+00:00 e4107c07209d9fa9026158c00697a7e33f9386f2 It's ported from 3.5.7 kernel. To test this driver, the EBook Daughter Board need to be attached (on imx6dl sabresd or imx6sl evk board). Signed-off-by: Robby Cai <R63905@freescale.com> 
It's ported from 3.5.7 kernel. To test this driver, the EBook Daughter
Board need to be attached (on imx6dl sabresd or imx6sl evk board).

Signed-off-by: Robby Cai <R63905@freescale.com>
ENGR00275004-1 input: touchscreen: max11801_ts: Add DCM mode for max11801 ADC 2014-04-16T13:01:17+00:00 Robin Gong b38343@freescale.com 2013-08-13T08:58:26+00:00 678199152705826f1fee736759d53e56155508bd We need add DCM mode/AUX mode for ADC converter function of max11801, so that it can be used to read voltage of battery. Meanwhile, let the driver based on device tree. The patchset is based on below patch (V3.5.7): commit 4001774cf51f0140ae7e4e8e0ec1d86475790682 Author: Rong Dian <b38775@freescale.com> Date: Fri Jan 18 14:24:28 2013 +0800 Engr00240284-1 MAX11801: Add DCM aux adc sample function 1.Add direct conversion mode operations 2.Add aux adc sample function Signed-off-by: Robin Gong <b38343@freescale.com> 
We need add DCM mode/AUX mode for ADC converter function of max11801, so that
it can be used to read voltage of battery. Meanwhile, let the driver based on
device tree. The patchset is based on below patch (V3.5.7):

commit 4001774cf51f0140ae7e4e8e0ec1d86475790682
Author: Rong Dian <b38775@freescale.com>
Date:   Fri Jan 18 14:24:28 2013 +0800

    Engr00240284-1 MAX11801: Add DCM aux adc sample function

        1.Add direct conversion mode operations
	2.Add aux adc sample function

Signed-off-by: Robin Gong <b38343@freescale.com>
ENGR00275384 touch: config: Add egalax touch support in Kconfig 2014-04-16T13:01:14+00:00 Luwei Zhou b45643@freescale.com 2013-08-15T04:20:19+00:00 86dea731f6fb16d7548bafad44359d7ccf4b9c14 Add egalax touchscreen as single-touch support in Kconfig. Signed-off-by: Luwei Zhou <B45643@freescale.com> 
Add  egalax touchscreen as single-touch support in Kconfig.

Signed-off-by: Luwei Zhou  <B45643@freescale.com>
ENGR00274247: touch: add egalax touch driver support on i.MX6Q/DL AUTO/SD 2014-04-16T13:01:06+00:00 Luwei b45643@freescale.com 2013-08-08T08:35:24+00:00 40e015a51dc6d5c86e70faed921ecf8b5f2f9fe8 Copy the egalax touch screen driver from linux3.5.7.Make some modification.Remove the __devinit __devexit __devexit_p out of the file, because 3.10 does not support. Signed-off-by: Luwei Zhou <b45643@freescale.com> 
Copy the egalax touch screen driver from linux3.5.7.Make some
modification.Remove the __devinit __devexit __devexit_p out
of the file, because 3.10 does not support.

Signed-off-by: Luwei Zhou <b45643@freescale.com>
Input: usbtouchscreen - separate report and transmit buffer size handling 2013-12-20T15:45:08+00:00 Christian Engelmayer christian.engelmayer@frequentis.com 2013-11-27T02:16:17+00:00 c3d8edeff268c5d7c6701b238a1d75389efd899c 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 <christian.engelmayer@frequentis.com> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 
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 <christian.engelmayer@frequentis.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Input: usbtouchscreen: ignore eGalax/D-Wav/EETI HIDs 2013-12-04T18:57:18+00:00 Forest Bond forest.bond@rapidrollout.com 2013-10-21T16:38:18+00:00 c2dd82b43dcc08aad0e139e23509efb195ad6fc1 commit ae2aa3a512fa5f50f67feba9e66bc2efb394bd63 upstream. The HID driver now handles these devices, regardless of what protocol the device claims it supports. Signed-off-by: Forest Bond <forest.bond@rapidrollout.com> Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 
commit ae2aa3a512fa5f50f67feba9e66bc2efb394bd63 upstream.

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

Signed-off-by: Forest Bond <forest.bond@rapidrollout.com>
Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Input: cyttsp - fix swapped mfg_stat and mfg_cmd registers 2013-06-06T05:46:37+00:00 Matthias Kaehlcke matthias.list@kaehlcke.net 2013-06-06T05:42:51+00:00 d3bf073aa7d50f06f81b4065a39fd6dc046f8bb2 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 <matthias@kaehlcke.net> Acked-by: Javier Martinez Canillas <javier@dowhile0.org> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> 
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 <matthias@kaehlcke.net>
Acked-by: Javier Martinez Canillas <javier@dowhile0.org>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Input: cyttsp - add missing handshake 2013-06-06T05:46:34+00:00 Ferruh Yigit fery@cypress.com 2013-05-23T17:04:36+00:00 fbd5e77e65c36d84dbcd71a19c4d1526f4604bdb For the devices that has blocking with timeout communication, these extra handshakes will prevent one timeout delay in startup sequence Tested-by: Ferruh Yigit <fery@cypress.com> on TMA300-DVK Signed-off-by: Ferruh Yigit <fery@cypress.com> Acked-by: Javier Martinez Canillas <javier@dowhile0.org> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> 
For the devices that has blocking with timeout communication, these
extra handshakes will prevent one timeout delay in startup sequence

Tested-by: Ferruh Yigit <fery@cypress.com> on TMA300-DVK
Signed-off-by: Ferruh Yigit <fery@cypress.com>
Acked-by: Javier Martinez Canillas <javier@dowhile0.org>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Input: cyttsp - fix memcpy size param 2013-06-06T05:46:30+00:00 Ferruh Yigit fery@cypress.com 2013-05-23T16:56:55+00:00 d2983cdb480157f637df07723f28aaa657b1080d memcpy param is wrong because of offset in bl_cmd, this may corrupt the stack which may cause a crash. Tested-by: Ferruh Yigit <fery@cypress.com> on TMA300-DVK Signed-off-by: Ferruh Yigit <fery@cypress.com> Acked-by: Javier Martinez Canillas <javier@dowhile0.org> Cc: stable@vger.kernel.org Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> 
memcpy param is wrong because of offset in bl_cmd, this may corrupt the
stack which may cause a crash.

Tested-by: Ferruh Yigit <fery@cypress.com> on TMA300-DVK
Signed-off-by: Ferruh Yigit <fery@cypress.com>
Acked-by: Javier Martinez Canillas <javier@dowhile0.org>
Cc: stable@vger.kernel.org
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>