linux-toradex.git/drivers/input/mouse/elantech.h, branch v3.4.73

Input: elantech - add resolution query support for v4 hardware

2011-11-21T06:28:34+00:00

It turns out that v4's firmware provides a command so we can query
the resolution. Let's use it.

Signed-off-by: JJ Ding 
Reviewed-by: Daniel Kurtz 
Signed-off-by: Dmitry Torokhov

Input: elantech - add support for elantech fast command

2011-11-21T06:28:30+00:00

Starting with v3 hardware, the firmware supports this shorter
elantech_send_cmd. Teach the driver to use it.

Signed-off-by: JJ Ding 
Reviewed-by: Daniel Kurtz 
Signed-off-by: Dmitry Torokhov

Input: elantech - better support all those v2 variants

2011-09-21T05:46:27+00:00

V2 hardware has many variants. This patch adddresses two issues:

 - some model also has debounce packets, but with a different signature
   than v3. Now we just check debounce for all v2 hardware.

 - due to different scanning methods the hardware uses, x and y ranges have
   to be calculated differently. And for some specific versions, we can just
   see them as custom-made, so set {x, y} the same values as Windows driver
   does.

Signed-off-by: JJ Ding 
Tested-by: Richard Schütz 
Reviewed-by: Éric Piel 
Signed-off-by: Dmitry Torokhov

Input: elantech - add v4 hardware support

2011-09-09T17:35:02+00:00

v4 hardware is a true multitouch capable touchpad (up to 5 fingers).
The packet format is quite complex, please see protocol document for
reference.

Signed-off-by: JJ Ding 
Signed-off-by: Dmitry Torokhov

Input: elantech - add v3 hardware support

2011-09-09T17:34:58+00:00

v3 hardware's packet format is almost identical to v2 (one/three finger touch),
except when sensing two finger touch, the hardware sends 12 bytes of data.

Signed-off-by: JJ Ding 
Acked-by: Daniel Kurtz 
Acked-by: Éric Piel 
Signed-off-by: Dmitry Torokhov

Input: elantech - remove ETP_EDGE_FUZZ_V2

2011-09-09T17:34:40+00:00

Don't try to be too clever and remove ETP_EDGE_FUZZ_V2. X, Y ranges
should be just the raw resolution of the device. Otherwise, they can
cause underflow on the Y axis.

Suggested-by: Éric Piel 
Signed-off-by: JJ Ding 
Acked-by: Daniel Kurtz 
Acked-by: Éric Piel 
Signed-off-by: Dmitry Torokhov

Input: elantech - use firmware provided x, y ranges

2011-09-09T17:34:36+00:00

With newer hardware, the touchpad provides range info.
Let's use it.

Signed-off-by: JJ Ding 
Acked-by: Daniel Kurtz 
Acked-by: Éric Piel 
Signed-off-by: Dmitry Torokhov

Input: elantech - get rid of ETP_2FT_* in elantech.h

2011-09-09T17:34:31+00:00

For two finger touches the coordinate of each finger gets reported
separately but with reduced resolution.

With this change, we now have the same range for ST and MT data and
scale MT data because it has lower resolution to match ST.

Suggested-by: Dmitry Torokhov 
Signed-off-by: JJ Ding 
Acked-by: Daniel Kurtz 
Acked-by: Éric Piel 
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: 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