linux.git/drivers/input/mouse/elantech.c, branch v3.1

Input: elantech - remove support for proprietary X driver

2011-05-17T05:48:43+00:00

Apparently somewhere someone had a proprietary X driver. To get the
multitouch info, it uses some hack on the normal API instead of using
the multitouch protocol. Now that the multitouch info is transmitted
correctly it makes not much sense to keep it. Especially because it's
impossible to find this proprietary X driver anywhere, so the number of
users must be very low.

Signed-off-by: Éric Piel 
Reviewed-by: Henrik Rydberg 
Signed-off-by: Dmitry Torokhov

Input: elantech - report multitouch with proper ABS_MT messages

2011-05-17T05:48:39+00:00

Multitouch info was reported only via a old protocol used by the
proprietary X driver from elantech. Let's report the multitouch info
also following the official MT protocol. It's semi-mt because the device
only reports the lowest/highest coordinates.

This was done following the multi-touch-protocol.txt documentation, and
inspired by the bcm5974 and elantech implementations. Testing was light
as there is not many applications using this protocol yet, but the X
synaptics driver didn't complain and the X multitouch driver behaved
correctly.

Signed-off-by: Éric Piel 
Reviewed-by: Henrik Rydberg 
Signed-off-by: Dmitry Torokhov

Input: elantech - export pressure and width when supported

2011-05-17T05:48:36+00:00

Using the info of the Dell/Ubuntu driver, described in the protocol
document, report both width and pressure when pressing 1 and 3
fingers, for the versions of the touchpad which support it.

Signed-off-by: Éric Piel 
Reviewed-by: Henrik Rydberg 
Signed-off-by: Dmitry Torokhov

Input: return -ENOMEM in select drivers when memory allocation fails

2010-10-13T14:49:23+00:00

Instead of using -1 let's start using proper error codes.

Signed-off-by: Davidlohr Bueso 
Signed-off-by: Dmitry Torokhov

Input: elantech - report position also with 3 fingers

2010-08-06T06:53:22+00:00

The 6-byte protocol supports reporting the position when three fingers
are pressed, exactly like when one finger is pressed. Report this.

In addition, it is also distinguishes between 3 and 4 fingers pressed.

Signed-off-by: Éric Piel 
Signed-off-by: Dmitry Torokhov

Input: elantech - discard the first 2 positions on some firmwares

2010-08-06T06:52:29+00:00

According to the Dell/Ubuntu driver, what was previously observed as
"jumpy cursor" corresponds to the hardware sending incorrect data for
the first two reports of a one touch finger. So let's use the same
workaround as in the other driver. Also, detect another firmware
version with the same behaviour, as in the other driver.

Signed-off-by: Éric Piel 
Signed-off-by: Dmitry Torokhov

Input: elantech - relax signature checks

2010-05-19T17:15:13+00:00

Apparently there are Elantech touchpads that report non-zero in the 2nd byte
of their signature. Adjust the detection routine so that if 2nd byte is
zero and 3rd byte contains value that is not a valid report rate, we still
assume that signature is valid.

Tested-by: Eric Piel 
Signed-off-by: Dmitry Torokhov

Input: elantech - enforce common prefix on messages

2010-05-19T17:15:02+00:00

Signed-off-by: Dmitry Torokhov

Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input

2010-05-13T14:28:43+00:00

* 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input:
  Input: ad7877 - keep dma rx buffers in seperate cache lines
  Input: psmouse - reset all types of mice before reconnecting
  Input: elantech - use all 3 bytes when checking version
  Input: iforce - fix Guillemot Jet Leader 3D entry
  Input: iforce - add Guillemot Jet Leader Force Feedback

Input: elantech - use all 3 bytes when checking version

2010-05-13T07:43:19+00:00

Apparently all 3 bytes returned by ETP_FW_VERSION_QUERY are significant
and should be taken into account when matching hardware version/features.

Tested-by: Eric Piel 
Signed-off-by: Dmitry Torokhov