- 10 Jul, 2007 40 commits
-
-
Andrew Morton authored
Noted by Fengwei Yin <yfw.kernel@gmail.com> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
Dmitry Torokhov <dtor@mail.ru>
-
Mike Rapoport authored
Signed-off-by:
Mike Rapoport <mike@compulab.co.il> Acked-by:
Rodolfo Giometti <giometti@linux.it> Signed-off-by:
-
Andrew Morton authored
drivers/input/serio/serio_raw.c: In function 'serio_raw_read': drivers/input/serio/serio_raw.c:163: warning: 'c' may be used uninitialized in this function Signed-off-by:
-
Robert P. J. Day authored
Signed-off-by:
Robert P. J. Day <rpjday@mindspring.com> Signed-off-by:
-
Hans de Goede authored
WWW/Homepage key on Microsoft-compatible keyboards generates KEY_WWW when connected via PS/2 port but KEY_HOMEPAGE when connected via USB. This patch changes mapping in atkbd to match one in HID driver. Signed-off-by:
Hans de Goede <j.w.r.degoede@hhs.nl> Acked-by:
Vojtech Pavlik <vojtech@suse.cz> Signed-off-by:
-
Ondrej Zary authored
This patch adds support for IRTOUCHSYSTEMS (or UNITOP) infrared touchscreens. The touchscreen sends data in 8-byte packets. BYTE 0 - unknown meaning, seen only one value: 0x54 BYTE 1 - unknown meaning, 3 lowest bits indicate touch state values seen: 0x81, 0x82 or 0x83 bit 0 = set if the screen is touched and was not touched before (touch bit 1 = set if the screen is touched and was touched (dragging) bit 2 = set if the touch was ended (release) BYTES 2 and 3 - X position, high-order-byte first, range = 0 to 0x0FFF BYTES 4 and 5 - Y position, high-order-byte first, range = 0 to 0x0FFF BYTE 6 - unknown meaning, seen only one value: 0xFF BYTE 7 - unknown meaning, seen only one value: 0x00 Signed-off-by:Ondrej Zary <linux@rainbow-software.org> Signed-off-by:
Daniel Ritz <daniel.ritz@gmx.ch> Signed-off-by:
-
Dmitry Torokhov authored
In preparation for struct class_device -> struct device input core conversion, switch to using input_dev->dev.parent when specifying device position in sysfs tree. Also, do not access input_dev->private directly, use helpers. Signed-off-by: -
Dmitry Torokhov authored
Make the driver report Y/RY up as positive value and down as negative. Also make DPAD mapping the same as classic xpad. Reported-by:
Brian Magnuson <bdmagnuson@gmail.com> Tested-by:
Jan Kratochvil <honza@jikos.cz> Signed-off-by:
-
Adrian Bunk authored
xpad_play_effect() does not need to be global. Signed-off-by:
Adrian Bunk <bunk@stusta.de> Signed-off-by:
-
Jan Kratochvil authored
Signed-off-by:
-
Andi Drebes authored
Signed-off-by:
Andi Drebes <lists-receive@programmierforen.de> Signed-off-by:
-
Ping Cheng authored
Signed-off-by:
Ping Cheng <pingc@wacom.com> Signed-off-by:
-
Hans-Christian Egtvedt authored
Adds support for simulating a mouse using GPIO lines. The driver needs an appropriate platform device to be created by architecture code. The driver has been tested on AT32AP7000 microprocessor using the ATSTK1000 development board. Signed-off-by:
Hans-Christian Egtvedt <hcegtvedt@atmel.com> Signed-off-by:
-
Dmitry Torokhov authored
Signed-off-by: -
Dmitry Torokhov authored
Implement getkeycode and setkeycode methods for the device so EVIOCGKEYCODE and EVIOCSKEYCODE ioctls will work. Signed-off-by: -
Dmitry Torokhov authored
Switch to using input-polldev skeleton instead of implementing polling loop by itself. Signed-off-by: -
Eric Piel authored
Add support to wistron_btns for leds that come with the multimedia keys. Mail and wifi leds are supported, on laptops which have them. Depending on the laptop, wifi subsystem may control just the led, or both the led and the wifi card. Wifi led interface is activated only for the former type of laptops, as the latter type is already managed. Leds are controled by the interface in /sys/class/leds. Signed-off-by:
Eric Piel <eric.piel@tremplin-utc.net> Signed-off-by:
-
Eric Piel authored
Reduces the polling frequency from 10 Hz to 2 Hz, which should be less a burden for laptops wrt energy saving. As it is multimedia keys, 500ms (maximum) of latency should be still fine for the user. In order to keep fluent the feeling when the user is pressing several keys in a raw (such as changing the volume), the frequency is increased for a short duration after a key is pressed. Signed-off-by:
-
Rene van Paassen authored
Update credits and version number to 2.3 Signed-off-by:
Rene van Paassen <rene.vanpaassen@gmail.com> Signed-off-by:
-
Rene van Paassen authored
Function keys (also called macro keys) code corrected. Using a lastMacro variable to keep track of key currently pressed. This ensures proper resetting when dragging the pen in the drawing area or to another key. Also suppress sending pressure reports when over the macro key area. Signed-off-by:
-
Rene van Paassen authored
Now echo "some value" > /sys/......./somefile is also acceptable. Signed-off-by:
-
Rene van Paassen authored
Now the old tool is remembered, and reset when a new tool is selected via the sysfs files. Signed-off-by:
-
Rene van Paassen authored
To get an on - off reporting for proximity, absolute misc reports are used. The mixture of absolute and relative reports is awkward Signed-off-by:
-
Rene van Paassen authored
Added warnings to the points where the tablet probe may fail Signed-off-by:
-
Rene van Paassen authored
Have to use set_bit since some bit values are over 32, and bitwise or won't work on these. To be safe for the future too, use set_bit for all input dev capabilities Signed-off-by:
-
Mark Vytlacil authored
Corrections to relative mode, was looking at wrong byte Signed-off-by:
Mark Vytlacil <mrv@wi.rr.com> Signed-off-by:
-
Rene van Paassen authored
Mouse button defines tested the wrong bits, now fixed Signed-off-by:
-
Rene van Paassen authored
Calculation of proximity bit and of data valid bits were reversed for stylus reports. Signed-off-by:
-
Rene van Paassen authored
Small fix that corrects the documentation on the report byte format produced by the mouse Signed-off-by:
-
Dmitry Torokhov authored
When setting up input device use an array to list all the buttons instead of setting every bit separately. Signed-off-by:
-
Dmitry Torokhov authored
There is no reason to do that, just tell the compiler that we are dealing with signed values in buffer, that's it. Signed-off-by:
-
Dmitry Torokhov authored
Use maps to convert for strings to internal constants and vice versa in aiptek's sysfs attribute methods instead of open-coding it. This results in smaller code that is also easier to maintain. [Rene: fix a typo - stylys instead of stylus] Signed-off-by:
-
Dmitry Torokhov authored
It makes no sense to check for NULL in attribute methods - we do usb_set_intfdata before creating attributes and once attributes have been removed we are guaranteed to not be called. Signed-off-by:
-
Dmitry Torokhov authored
Use attribute group to simplify error handling and reduce code. [Rene: add missing NULL to properly terminate aiptek_attributes] Signed-off-by:
-
Dmitry Torokhov authored
They are already exported by input core; there is no need to do it twice. Signed-off-by:
-
Dmitry Torokhov authored
Do not try to export via sysfs associated event device - it does not work when evdev is a module that is loaded after aiptek; also it pokes too deply into input core internals. Userspace should rely on udev to set up permanent device name for the tablet. Signed-off-by:
-
Aristeu Rozanski authored
Cortron PS/2 Trackballs (700-0001A) report the 4th button using the 4th bit of the first packet (yes, it breaks the standard PS/2 protocol). This patch adds an extra protocol to generate BTN_SIDE based on the 4th bit. There's no way to detect those trackballs using any kind of special sequence, thus the protocol must be activated explicitely by writing into 'protocol' sysfs attribute: echo -n "cortps" > /sys/devices/platform/i8042/serio1/protocol Signed-off-by:
Aristeu Rozanski <arozansk@redhat.com> Signed-off-by:
-
Jan Kratochvil authored
Implementation is using force feedback support for memoryless devices. Signed-off-by:
-
Jan Kratochvil authored
Xbox 360 gamepad is slightly different then the previous model so it has its own version of process_packet method. Detection of this new device relies on USB_DEVICE_INTERFACE_PROTOCOL macro. This device got vendor specific subclass so it can't be matched with USB_INTERFACE_INFO and we need only one interface protocol from four availaible. It means USB_DEVICE can't be used either. Added xpad360_btn structure with additional buttons for x360 gamepad. Added xtype into xpad_device structure to distinguish between different types of xbox devices. Signed-off-by:
-
Jan Kratochvil authored
The USB_DEVICE_INTERFACE_PROTOCOL will allow to match one interface protocol of vendor specific device. This macro is used in patch adding support for xbox360 to xpad.c Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de> Signed-off-by:
-
