- 05 Mar, 2010 1 commit
-
-
Dan Carpenter authored
It should be >= GC_MAX not > GC_MAX. Signed-off-by:
Dan Carpenter <error27@gmail.com> Signed-off-by:
Dmitry Torokhov <dtor@mail.ru>
-
- 02 Mar, 2010 1 commit
-
-
Ping Cheng authored
Replacing WACOM_PKGLEN_PENABLED with WACOM_PKGLEN_GRAPHIRE since they both represent the same value, 8. This value will be used for both Tablet PC and Bamboo with touch devices. Signed-off-by:
Ping Cheng <pingc@wacom.com> Signed-off-by:
-
- 01 Mar, 2010 1 commit
-
-
Dmitry Torokhov authored
-
- 26 Feb, 2010 2 commits
-
-
Dmitry Torokhov authored
Keycodes in 248 - 254 range were reserved for special needs (scrolling) of atkbd driver. Now that the driver has been switched to use unsigned short keycodes instead of unsigned char we can release this range back into pull. We keep code 255 (ATKBD_KEY_NULL) reserved since users may have been using it to silence keys they do not care about since atkbd silently drops scancodes mapped to this keycode. Signed-off-by: -
Dmitry Torokhov authored
The new key definition is supposed to be used for buttons that initiate WiFi Protected setup sequence: http://en.wikipedia.org/wiki/Wi-Fi_Protected_SetupSigned-off-by:
-
- 25 Feb, 2010 1 commit
-
-
Grazvydas Ignotas authored
The ADS7846/TSC2046 touchscreen controllers can (and usually are) connected to various regulators for power, so add regulator support. Valid regulator will now be required, so boards without complete regulator setup should either disable regulator framework or enable CONFIG_REGULATOR_DUMMY. Signed-off-by:
Grazvydas Ignotas <notasas@gmail.com> Acked-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by:
-
- 24 Feb, 2010 1 commit
-
-
David Härdeman authored
This fixes suspend/resume problem with the driver caused by the fact that ACPI _DIS method would completely power off the SP3 module leaving the output lines (including IRQ lines) in an undefined state. This could cause spurious interrupts and requires reinitializing hardware from scratch during resume. This fixes: http://bugzilla.kernel.org/show_bug.cgi?id=15257Signed-off-by:
David Härdeman <david@hardeman.nu> Signed-off-by:
-
- 22 Feb, 2010 7 commits
-
-
Roy Yin authored
Generaltouch protocol allows for coordinates in [0, 0xffff] range and there are devices reporting coordinates as high as 0x7fff so let's update the driver to reflect that. Signed-off-by:
Roy Yin <yhch@generaltouch.com> Signed-off-by:
-
Dmitry Torokhov authored
Tested-by:
Scott Moreau <oreaus@gmail.com> Signed-off-by:
-
Dmitry Torokhov authored
Tested-by:
-
Dmitry Torokhov authored
Instead of having array bitmasks by type for all gamepads have explicit type field in every pad structure. Tested-by:
-
Dmitry Torokhov authored
Signed-off-by: -
Dmitry Torokhov authored
Fix formatting of 'switch' statements and change the code to stay closer to 80 column limit where it does not hurt code readability. Tested-by:
-
Scott Moreau authored
Add force-feedback support for N64 pads with rumble pak accessory installed. Actually we do not check for the presence of rumble pad but simply assume it is installed and expect the device to ignore FF commands if rumble pak is missing. Signed-off-by:
-
- 20 Feb, 2010 3 commits
-
-
Samu Onkalo authored
When polled input device is opened and closed and there are no other users of polled device, the workqueue is created and destroyed in every open / close operation. It is probable that at some point dynamic allocation of internal parts of the workqueue cause changes to the workqueue. When a work is queued to the workqueue the work struct contains pointers to the workqueue data. If the workqueue has been changed and the work has never been queued to the new workqueue, work-struct contains pointers to the non-existing workqueue. This will cause crash at the work cancellation during device close since cancellation of a work assumes that the workqueue exists. To prevent that, work struct is cleaned up at device close. This keeps work struct clean for the next use. Signed-off-by:
Samu Onkalo <samu.p.onkalo@nokia.com> Signed-off-by:
-
Ping Cheng authored
Devices supporting both pen and touch features share the same product ID, but presented as 2 separate input devices. By adding device type to device name string we can help userspace applications and users differentiate between them. 'Finger' is used for the touch since touch has been used as a suffix by userland hotplugging services. Signed-off-by:
Jason Childs <oblivian@users.sourceforge.net> Signed-off-by:
-
Vasily Khoruzhick authored
Currently driver reports touches when it gets (1 << ts.shift) samples, even if stylus is up, which is incorrect. We should only report coordinates and touch condition when stylus is down. Signed-off-by:
Vasily Khoruzhick <anarsoul@gmail.com> Signed-off-by:
-
- 19 Feb, 2010 3 commits
-
-
Vasily Khoruzhick authored
IRQ should be re-enabled on resume, otherwise driver stops reporting events. Signed-off-by:
-
Dmitry Torokhov authored
Features are not supposed to be modified; devices use their own private copies, so let's mark them const. Signed-off-by: -
Jason Childs authored
Since we mangle data in wacom_features when dealing with certain devices let's use a private (per-device) instance of wacom_features in wacom_wac. This way same product ID can support more than one type of device, such as pen and touch, and not interfere with each other. Signed-off-by:
-
- 18 Feb, 2010 2 commits
-
-
Matthew Garrett authored
Most laptops have keys that are intended to toggle all device state, not just wifi. These are currently generally mapped to KEY_WLAN. As a result, rfkill will only kill or enable wifi in response to the key press. This confuses users and can make it difficult for them to enable bluetooth and wwan devices. This patch adds a new keycode, KEY_RFKILL. It indicates that the system should toggle the state of all rfkillable devices. Signed-off-by:
Matthew Garrett <mjg@redhat.com> Acked-by:
Marcel Holtmann <marcel@holtmann.org> Signed-off-by:
-
Alan Jenkins authored
633aae23 "Input: i8042 - switch to using dev_pm_ops" removed handling for PMSG_THAW, since we do not need to do anything during freeze and thus it was thougt that thaw is not needed as well. However, there is a period when interrupts are kept off, and if key happens to be pressed during that time KBC becomes jammed. To avoid the jam we simply need to poll KBC once during thaw. Signed-off-by:
Alan Jenkins <alan-jenkins@tuffmail.co.uk> Signed-off-by:
-
- 17 Feb, 2010 1 commit
-
-
Magnus Damm authored
Update the Kconfig entry for the sh_keysc driver to enable build on SH-Mobile ARM platforms. Signed-off-by:
Magnus Damm <damm@opensource.se> Signed-off-by:
-
- 11 Feb, 2010 7 commits
-
-
Bastian Blank authored
Get the features information from the driver info of the usb device id structure provided by the caller. The device ids and feature structs are strong coupled using indices. Signed-off-by:
Bastian Blank <waldi@debian.org> Tested-by:
-
Andrew Clayton authored
Even with the correct pin mux settings, you still need to explicitly set the gpio direction. Call gpio_direction_input() after each requested gpio. Signed-off-by:
Andrew Clayton <andrew@digital-domain.net> Signed-off-by:
Mark Somerville <mark@scottishclimbs.com> Tested-by:
H Hartley Sweeten <hsweeten@visionengravers.com> Acked-by:
Daniel Mack <daniel@caiaq.de> Signed-off-by:
-
Magnus Damm authored
Add mode 6 support to the sh_keysc driver. Also update the KYOUTDR mask value to include all 16 register bits. Signed-off-by:
-
Magnus Damm authored
Use bitmaps instead of using 32-bit integers to keep track of the key states. With this change in place the driver supports key pads with more than 32 keys. Signed-off-by:
-
Magnus Damm authored
Update the sh_keysc driver to factor out the register access functions sh_keysc_read(), sh_keysc_write() together with sh_keysc_level_mode(). This makes the code a bit easier to follow. Signed-off-by:
-
Eric Miao authored
Signed-off-by:
Eric Miao <eric.y.miao@gmail.com> Acked-by:
Richard Purdie <rpurdie@rpsys.net> Acked-by:
Pavel Machek <pavel@ucw.cz> Signed-off-by:
-
Eric Miao authored
Provided that now keyboards on these devices are fully supported by generic GPIO based matrix keypad driver, mark these hardcoded and difficult to maintain drivers as deprecated. Signed-off-by:
-
- 08 Feb, 2010 1 commit
-
-
Dmitry Torokhov authored
Set state of the device as "initializing" during and after cleanup to ensure that unsolicited data from the device is not passed on. We especially want to avoid processing new device announcements "0xaa 0x00" that can come up before we perform reconnect operation. Signed-off-by:
-
- 04 Feb, 2010 8 commits
-
-
Mika Westerberg authored
Now gpio-keys input driver exports 4 new attributes to userland through sysfs: /sys/devices/platform/gpio-keys/keys [ro] /sys/devices/platform/gpio-keys/switches [ro] /sys/devices/platform/gpio-keys/disabled_keys [rw] /sys/devices/platform/gpio-keys/disables_switches [rw] With these attributes, userland program can read which keys and switches can be disabled and then disable/enable them as needed. Keys and switches are exported as stringified bitmap of codes (keycodes or switch codes). For example keys 15, 89, 100, 101, 102 are exported as: '15,89,100-102'. Description of the attributes: keys - bitmap of keys which can be disabled switches - bitmap of switches which can be disabled disabled_keys - bitmap of currently disabled keys (bit 1 means disabled, 0 enabled) disabled_switches - bitmap of currently disabled switches (bit 1 means disabled, 0 enabled) Signed-off-by:
Mika Westerberg <ext-mika.1.westerberg@nokia.com> Signed-off-by:
-
Dmitry Torokhov authored
Seeking does not make sense for input interfaces such as evdev and joydev so let's use nonseekable_open to mark them non-seekable. Signed-off-by: -
Dmitry Torokhov authored
Seeking does not make sense for uinput so let's use nonseekable_open to mark the device non-seekable. Signed-off-by: -
Dmitry Torokhov authored
Get rid of blacklist in input handler structure and instead allow handlers to define their own match() method to perform fine-grained filtering of supported devices. Signed-off-by: -
Ondrej Zary authored
Fix urb leak in error path of initialization and make sure we handle errors from initial usb_submit_urb(). Signed-off-by:
Ondrej Zary <linux@rainbow-software.org> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
-
Ondrej Zary authored
Add support for NEXIO (or iNexio) USB touchscreens to usbtouchscreen driver. Tested with NEX170MRT 17" LCD monitor with integrated touchscreen (with xserver-xorg-input-evtouch 0.8.8-1): T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 54 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=02(comm.) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=1870 ProdID=0001 Rev= 1.00 S: Manufacturer=iNexio S: Product=iNexio USB C:* #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr=500mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=02 Prot=00 Driver=(none) E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=255ms I:* If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=(none) E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms No datasheet is available, this was written by capturing some data with SniffUSB in Windows: http://www.rainbow-software.org/linux_files/nexio/Signed-off-by:
-
Ondrej Zary authored
Find input enpoint automatically instead of assuming that the first one is OK. This is needed for devices with multiple endpoints such as iNexio where the first endpoint might be output. Signed-off-by:
-
Ondrej Zary authored
Convert usbtouchscreen from storing usb_device to usb_interface. This is needed for multi-interface touchscreen devices such as iNexio. Signed-off-by:
-
- 01 Feb, 2010 1 commit
-
-
Alberto Panizzo authored
The IMX family of Application Processors is shipped with a Keypad Port supported by this driver. The peripheral can control up to an 8x8 matrix key pad where all the scanning is done via software. The hardware provides two interrupts: one for key presses (KDI) and one for all key releases (KRI). There is also a simple circuit for glitch reduction (said for synchronization) made by two series of 3 D-latches clocked by the keypad-clock that stabilize the interrupts sources. KDI and KRI are fired only if the respective conditions are maintained for at last 4 keypad-clock cycle. Since those circuits are poor for a correct debounce process (the keypad-clock frequency is 32K and bounces longer than 94us are not masked) the driver, when an interrupt arrives, samples the matrix with a period of 10ms until the readins are stable for IMX_KEYPAD_SCANS_FOR_STABILITY times (currently set at 3). After getting stable result appropriate events are sent through the input stack. If some keys are maintained pressed, the driver continues to scan the matrix with a longer period (60ms) to catch possible multiple key presses without overloading the cpu. This process ends when all keys are released. This driver is tested to build in kernel or as a module and follow the specification of Freescale Application processors: i.MX25 i.MX27 i.MX31 i.MX35 i.MX51 especially tested on i.MX31. Signed-off-by:
Alberto Panizzo <maramaopercheseimorto@gmail.com> Signed-off-by:
-
