summaryrefslogtreecommitdiff
path: root/drivers/input
AgeCommit message (Collapse)Author
2010-10-21[ARM]: touch: low power mode for touchscreen.Suresh Mangipudi
The late resume of touch was not invoked when display was not turned on. This has been handled now. Bug 740740 (cherry picked from commit ef6a066e3ad9254312660bbb725be9ed49448ffa) Change-Id: Id2f1cd255ed59019fb46778da1b93cbe7aa3b8bb Reviewed-on: http://git-master/r/7973 Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com> Tested-by: Suresh Mangipudi <smangipudi@nvidia.com> Reviewed-by: Narendra Damahe <ndamahe@nvidia.com> Reviewed-by: Bitan Biswas <bbiswas@nvidia.com> Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com> Reviewed-by: Varun Colbert <vcolbert@nvidia.com> Tested-by: Varun Colbert <vcolbert@nvidia.com>
2010-10-19[arm/tegra] kbc: Adding scanning timeout configuration.Laxman Dewangan
Keyboard controller goes to continuous polling mode from wakeup mode if any key is pressed and stay for hw default to 5 second. This parameter was not configurable from odm. It is require to configure this parameter from odm based on platform. Adding support for keeping this time as configurable. The default time still be 5 second if it is not configured from odm. Change-Id: I0fc11cc2a2d64db33b00c048f87081b6181354fa Reviewed-on: http://git-master/r/8644 Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com> Tested-by: Laxman Dewangan <ldewangan@nvidia.com> Reviewed-by: Chun-Hung (Alex) Wu <chuwu@nvidia.com> Tested-by: Chun-Hung (Alex) Wu <chuwu@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Reviewed-by: Varun Colbert <vcolbert@nvidia.com> Tested-by: Varun Colbert <vcolbert@nvidia.com>
2010-10-07[arm/tegra] kbc: Keep KBC to wake mode before LP0 entryLaxman Dewangan
KBC does not behave properly after resume from LP0 if KBC is in continuous mode before entering into LP0. So making sure that KBC should be in wakeup mode before entering to LP0. bug 740263 Change-Id: Ia882dfb034bd9ab87811855f2ac20d26fc9581d8 Reviewed-on: http://git-master/r/7756 Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com> Tested-by: Laxman Dewangan <ldewangan@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
2010-09-30[arm/tegra] kbc: Keep enabling if wake key configured in suspend/resume.Laxman Dewangan
Keep enabling the kc controller only if any of keys are configured as wakeup source during suspend. bug 735233 (cherry picked from commit 13825a46587b0508aa7a43054964b76524d5f2b6) Change-Id: I028965400ee4f96c1460f8e261a2376943384030 Reviewed-on: http://git-master/r/7499 Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com> Tested-by: Laxman Dewangan <ldewangan@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
2010-08-17tegra accelerometer: power management changesVenu Byravarasu
Added suspend and resume functionality to tegra accelerometer, for supporting LP0 on Ventana tested on Ventana-C bug 716080 Change-Id: Ib57b3f2f0d3bec77839f40226f79cd60e222a366 Reviewed-on: http://git-master/r/4836 Tested-by: Venu Byravarasu <vbyravarasu@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
2010-08-16tegra accelerometer: removing threshold settingVenu Byravarasu
As Threshold settings are done in a common place for different accelerometers, removing it. Need to add threshold settings to individual ODM driver based on the need. Bug 721469 Change-Id: I6fe20c4e501208dde9fcf47ac3e31bdf81343efc Reviewed-on: http://git-master/r/5082 Tested-by: Venu Byravarasu <vbyravarasu@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
2010-07-12[Tegra KBC] Added call of NvOdmKbcFilterKeys function from keyboard driver.Victor Ryabukhin
Fix for bug 688807. Function NvOdmKbcFilterKeys (ghost keys filter) was called only from bootloader keyboard driver, but not from OS driver. Fixed. Change-Id: Ibf8c0ccbf393e9c53a08a4cb2f746960bb43e4f8 Reviewed-on: http://git-master/r/3648 Tested-by: Victor Ryabukhin <vryabukhin@nvidia.com> Reviewed-by: Janne Hellsten <jhellsten@nvidia.com>
2010-07-05[arm/tegra] kbc: Configuring kbc controller for LP0.Laxman Dewangan
KBC driver should set the DPD override register before entering in to LP0. Also it should forcefully clear the interrupt status register to clear any pending status. Configuring the kbc rowmask register for allowing the key detection only from wakeup enabled keysi before suspend. Change-Id: I2b1b0e2cd7d0ffc10c2b2f6b2e88f79ab7fb687b Reviewed-on: http://git-master/r/3495 Tested-by: Abhishek Aggarwal <aaggarwal@nvidia.com> Reviewed-by: Narendra Damahe <ndamahe@nvidia.com> Tested-by: Narendra Damahe <ndamahe@nvidia.com> Reviewed-by: Aleksandr Frid <afrid@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
2010-06-25kernel: fixing kernel compilation warningsSachin Nikam
Integrating warning fixes from kernel .29 to .32 Change-Id: I95f0dd92e830f80cae2fb4d3383c9efa845238a9 Reviewed-on: http://git-master/r/3176 Tested-by: Sachin Nikam <snikam@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
2010-06-24tegra accelerometer: reverting threshold setting changesVenu Byravarasu
As these changes are causing power regressions on whistler, reverting them. Tested on: whistler Bug 702317 Change-Id: I025e1f4e7d58f020ced7dadff1707ac403d620ba Reviewed-on: http://git-master/r/3180 Reviewed-by: Bitan Biswas <bbiswas@nvidia.com> Tested-by: Bitan Biswas <bbiswas@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com>
2010-06-22tegra: Run time detection of accelerometer on E1206Venu Byravarasu
Enabled Bosch and Kionix accelerometers together. Added an abstraction layer which would route calls to Bosch or Kionix accelerometer based on run time detection Testing done: observed changes in accelerometer readings when the device is moved. Change-Id: I7cdadb609703d6d0eeabf6e2878adb5f81c43b72 Reviewed-on: http://git-master/r/2753 Tested-by: Venu Byravarasu <vbyravarasu@nvidia.com> Reviewed-by: Hoang Pham <hopham@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com>
2010-06-21[ARM/tegra] Touch driver event size for finger vs cheek events.Michael Hsu
Touch screen drivers must report size value for presses. If size < 0.6, then it is considered finger press. If size > 0.6, then event is considered to be cheek press. The distinction is important in phone mode, because cheek presses are ignored in that mode (the user has the device next to his face in phone mode, and will likely press cheek accidentally against touch screen). Bug 700050 Change-Id: I6792a888f4761672230140e011e9fdc5d60696d3 Reviewed-on: http://git-master/r/2903 Reviewed-by: Michael Hsu <mhsu@nvidia.com> Tested-by: Michael Hsu <mhsu@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com>
2010-06-17nvec_keyboard:Correcting Virtual code for Escape KeySachin Nikam
Correct return value for key 1 is KEY_ESC, not KEY_BACK. Bug 684439 Change-Id: I55db604e79f9f9c3eed4e7dcb4538b096cdc69ae Reviewed-on: http://git-master/r/2566 Tested-by: Sachin Nikam <snikam@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com>
2010-06-16touchscreen: tegra_odm: fix infinite loopVarun Wadekar
fix the infinite loop triggered by multi-touch controllers also, modify the multi-touch loops to loop over the number of fingers supported by the controller, rather than MAX_FINGERS bug 699471 Change-Id: I7c83aa87f9d5c75600cae36c1b40615903a95cec Reviewed-on: http://git-master/r/2747 Reviewed-by: Gary King <gking@nvidia.com> Tested-by: Gary King <gking@nvidia.com>
2010-06-15tegra touch: support more than 2 fingersVarun Wadekar
The kernel touch stack can support a max of 5 fingers at a time. Adding support in the driver to suport 5 fingers too. The touch odm for whistler is broken, hence disable pressure and width support. Change-Id: I9e148bab2efa0116a6513cc8b1cb2ffc2ea27cc8 Reviewed-on: http://git-master/r/2327 Tested-by: Varun Wadekar <vwadekar@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com>
2010-06-15nvec-keyboard: move suspend-resume code to odmBharat Nihalani
Moved NvEc calls from nvec-keyboard driver to keyboard odm kit where all the remaining communication with NvEc resides. Change-Id: I12c528a7b54a02ccef5129d022934da3476e0fcf Reviewed-on: http://git-master/r/2471 Tested-by: Bharat Nihalani <bnihalani@nvidia.com> Reviewed-by: Varun Wadekar <vwadekar@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com>
2010-05-28input: misc: add accelerometer driver for tegra ODM kitGary King
Change-Id: I60f52fc6e91839abb11333e44fb77fdda85841f1 Reviewed-on: http://git-master/r/1830 Reviewed-by: Gary King <gking@nvidia.com> Tested-by: Gary King <gking@nvidia.com>
2010-05-28input: misc: add input driver for tegra scrollwheel ODM kitGary King
Change-Id: I79ca91a26094567207eb55837b908086209cfcf2 Reviewed-on: http://git-master/r/1829 Reviewed-by: Gary King <gking@nvidia.com> Tested-by: Gary King <gking@nvidia.com>
2010-05-27Input: add tegra_odm generic touchscreen driverGary King
Change-Id: Ife43077e4699e38339a637be5a21f1f75fb46543
2010-05-24input: mouse: add tegra nvec mouse driverGary King
Change-Id: Id1bc377bc730198f2482f7ffa6b91d540fa1bc2c
2010-05-19input: keyboard: add keyboard driver for tegra NvEcGary King
Change-Id: I87b0263b80103faa428b9507fa0ca3603cfc8d7d
2010-05-11keyboard/tegra-kbc: remove RM support, fix hang bootup keypressGary King
integrate fixes from 78711168 to move the kbc work into its own workqueue remove the RM_SUPPORT codepath and the (never-will-matter) regulator calls Change-Id: Ief5c1887409b575f907d56c5cf6a0486d69cee07
2010-04-08Input: add keyboard driver for tegra matrix keyboard controllerGary King
Change-Id: I3bb4091a9d0cc1021f822876e2809426f115f038
2010-03-10Merge commit 'v2.6.32.9' into android-2.6.32Arve Hjønnevåg
2010-02-09Input: winbond-cir - remove dmesg spamDavid Härdeman
commit 93fb84b50fe03aabca8d9dea5d3ba521a07e8571 upstream. I missed converting one dev_info call to deb_dbg before submitting the driver. Without this change, a message will be printed to dmesg for each button press if a RC6 remote is used. Signed-off-by: David Härdeman <david@hardeman.nu> Signed-off-by: Dmitry Torokhov <dtor@mail.ru> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2010-02-08Input: synaptics_i2c_rmi: Add irqflags to platform data struct to pass them ↵Rebecca Schultz Zavin
to driver Signed-off-by: Rebecca Schultz Zavin <rebecca@android.com> Signed-off-by: Arve Hjønnevåg <arve@android.com>
2010-02-08Input: synaptics_i2c_rmi: Send new multi touch eventsArve Hjønnevåg
Send both fingers using the new multitouch protocol in addition to the old single finger event and second finger ABS_HAT* hack. The new protocol does not specify how to report up events. To make sure the user-space frameworks can generate up events, we send at least one event where ABS_MT_TOUCH_MAJOR is zero before we stop sending events for a finger. Signed-off-by: Arve Hjønnevåg <arve@android.com>
2010-02-08Input: synaptics_i2c_rmi: Add sensitivity adjust option.Arve Hjønnevåg
Signed-off-by: Arve Hjønnevåg <arve@android.com>
2010-02-08Input: synaptics_i2c_rmi: Add support for panels with has-no-relative-data ↵Arve Hjønnevåg
property. Signed-off-by: Arve Hjønnevåg <arve@android.com>
2010-02-08Input: synaptics_i2c_rmi: Driver for Synaptics Touchscreens using RMI over I2C.Arve Hjønnevåg
Signed-off-by: Arve Hjønnevåg <arve@android.com> Input: synaptics_i2c_rmi: disable_irq -> disable_irq_nosync Also remove duplicate swap macro Signed-off-by: Arve Hjønnevåg <arve@android.com>
2010-02-08input: keychord: Add keychord driverMike Lockwood
This driver allows userspace to receive notification when client specified key combinations are pressed. The client opens /dev/keychord and writes a list of keychords for the driver to monitor. The client then reads or polls /dev/keychord for notifications. A client specified ID for the keychord is returned from read() when a keychord press is detected. Signed-off-by: Mike Lockwood <lockwood@android.com> keychord: fix to build without CONFIG_PREEMPT Change-Id: I911f13aeda4224b6fa57863bc7e8972fec8837fb
2010-02-08input: Add keyreset driver.Arve Hjønnevåg
Add a platform device in the board file to specify a reset key-combo. The first time the key-combo is detected a work function that syncs the filesystems is scheduled. If all the keys are released and then pressed again, it calls panic. Reboot on panic should be set for this to work. Signed-off-by: Arve Hjønnevåg <arve@android.com>
2010-02-08Input: gpio_input: disable_irq -> disable_irq_nosyncArve Hjønnevåg
Signed-off-by: Arve Hjønnevåg <arve@android.com>
2010-02-08Input: gpio_event: Allow multiple input devices per gpio_event deviceArve Hjønnevåg
This is needed to support devices that put non-keyboard buttons in the keyboard matrix. For instance several devices put the trackball button in the keyboard matrix. In this case BTN_MOUSE should be reported from the same input device as REL_X/Y. It is also useful for devices that have multiple logical keyboard in the same matrix. The HTC dream has a menu key on the external keyboard and another menu key on the slide-out keyboard. With a single input device only one of these menu keys can be mapped to KEY_MENU. Signed-off-by: Arve Hjønnevåg <arve@android.com>
2010-02-08Input: gpio_input: Fix keys with keycode 0x100-0x1ffArve Hjønnevåg
KEY_MAX is no longer a power of 2. Signed-off-by: Arve Hjønnevåg <arve@android.com>
2010-02-08Input: Generic GPIO Input device.Arve Hjønnevåg
Supports keyboard matrixces, direct inputs, direct outputs and axes connected to gpios. Signed-off-by: Arve Hjønnevåg <arve@android.com> Signed-off-by: Nick Pelly <npelly@google.com>
2010-02-03input: evdev: Use unique wakelock namesMike Chan
wakelock names are now contain evdev->name and pid Signed-off-by: Mike Chan <mike@android.com>
2010-02-03Input: Use monotonic time for event time stamps.Arve Hjønnevåg
Since wall time can jump backwards, it cannot be used to determine if one event occured before another or for how long a key was pressed. Signed-off-by: Arve Hjønnevåg <arve@android.com>
2010-02-03Input: Hold wake lock while event queue is not empty.Arve Hjønnevåg
Allows userspace code to process input events while the device appears to be asleep. Signed-off-by: Arve Hjønnevåg <arve@android.com>
2010-01-28Input: i8042 - add Dritek quirk for Acer Aspire 5610.Elliott Sales de Andrade
commit e6edbdc52bc0755cbfe0721ca91d4fd87649bc13 upstream. Signed-off-by: Elliott Sales de Andrade <quantum.analyst@gmail.com> Signed-off-by: Dmitry Torokhov <dtor@mail.ru> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2010-01-28Input: i8042 - add Gigabyte M1022M to the noloop listDmitry Torokhov
commit a61cd03827eceefcec19eefc6e1173703fdc5e5d upstream. Gigabyte netbook model M1022M requires i8042.noloop, otherwise AUX port will not detected and the touchpad will not work. Unfortunately chassis type in DMI set to "Other" and thus generic laptop entry does not fire on it. Reported-by: Darryl Bond <dbond@nrggos.com.au> Signed-off-by: Dmitry Torokhov <dtor@mail.ru> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2010-01-28Input: i8042 - remove identification strings from DMI tablesDmitry Torokhov
commit f909b1df0a068f30e252d8dc3e9d45ca25bf266f upstream. The driver does not reference identification strings in DMI tables and since these strings are no longer required by DMI core we can safely remove them and save some memory. Signed-off-by: Dmitry Torokhov <dtor@mail.ru> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2010-01-28Input: ALPS - add interleaved protocol support (Dell E6x00 series)Sebastian Kapfer
commit 1d9f26262aef6d63ff65eba0fd5f1583f342b69b upstream Properly handle version of the protocol where standard PS/2 packets from trackpoint are stuffed into middle (byte 3-6) of the standard ALPS packets when both the touchpad and trackpoint are used together. The patch is based on work done by Matthew Chapman and additional research done by David Kubicek and Erik Osterholm: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/296610 Many thanks to David Kubicek for his efforts in researching fine points of this new version of the protocol, especially interaction between pad and stick in these models. Cc: Andy Isaacson <adi@hexapodia.org> Signed-off-by: Sebastian Kapfer <sebastian_kapfer@gmx.net> Signed-off-by: Dmitry Torokhov <dtor@mail.ru> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2010-01-22Input: pmouse - move Sentelic probe down the listTai-hwa Liang
commit 4a18b3ab6ed537b055e3fcfca64ab870b4f9acf0 upstream. Sentelic probes confuse IBM trackpoints so they stop responding to TP_READ_ID command. See: http://bugzilla.kernel.org/show_bug.cgi?id=14970 Let's move FSP detection lower so it is probed after trackpoint and others, just before we strat probing for Intellimouse Explorer. Signed-off-by: Tai-hwa Liang <avatar@sentelic.com> Signed-off-by: Dmitry Torokhov <dtor@mail.ru> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2009-12-02Input: i8042 - add Dell Vostro 1320, 1520 and 1720 to the reset listAnisse Astier
These laptops often leave i8042 in a wierd state resulting in non- operational touchpad and keyboard. Signed-off-by: Anisse Astier <anisse@astier.eu> Signed-off-by: Dmitry Torokhov <dtor@mail.ru> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-11-16Input: lifebook - fix settings for CF-72Abner Holsinger
Panasonic CF-72 uses 6-byte protocol and does not need to be tied to a particular port. Signed-off-by: Abner Holsinger <9zabner@gmail.com> Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
2009-11-16Input: psmouse - fix breakage introduced by b7802c5c1eaJiri Kosina
Commit b7802c5c1ea ("Input: psmouse - use boolean type") caused the synaptics_hardware variable to be completely useless, as it is constantly set to 'true' throughout the whole psmouse_extensions(). This was caused by the following hunk in the commit in question - int synaptics_hardware = 0; + bool synaptics_hardware = true; which is wrong and causes driver to issue extra reset when falling back to bare PS/2 protocol. Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
2009-11-12Input: psmouse - remove unneeded '\n' from psmouse.proto parameterTakashi Iwai
The get parameter function should return a string without a life-feed. Otherwise you'll see additional empty line in sysfs parameters file. Signed-off-by: Takashi Iwai <tiwai@suse.de> Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
2009-11-12Input: atkbd - restore LED state at reconnectDmitry Torokhov
Even though input core tells us to restore LED state and repeat rate at resume keyboard may be reconnected either by request from userspace (via sysfs) or just by pulling it from the box and plugging it back in. In these cases we still need to restore state ourselves. Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
2009-11-12Input: force LED reset on resumeDmitry Torokhov
We should be sending EV_LED event down to drivers upon resume even in cases when in-kernel state of the LED is off since device could come up with some leds turned on. Reported-and-tested-by: Mikko Vinni <mmvinni@yahoo.com> Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
generated by cgit v1.2.3 (git 2.0.4) at 2026-04-28 07:24:58 +0000