Age | Commit message (Collapse) | Author |
|
The hardware gives you 0 as the pressure even for
valid touches. Pass a default value if you get
pressure value outside limits from the hardware during
a 'press'.
Pass pressure as 0, for a 'release'.
Change-Id: Id858240464474d3c18e4bae9768f41327c5d4124
Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
|
|
When 2nd multi touch is removed, release point is (0,0) point.
To correct this, in removing 2nd multi touch,
we send last touched position of 2nd multi touch.
And this removes noise touch event and joystick event also.
Bug 896919
Change-Id: Icccaa3ccc28e613565ce696339b83d60335b344a
Reviewed-on: http://git-master/r/64008
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
Rebase-Id: Re3c488cd60c5b02ec43fa8f3e700dc93afbff043
|
|
Change-Id: I08eb7b5ad1c70b84ff40ba75a29913b61634d0f0
Signed-off-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-on: http://git-master/r/48786
Reviewed-by: Daniel Willemsen <dwillemsen@nvidia.com>
Rebase-Id: Rc7ac5d5153d845c8be10dbe79f57083fb1919760
|
|
In the case where early suspend/resume is enabled, prevent
suspend/resume from being called twice. Removing the
default suspend/resume handlers while early suspend/resume is
enabled prevents the double suspend/resume from occurring.
BUG 843934
Original-Change-Id: I2e014f7a79db524cbe9d5b8b934c8f42216a8ad5
Reviewed-on: http://git-master/r/38576
Tested-by: Krishna Yarlagadda <kyarlagadda@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Robert R Collins <rcollins@nvidia.com>
Tested-by: Robert R Collins <rcollins@nvidia.com>
Rebase-Id: R6c38a345206679eb2ee5ca279d0ffa922c3f8744
|
|
Add early suspend/resume functionality to Atmel touch driver.
0W suspend.
Early suspend/resume functions written and provided by
Atmel Corporation.
BUG 826854
Original-Change-Id: I58d5abacff20df9d3027c960021e94298e31b8a6
Reviewed-on: http://git-master/r/35286
Reviewed-by: Robert R Collins <rcollins@nvidia.com>
Tested-by: Robert R Collins <rcollins@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Daniel Willemsen <dwillemsen@nvidia.com>
Rebase-Id: R1364d26f0c95bdb9e650e3231ac254242a9b3349
|
|
Conflicts:
arch/arm/mach-tegra/Kconfig
arch/arm/mach-tegra/board-ventana.c
drivers/misc/Kconfig
drivers/video/tegra/dc/hdmi.c
Signed-off-by: Dan Willemsen <dwillemsen@nvidia.com>
|
|
Video playback would like to save power by slowing touchscreen
scanning. This change adds a SysFS interface to allow the
scan rate to be programmed by the video display interface.
SysFS location:
/sys/devices/platform/tegra-i2c.1/i2c-1/1-005a/slowscan_enable
Read functions:
cat slowscan_enable (returns current register status)
Write functions:
0 - Disable slowscan
1 - Enable slowscan
2 N - Program actv_cycle_time with value of N
3 N - Program idle_cycle_time with value of N
4 N - Program actv2idle timeout with value of N (seconds * 10)
Bug 891993
Change-Id: Ib11b544019f3a78290785502e7209b8cbd985852
Reviewed-on: http://git-master/r/65006
Reviewed-by: Robert Collins <rcollins@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
Rebase-Id: Re4398871d4964d366f0dbdd856a7953600577dea
|
|
In order to save system power, we should cut the power to the
touchscreen controller. Older versions of our TS driver did this.
This feature was accidentally removed during a recent driver
update.
Bug 891979
Change-Id: I4bf9333832af65c00b8b10cc8191f4d26aad04e4
Reviewed-on: http://git-master/r/65005
Reviewed-by: Robert Collins <rcollins@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
Rebase-Id: R370b26e990a5f129ea0f8e73e9b7178bd85b79e5
|
|
Updated to new Atmel touch driver. Added sysfs interface to
allow Config-UI applications to run.
Primary changes:
* Add sysfs interface to allow user applications access to the
touchscreen controller register interface. Required by
Config-UI utility.
* Fixed bug in stop/start functions that would prevent TS
from working with encrypted filesystems.
* Fix logic error that could cause a deadlock condition during
LP0 resume.
Change-Id: If25260e60843e3c3bb3a9818ed9146ea78c39902
Reviewed-on: http://git-master/r/65004
Reviewed-by: Robert Collins <rcollins@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
Rebase-Id: R9bde02eeeae3a899e18d17b5ff26cac371729cb0
|
|
These changes have no effect if CONFIG_GCOV_KERNEL is not set in
defconfig. It is easier to trigger GCOV for kernel if this patch
is in by only setting the before mentioned flag.
Change-Id: I8aade309da2da62c4b3889bd84e4123ba8f182da
Signed-off-by: Juha Tukkinen <jtukkinen@nvidia.com>
Reviewed-on: http://git-master/r/62999
Reviewed-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
Tested-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
Rebase-Id: R4c238f707f1db600f188ae83426336753992b7be
|
|
The scan timeout of the continuous mode can be calculated based on
init delay, repeat delay, debounce count and number of active row.
It also depends on how many scan need to be done before kbc change
the mode from continuous to wakeup mode.
Providing mechanism to select the scan count from platform data
and calculating the scan timeout count based on above parameters.
bug 876712
Reviewed-on: http://git-master/r/62591
(cherry picked from commit 3360ed5be86a2afd6716bc5227cc39657efd35b2)
Change-Id: Ib9dc96b1cc201b7af0bd62a3ec7fe9a80791d796
Reviewed-on: http://git-master/r/63229
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
Tested-by: Laxman Dewangan <ldewangan@nvidia.com>
Rebase-Id: Rbcb685d34c5d00ebf1c79d356eb63e4584075447
|
|
-Set only REQUIRED row and column configuration register to
PROPER values to avoid continuously generating KBC input events.
-Use *enable* field in pin_cfg, to check GPIO_x_ROW_EN register
should be set or clear.
bug 889620
Change-Id: I91990156c300605c214e7e393edf14fbced1573d
Reviewed-on: http://git-master/r/59153
Reviewed-by: Shridhar Rasal <srasal@nvidia.com>
Tested-by: Shridhar Rasal <srasal@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Rebase-Id: R03e9deb839fc21c1ea66fc81ae6601155b8e8d4d
|
|
in some situations
BUG 868649
Reviewed-on: http://git-master/r/50598
(cherry picked from commit ad1dbe0eda931f813b20d75400daaa9edf18c82a)
Change-Id: I29f353687c499ff830e98fcf038d8a786dc5608b
Reviewed-on: http://git-master/r/54841
Reviewed-by: Joel Kenny <jkenny@nvidia.com>
Reviewed-by: Robert Collins <rcollins@nvidia.com>
Reviewed-by: Dan Willemsen <dwillemsen@nvidia.com>
Tested-by: Joel Kenny <jkenny@nvidia.com>
Rebase-Id: Rdde94e071f4a27250eccad562c819ca2f537ffcd
|
|
This reverts commit baafb435372dd48e3854028aec669effae957c9e.
Rebase-Id: Re9bd7135ad63df297876341431cad65fa12a838a
|
|
Prevents touchscreen hangs during initial TS boot, and TS resume.
BUG 847725
BUG 845156
BUG 846711
Original-Change-Id: Ia853574e4b2422eb9368fe37eaf7457bd4022df8
Reviewed-on: http://git-master/r/40261
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
Rebase-Id: Rc1de4685a4e85d761097142b39f2a672846b8c44
|
|
* Fix suspend/resume bug to prevent unecessary i2cinterrupts when suspended.
* Change input device name to match NVDA IDC name.
* Add I2C address defines.
* Change "printk" to "dev_info" function calls.
BUG 826854
Original-Change-Id: Ic1b25bc469b86d8a26e876e80973597d9f6fb107
Reviewed-on: http://git-master/r/35285
Reviewed-by: Robert R Collins <rcollins@nvidia.com>
Tested-by: Robert R Collins <rcollins@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Daniel Willemsen <dwillemsen@nvidia.com>
Rebase-Id: Rcba51c79d3c004372c0be18538f14f56a2249bc0
|
|
Integrate changes made by Atmel. These changes are in addition to
mainline driver.
NOTE: Driver will compile as a stand-alone.
BUG 826854
Original-Change-Id: If13688d90d97b71718576f3fb756496f57a965d7
Reviewed-on: http://git-master/r/35280
Reviewed-by: Robert R Collins <rcollins@nvidia.com>
Tested-by: Robert R Collins <rcollins@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Daniel Willemsen <dwillemsen@nvidia.com>
Rebase-Id: Reb8ae14299d248c0ce69e52b26a8816d1a0ee057
|
|
For the key connected directly to interrupt keys, there is continuous
interrupt from key pressed. The generation of interrupt stops only
when key is released.
To handle this case, reporting the key press in first interrupt and key
release event if there is no interrupt for sometime. This time is configurable
from platform data.
bug 814005
Original-Change-Id: I56345ca68bd227e48cf31b1f54a0deac43bf900c
Reviewed-on: http://git-master/r/28065
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
Tested-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Ramachandrudu Kandhala <rkandhala@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Original-Change-Id: I83d04992fe29c9a472a79e900b8083475c1ddf40
Rebase-Id: R62a01548c16a78033337dcfe35d391210412c3f2
|
|
Original-Change-Id: I2ffeaf6f8dfeb279b40ca6f69f6c9157401a746a
Rebase-Id: R056056997b4913133216474f863fc17c7f69878b
|
|
Adding keys support which are directly connected to interrupt lines.
Original-Change-Id: Ib26c06b170b82f4745e758be80b3e04122ad1d6c
Reviewed-on: http://git-master/r/22069
Tested-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
Original-Change-Id: I3921cc88f32558282654fbd36243b4b0b3574133
Rebase-Id: Rd7954ff7c2e0167a6a4765ff2f08494b9d0eba14
|
|
During resume, gpio-keys does not get updated state of gpios which
fails to report wakeup key event. Update resume routine to report
key event based on wakeup source.
BUG 745149
Original-Change-Id: Iff7a9b431f9da8d226c8d3cd522725c3049fef07
Reviewed-on: http://git-master/r/17455
Tested-by: Nitin Kumbhar <nkumbhar@nvidia.com>
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Rebase-Id: Rde589cdb4f74683e9ea46933c7f949da16c5f884
|
|
Reports Scroll keys:
- Press
- Scrollup
- Scrolldown
Original-Change-Id: I47f6ca3d7b5bed4aa7441634850881df7066fce7
Reviewed-on: http://git-master/r/13618
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
Rebase-Id: R7c42f5468e8a89fb4881abd7ef7d314740f99144
|
|
Change-Id: I1adc2bb646269f17480718a7efb3dc14e6325fbc
Signed-off-by: Gary King <gking@nvidia.com>
|
|
Conflicts:
arch/arm/mm/cache-l2x0.c
drivers/misc/Kconfig
drivers/misc/Makefile
Signed-off-by: Dan Willemsen <dwillemsen@nvidia.com>
|
|
Change-Id: I29ccb32e795c5c3e4c51c3d3a209f5b55dfd7d94
Signed-off-by: Dima Zavin <dima@android.com>
|
|
If there is a full packet in the buffer, and we overflow that buffer
right after checking for that condition, it would have been possible
for us to block indefinitely (rather, until the next full packet) even if
the file was marked as O_NONBLOCK.
Change-Id: Icd0f59f8cc98392be4c4d13bd45b5cf94317eb5a
Signed-off-by: Dima Zavin <dima@android.com>
|
|
Change-Id: I5f0da721f74e5de111cffc7e7b375b72dd80e530
Signed-off-by: Dima Zavin <dima@android.com>
|
|
Without this, it was possible for the reader to get ahead of packet_head.
If the the input device generated a partial packet *right* after the
reader got ahead, then we can get into a situation where the device is
marked readable but read always returns 0 until the next packet is
finished (i.e a SYN is generated by the input driver).
This situation can also happen if we overflow the buffer while a reader
is trying to read an event out.
Change-Id: If01ab371bc7de1bf1f90c122dcc5a29242b01a09
Signed-off-by: Dima Zavin <dima@android.com>
|
|
Add a board file option to gpio_input devices to make
calling enable_irq_wake conditional. Also disable the
wake irq when removing the device.
Change-Id: If933b9d3a751d89fa95ae3b7f739dfe70fcb23c8
Signed-off-by: Mike J. Chen <mjchen@sta.samsung.com>
|
|
Signed-off-by: jeffbrown@android.com
Change-Id: Ie170960df3c8ab4833ed686135dc8575cb9f2d48
|
|
Signed-off-by: jeffbrown@android.com
Change-Id: I9bd2437503b48bf37f4d93505ccd2806e4aab977
|
|
Change-Id: Ib8dd0ab6554e6b0e3798bf75d41f77ea0b20b8de
Signed-off-by: Colin Cross <ccross@android.com>
|
|
Change-Id: I68e5451fef2e6f08bf1035077ea999e34a619f87
Signed-off-by: Colin Cross <ccross@android.com>
|
|
Change-Id: Ief1ef44d98a197e5b457f5e8617c413e76e3c6d2
Signed-off-by: Benoit Goby <benoit@android.com>
|
|
Change-Id: Ibb3dda05772b2e89d7b2646689944d309cb1f74e
Signed-off-by: Colin Cross <ccross@android.com>
|
|
lvl trigger irqs
Change-Id: Ie378600668500dcffeaaddeaba3628e5c2141aa4
Signed-off-by: Dima Zavin <dima@android.com>
|
|
If the gpio did not exist it would crash in gpiolib.
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|
|
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
to driver
Signed-off-by: Rebecca Schultz Zavin <rebecca@android.com>
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|
|
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>
|
|
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|
|
property.
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|
|
Signed-off-by: Arve Hjønnevåg <arve@android.com>
Input: synaptics_i2c_rmi: disable_irq -> disable_irq_nosync
Also remove duplicate swap macro
Change-Id: I77266431ba5c267a5d92c4bdc2f127a5297065a8
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|
|
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
|
|
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.
Change-Id: I9d54283ca1fba45e4b1ae1a407524cdda8171143
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|
|
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|
|
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>
|
|
KEY_MAX is no longer a power of 2.
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|
|
Supports keyboard matrixces, direct inputs, direct outputs and axes connected to gpios.
Change-Id: I5e921e6e3a1cc169316ee3b665f4cc21b5735114
Signed-off-by: Arve Hjønnevåg <arve@android.com>
Signed-off-by: Nick Pelly <npelly@google.com>
|
|
wakelock names are now contain evdev->name and pid
Signed-off-by: Mike Chan <mike@android.com>
|