Linux kernel source tree https://git.amat.us/linux/atom/drivers/input?h=v2.6.30.8 2009-09-24T15:27:02Z 2009-09-24T15:27:02Z Stephen Kitt steve@sk2.org 2009-08-12T08:12:08Z urn:sha1:e276bbcae3a15314c94ae97283697d818fbe8a1b commit ec8b4b7085605e801a7740a2c3c33256aebe249c upstream. The KEY_MAX change in 2.6.28 changed the values of the JSIOCSBTNMAP and JSIOCGBTNMAP constants; software compiled with the old values no longer works with kernels following 2.6.28, because the ioctl switch statement no longer matches the values given by the software. This patch handles these ioctls independently of the length of data specified, and applies the same treatment to JSIOCSAXMAP and JSIOCGAXMAP which currently depend on ABS_MAX. Signed-off-by: Stephen Kitt <steve@sk2.org> Signed-off-by: Dmitry Torokhov <dtor@mail.ru> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> 2009-07-30T21:40:32Z Giuseppe Mazzotta g.mazzotta@iragan.com 2009-07-13T04:02:27Z urn:sha1:a5ed86d5af2d63f3edeab7e63f15aa3c34c5cc25 commit e705cee427e319665969ef7ac664f3612dec8899 upstream. This patch adds DMI information to automatically load the correct layout for the Maxdata Pro 7000X/DX notebook models. Such notebooks are clones of Fujitsu Amilo V2000, the hook for the v2000 is being used and I have tested that perfectly works. The immediate result of integrating this patch is that the five special buttons will work on these specific notebook models and that the RF killswitch will not be activated after suspend. This patch definitively obsoletes the fsam7400 module which I was still needing to enable wifi and to fix the RF killswitch suspend problem; in the current 2.6.30 kernel it is necessary to load the wistron_btns module with options 'force=1 keymap=1557/MS2141', which was not anyway a complete workaround. Signed-off-by: Giuseppe Mazzotta <g.mazzotta@iragan.com> Signed-off-by: Dmitry Torokhov <dtor@mail.ru> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> 2009-05-29T15:48:25Z Linus Torvalds torvalds@linux-foundation.org 2009-05-29T15:48:25Z urn:sha1:5f789cd8bae9b6315b7bf93e24ec1ac85f5a13b9 * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input: Input: libps2 - better handle bad scheduler decisions Input: usb1400_ts - fix access to "device data" in resume function Input: multitouch - augment event semantics documentation Input: multitouch - add tracking ID to the protocol 2009-05-28T17:34:02Z Dmitry Torokhov dmitry.torokhov@gmail.com 2009-05-28T16:51:31Z urn:sha1:a3ce6ea46cc0d6397d1b92b1a5983bb2935306ed Sometimes devices send us their responses in time but due to unfortunate scheduling decisions the receiving thread does not get scheduled till much later and we erroneously decide that device timed out. Work around this problem by checking whether we received the data we needed instead of checking timeout condition. Tested-by: Sitsofe Wheeler <sitsofe@yahoo.com> Signed-off-by: Dmitry Torokhov <dtor@mail.ru> 2009-05-27T13:24:41Z Manuel Traut manut@linutronix.de 2009-05-27T13:20:05Z urn:sha1:346a850e3c3a20159cef2b79235e6d34aa497c65 platform_data != driver_data driver data is actually the "correct" place of the struct however it is not placed there due to the need of the ac97 struct. This is broken since d9105c2b01 aka "[ARM] 5184/1: Split ucb1400_ts into core and touchscreen" Signed-off-by: Manuel Traut <manut@linutronix.de> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de> Signed-off-by: Dmitry Torokhov <dtor@mail.ru> 2009-05-23T16:53:18Z Henrik Rydberg rydberg@euromail.se 2009-05-23T16:51:20Z urn:sha1:df391e0eda1e678add56a8e34226edf05d89af6a There are a few multi-touch devices that support finger tracking well in hardware, Stantum being the prime example. By exposing the tracking ID in the MT protocol, evdev bandwidth and cpu usage in user space can be reduced. This patch adds the ABS_MT_TRACKING_ID to the MT protocol. Signed-off-by: Henrik Rydberg <rydberg@euromail.se> Tested-by: Stéphane Chatty <chatty@enac.fr> Signed-off-by: Dmitry Torokhov <dtor@mail.ru> 2009-05-20T22:26:51Z Alessandro Rubini rubini@gnudd.com 2009-05-20T21:39:08Z urn:sha1:03fbdb15c14e9746c63168e3ff2c64b9c8336d33 The second argument of the probe method points to the amba_id structure, so it's better passed with the correct type. None of the current in-tree drivers uses the pointer, so they have only been checked for a clean compile. Change suggested by Russell King. Signed-off-by: Alessandro Rubini <rubini@unipv.it> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 2009-05-12T18:21:24Z Linus Torvalds torvalds@linux-foundation.org 2009-05-12T18:21:24Z urn:sha1:3b4334e200ba50cd02e53b122ef56214b170ea23 * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input: Input: tsc2007 - fix locking in hrtimer handler Input: atkbd - add force release keys quirk for Amilo Xi 3650 Input: ff-memless - fix signed to unsigned bit overflow Input: joydev - blacklist digitizers 2009-05-11T22:35:48Z Thierry Reding thierry.reding@avionic-design.de 2009-05-11T15:36:39Z urn:sha1:705a76d2d22a2824f45f07d023a380293554e989 Now that hrtimers are always running in hard irq context we can't unconditionally enable interrupts at the end of the timer function. Signed-off-by: Thierry Reding <thierry.reding@avionic-design.de> Signed-off-by: Kwangwoo Lee <kwangwoo.lee@gmail.com> Signed-off-by: Dmitry Torokhov <dtor@mail.ru> 2009-05-11T22:30:45Z Adrian Batzill agib@gmx.de 2009-05-11T22:22:16Z urn:sha1:9166d0f620d5dd4a128711bdeedb3e0f534d9d49 Signed-off-by: Adrian Batzill <agib@gmx.de> Signed-off-by: Dmitry Torokhov <dtor@mail.ru>