kernel.git/drivers/input/mouse/elantech.c, branch linux-2.6.32.y

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

2011-05-09T22:55:08Z

commit 7f29f17b57255b6395046805a98bc663ded63fb8 upstream. 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 [bwh: Adjust for 2.6.32] Signed-off-by: Greg Kroah-Hartman

Input: elantech - relax signature checks

2011-05-09T22:55:07Z

commit a083632eaf6231162b33e40561cfec6a9c156945 upstream. 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 [bwh: Adjust context for 2.6.32] Signed-off-by: Greg Kroah-Hartman

Input: elantech - use all 3 bytes when checking version

2011-05-09T22:55:06Z

commit 504e8beed161bd11a2c6cbb8aaf352c14d39b5bb upstream. 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 Signed-off-by: Greg Kroah-Hartman

Input: elantech - ignore high bits in the position coordinates

2011-05-09T22:55:06Z

commit e938fbfd4a7ac829d48b767c4dc365535d5c4f97 upstream. In older versions of the elantech hardware/firmware those bits always were unset, so it didn't actually matter, but newer versions seem to use those high bits for something else, screwing up the coordinates we report to the input layer for those devices. Signed-off-by: Florian Ragwitz Signed-off-by: Dmitry Torokhov Signed-off-by: Greg Kroah-Hartman

Input: elantech - allow forcing Elantech protocol

2011-05-09T22:55:06Z

commit f81bc788ff91d4efd4baf88b2c29713838caa8e5 upstream. Apparently hardware vendors now ship elantech touchpads with different version magic. This options allows for them to be tested easier with the current driver in order to add their magic to the whitelist later. Signed-off-by: Florian Ragwitz Signed-off-by: Dmitry Torokhov Signed-off-by: Greg Kroah-Hartman

Input: elantech - fix firmware version check

2011-05-09T22:55:05Z

commit 225c61aad38b12924b3df5f4ef43150c0d6bae8c upstream. The check determining whether device should use 4- or 6-byte packets was trying to compare firmware with 2.48, but was failing on majors greater than 2. The new check ensures that versions like 4.1 are checked properly. Signed-off-by: Florian Ragwitz Signed-off-by: Dmitry Torokhov Signed-off-by: Greg Kroah-Hartman

Input: elantech - do not advertise relative events

2011-05-09T22:55:05Z

commit c7a1f3ccfc2f99427f2e1545b3171e98539c3c95 upstream. Elantech touchpads work in absolute mode and do not generate relative events so they should not be advertising them. Signed-off-by: Dmitry Torokhov Signed-off-by: Greg Kroah-Hartman

Input: psmouse - use boolean type

2009-09-11T05:11:38Z

Signed-off-by: Dmitry Torokhov

Input: elantech - make sure touchpad is really in absolute mode

2009-04-19T02:11:59Z

There exist laptops with Elantech touchpads where switching to absolute mode does not happen, although writing the configuration register succeeds without error. Reading back the register afterwards reveils that the absolute mode bit is not set as if masked out by the touchpad firmware. Always read back register 0x10, make sure that for hardware version 1 the absolute mode bit is actually set and fail otherwise. This prevents the case where the touchpad is claimed by the Elantech driver but is nonetheless not working. Signed-off-by: Arjan Opmeer Signed-off-by: Dmitry Torokhov

Input: elantech - provide a workaround for jumpy cursor on firmware 2.34

2009-04-19T02:11:51Z

It seems that Elantech touchpad firmware version 2.34 on the Hercules eCAFÉ suffers from a problem where bogus coordinates get reported at the beginning of a touch action. This causes the mouse cursor or the scrolled page to jump. Included patch provides a workaround that discards mouse packets that are likely to contain bogus coordinates. The workaround is activated when we detect touchpad with fimware version 2.34. Signed-off-by: Arjan Opmeer Signed-off-by: Dmitry Torokhov