Select Git revision
Search by author
- Any Author
- authors
-
Abhiram Balasubramanian abhiram
-
Anton Burtsev
aburtsev
-
Charlie Jacobsen cjacobsen
-
David Detweiler ddetweiler
-
David Johnson johnsond
-
Michael Quigley MichaelQuigley
-
Mike Hibler hibler
-
Robert Ricci ricci
-
Sarah Spall spall
-
Scotty Bauer ScottyB
-
Vikram Narayanan vikram
- Jul 16, 2010
-
-
Henrik Rydberg authored
This patch adds documentation for the ABS_MT_SLOT event and gives examples of how to use the event slot protocol. Reviewed-by:
Ping Cheng <pingc@wacom.com> Signed-off-by:
Henrik Rydberg <rydberg@euromail.se> Signed-off-by:
Dmitry Torokhov <dtor@mail.ru>
-
Henrik Rydberg authored
With the rapidly increasing number of intelligent multi-contact and multi-user devices, the need to send digested, filtered information from a set of different sources within the same device is imminent. This patch adds the concept of slots to the MT protocol. The slots enumerate a set of identified sources, such that all MT events can be passed independently and selectively per identified source. The protocol works like this: Instead of sending a SYN_MT_REPORT event immediately after the contact data, one sends an ABS_MT_SLOT event immediately before the contact data. The input core will only emit events for slots with modified MT events. It is assumed that the same slot is used for the duration of an initiated contact. Acked-by:
Chase Douglas <chase.douglas@canonical.com> Acked-by:
Rafi Rubin <rafi@seas.upenn.edu> Signed-off-by:
-
- Jul 15, 2010
-
-
Oliver Neukum authored
This implements reset_resume() by splitting init into allocations of private data structures and device initializations. Device initializations are repeated upon reset_resume. Signed-off-by:
Oliver Neukum <oneukum@suse.de> Tested-by:
Petr Štetiar <ynezz@true.cz> Tested-by:
Ondrej Zary <linux@rainbow-software.org> Signed-off-by:
-
Oliver Neukum authored
This implement USB autosuspend while the device is opened for devices that do remote wakeup with a fallback to open/close for those devices that don't. Devices that require the host to constantly poll them are never autosuspended. Signed-off-by:
-
Oliver Neukum authored
This implements basic support for suspend & resume. Signed-off-by:
-
- Jul 14, 2010
-
-
Joonyoung Shim authored
The chip's full name is AT42QT602240 or ATMXT224. This is a capacitive touchscreen supporting 10-contact multitouch and using I2C interface. Signed-off-by:
Joonyoung Shim <jy0922.shim@samsung.com> Acked-by:
-
Dmitry Torokhov authored
The dev->getkeycode() method expects unsigned argument. Signed-off-by: -
Lars-Peter Clausen authored
This patch adds a simple driver which allows to use pwm based beepers (for example piezo elements) as a pcspkr-like device. Signed-off-by:
Lars-Peter Clausen <lars@metafoo.de> Signed-off-by:
-
- Jul 13, 2010
-
-
Christoph Fritz authored
Dance pads don't have any axes/sticks, only buttons for directions. For example buttons like left+right will get triggered at once, an axis can't handle this anyway. So this patch adds a module parameter named "sticks_to_null" for unknown devices. A known dance pad makes use of it by changing to a new mapping-option named DANCEPAD_MAP_CONFIG. Other tested devices may follow by adding this mapping-option too. Some buttons of xpad-devices are addressing mouse-buttons instead of gamepad-buttons. This gets fixed too. Signed-off-by:
Christoph Fritz <chf.fritz@googlemail.com> Signed-off-by:
-
Dmitry Torokhov authored
This ensures consistent prefixes on all messages emitted by the driver. Signed-off-by: -
Axel Lin authored
To improve readability, this patch fixes mixing acpi_status and int for return value. Signed-off-by:
Axel Lin <axel.lin@gmail.com> Signed-off-by:
-
Axel Lin authored
The owner field provides the link between drivers and modules in sysfs. After setting the owner field, we can see which module provides which driver and vice versa by looking at /sys/bus/acpi/drivers/Atlas ACPI/module and /sys/module/atlas_btns/drivers/acpi:Atlas ACPI Signed-off-by:
-
- Jul 08, 2010
-
-
Markus Lehtonen authored
Power button is not hot-pluggable so we can save some memory by using __init. Signed-off-by:
Markus Lehtonen <markus.lehtonen@nokia.com> Signed-off-by:
-
- Jul 04, 2010
-
-
Joonyoung Shim authored
This adds support for MELPAS MCS5000/MSC5080 touch key controllers. Signed-off-by:
-
- Jul 03, 2010
-
-
Oliver Neukum authored
As the kernel has no way to know whether a key was released while the system was asleep, keys need to be reported released as the system is resumed, lest autorepeat set in. Signed-off-by:
-
Anatolij Gustschin authored
ADS7845 is a controller for 5-wire touch screens and somewhat different from 7846. It requires three serial communications to accomplish one complete conversion. Unlike 7846 it doesn't allow Z1-/Z2- position measurement. The patch extends the ads7846 driver to also support ads7845. The packet struct is extended to contain needed command and conversion buffers. ads7846_rx() and ads7846_rx_val() now differentiate between 7845 and 7846 case. ads7846_probe() is modified to setup ads7845 specific command and conversion messages and to switch ads7845 into power-down mode, since this is needed to be prepared to respond to pendown interrupts. Signed-off-by:
Anatolij Gustschin <agust@denx.de> Signed-off-by:
-
Dmitry Torokhov authored
Tested-by:
-
Dmitry Torokhov authored
Suspending and resuming the device should be separate from enabling and disabling it through sysfs attribute and thus should not alter ac->disabled flag. [michael.hennerich@analog.com: various fixups] Tested-by:
Michael Hennerich <michael.hennerich@analog.com> Signed-off-by:
-
Michael Hennerich authored
Some input events users such as Android require BTN_TOUCH events. Implement EV_KEY/BTN_TOUCH and make sure that the release event is not erroneous scheduled without a preceding valid touch. Avoid duplicated BTN_TOUCH events, even though input core filters them. Signed-off-by:
-
Michael Hennerich authored
Signed-off-by:
-
Michael Hennerich authored
Avoid additional addressing overhead incurred by word_data transfers. Signed-off-by:
Mike Frysinger <vapier@gentoo.org> Signed-off-by:
-
Dmitry Torokhov authored
Tested-by:
-
Mike Frysinger authored
The ad7879 driver is using the old bus method of only supporting one at a time (I2C or SPI). So refactor it like the other input drivers that support multiple busses simultaneously. Signed-off-by:
-
- Jun 30, 2010
-
-
Dmitry Torokhov authored
Tested-by:
-
Dmitry Torokhov authored
-
- Jun 28, 2010
-
-
Dan Carpenter authored
We reuse the "i" variable later on so if we goto fail3 or fail4 then "i" will be set to the wrong thing and cause a crash. Signed-off-by:
Dan Carpenter <error27@gmail.com> Signed-off-by:
-
Grazvydas Ignotas authored
gpiolib now has debounce support added in .35, so let's make use of it. This allows to use hardware GPIO debouncing on some platforms like OMAP. In case gpiolib debounce setup fails for some GPIO, the driver will fall back to timer based debouncing, which is what it used before. Signed-off-by:
Grazvydas Ignotas <notasas@gmail.com> Signed-off-by:
-
Petr Štetiar authored
The device is handled by usbtouchscreen driver. Signed-off-by:
Jiri Kosina <jkosina@suse.cz> Signed-off-by:
-
Petr Štetiar authored
This patch adds support for the ET&T TC4UM 4-wire USB touchscreen controller and tries to reuse the bits for TC5UH controller in kernel already. Data interface is same. Tested-by:
Roger Pueyo Centelles <rogerpueyo@rogerpueyo.com> Signed-off-by:
-
Anatolij Gustschin authored
On some platforms, for example with GPIO interrupts on mpc5121, it is not possible to configure falling edge interrupts. Specifying irq trigger type in platform data structure allows using ads7846 driver on such platforms. Signed-off-by:
-
Ping Cheng authored
Add support for the two new devices: DTU2231 and DTU1631. Signed-off-by:
-
Axel Lin authored
select_keymap() calls copy_keymap() to allocate a memory for keymap. This patch adds a missing kfree(keymap) in wb_module_init error path. Signed-off-by:
-
- Jun 25, 2010
-
-
Michael Hennerich authored
Signed-off-by:
-
Michael Hennerich authored
This is a driver for the ADXL345/346 Three-Axis Digital Accelerometers. Signed-off-by:
Chris Verges <chrisv@cyberswitching.com> Signed-off-by:
Luotao Fu <l.fu@pengutronix.de> Signed-off-by:
Barry Song <barry.song@analog.com> Signed-off-by:
-
- Jun 24, 2010
-
-
Xiaolong CHEN authored
A column or row configured as a GPI can be programmed to be part of the key event table and therefore also capable of generating a key event interrupt. A key event interrupt caused by a GPI follows the same process flow as a key event interrupt caused by a key press. GPIs configured as part of the key event table allow single key switches and other GPI interrupts to be monitored. As part of the event table, GPIs are represented by the decimal value 97 (0x61 or 1100001) through the decimal value 114 (0x72 or 1110010). See table below for GPI event number assignments for rows and columns. GPI Event Number Assignments for Rows Row0 Row1 Row2 Row3 Row4 Row5 Row6 Row7 97 98 99 100 101 102 103 104 GPI Event Number Assignments for Cols Col0 Col1 Col2 Col3 Col4 Col5 Col6 Col7 Col8 Col9 105 106 107 108 109 110 111 112 113 114 Signed-off-by:
Xiaolong Chen <xiao-long.chen@motorola.com> Signed-off-by:
Yuanbo Ye <yuan-bo.ye@motorola.com> Signed-off-by:
Tao Hu <taohu@motorola.com> Acked-by:
-
- Jun 23, 2010
-
-
Henrik Rydberg authored
When the client buffer is very small and wraps around a lot, it may well be that a write increases the head such that head == tail. If this happens between the point where a poll is triggered and the actual data is being read, there will be no data to read. This is confusing to applications, which might end up closing the file. This patch solves the problem by making sure the client buffer is never empty after writing to it. Signed-off-by:
-
Henrik Rydberg authored
The MT devices produce a lot of data. Tell the underlying input device approximately how many events will be sent per synchronization, to allow for better buffering. The number is a template based on continuously reporting details for each finger on a single hand. Signed-off-by:
-
Henrik Rydberg authored
The MT devices produce a lot of data. Tell the underlying input device approximately how many events will be sent per synchronization, to allow for better buffering. The number is a template based on continuously reporting details for each finger on a single hand. Signed-off-by:
-
Henrik Rydberg authored
Some devices, in particular MT devices, produce a lot of data. This may lead to overflowing of the event queues in evdev driver, which by default are fairly small. Let the drivers hint the average number of events per packet generated by the device, and use that information when computing the buffer size evdev should use for the device. Signed-off-by:
-
Henrik Rydberg authored
Allocate the event buffer dynamically, and prepare to compute the buffer size in a separate function. This patch defines the size computation to be identical to the current code, and does not contain any logical changes. Signed-off-by:
-
