Linux kernel stable tree (mirror) https://git.radix-linux.su/kernel/linux.git/atom?h=linux-2.6.34.y 2012-03-14T14:57:33+00:00 2012-03-14T14:57:33+00:00 Éric Piel E.A.B.Piel@tudelft.nl 2010-08-06T06:51:49+00:00 urn:sha1:e83ff3dd0768d28aa2b5d91393b37e2fa0d17bdc 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 <eric.piel@tremplin-utc.net> Signed-off-by: Dmitry Torokhov <dtor@mail.ru> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> 2012-03-14T14:57:32+00:00 Dmitry Torokhov dmitry.torokhov@gmail.com 2010-05-19T17:11:13+00:00 urn:sha1:94a22b2f32a57ead40fb08f5d9de9e0f341710db 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 <eric.piel@tremplin-utc.net> Signed-off-by: Dmitry Torokhov <dtor@mail.ru> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> 2011-06-26T16:46:27+00:00 Edgar (gimli) Hucek gimli@dark-green.com 2010-11-09T16:38:42+00:00 urn:sha1:35a6e6bd6ca56f583b7399a079005e3c918a1ba1 commit 6021afcf19d8c6f5db6d11cadcfb6a22d0c28a48 upstream. This patch adds support for the MacBookAir3,1 and MacBookAir3,2 models. [rydberg@euromail.se: touchpad range calibration] Signed-off-by: Edgar (gimli) Hucek <gimli@dark-green.com> Signed-off-by: Henrik Rydberg <rydberg@euromail.se> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> 2010-05-13T14:28:43+00:00 Linus Torvalds torvalds@linux-foundation.org 2010-05-13T14:28:43+00:00 urn:sha1:aa86f26bd81a46985f1b32e513638d1c36cf3104 * '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 2010-05-13T07:43:26+00:00 Dmitry Torokhov dmitry.torokhov@gmail.com 2010-05-13T07:42:23+00:00 urn:sha1:ef110b24e28f36620f63dab94708a17c7e267358 Synaptics hardware requires resetting device after suspend to ram in order for the device to be operational. The reset lives in synaptics-specific reconnect handler, but it is not being invoked if synaptics support is disabled and the device is handled as a standard PS/2 device (bare or IntelliMouse protocol). Let's add reset into generic reconnect handler as well. Signed-off-by: Dmitry Torokhov <dtor@mail.ru> 2010-05-13T07:43:19+00:00 Dmitry Torokhov dmitry.torokhov@gmail.com 2010-05-13T07:41:15+00:00 urn:sha1:504e8beed161bd11a2c6cbb8aaf352c14d39b5bb 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 <eric.piel@tremplin-utc.net> Signed-off-by: Dmitry Torokhov <dtor@mail.ru> 2010-05-05T14:53:18+00:00 Linus Torvalds torvalds@linux-foundation.org 2010-05-05T14:53:18+00:00 urn:sha1:1d7aec304147aadcbc66ef9ab691208f9f22b6a8 * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input: Input: joydev - allow binding to button-only devices Input: elantech - ignore high bits in the position coordinates Input: elantech - allow forcing Elantech protocol Input: elantech - fix firmware version check Input: ati_remote - add some missing devices from lirc_atiusb Input: eeti_ts - cancel pending work when going to suspend Input: Add support of Synaptics Clickpad device Revert "Input: ALPS - add signature for HP Pavilion dm3 laptops" Input: psmouse - ignore parity error for basic protocols 2010-05-04T06:35:11+00:00 Florian Ragwitz rafl@debian.org 2010-05-04T06:29:37+00:00 urn:sha1:e938fbfd4a7ac829d48b767c4dc365535d5c4f97 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 <rafl@debian.org> Signed-off-by: Dmitry Torokhov <dtor@mail.ru> 2010-05-04T06:34:33+00:00 Florian Ragwitz rafl@debian.org 2010-04-27T07:47:04+00:00 urn:sha1:f81bc788ff91d4efd4baf88b2c29713838caa8e5 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 <rafl@debian.org> Signed-off-by: Dmitry Torokhov <dtor@mail.ru> 2010-05-04T06:34:13+00:00 Florian Ragwitz rafl@debian.org 2010-04-27T07:45:10+00:00 urn:sha1:225c61aad38b12924b3df5f4ef43150c0d6bae8c 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 <rafl@debian.org> Signed-off-by: Dmitry Torokhov <dtor@mail.ru>