| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Eventhub defines two entries:
MSC_ANDROID_TIME_SEC 0x6
MSC_ANDROID_TIME_USEC 0x7
to pass the timestamp from the linux kernel to android
if the input devices have a better concetp of the time.
These two entries conflict with MSC_ACTIVITY which is
used for CPU_BOOST, which causes the first touc does not
work after lp0. Add the two entries in input.h to match
with android layer.
Bug 1354400
Change-Id: I5cc9b2605db609cebad96ad1b95433fa333e77f7
Signed-off-by: Xiaohui Tao <xtao@nvidia.com>
Reviewed-on: http://git-master/r/266219
Reviewed-by: Mitch Luban <mluban@nvidia.com>
Tested-by: Mitch Luban <mluban@nvidia.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Code drop from synaptics
Below is the detailed description of the change:
* Support for multiple RMI4 devices has been added.
* The Kconfig options have been further simplified. CONFIG_RMI4_BUS and
CONFIG_RMI4_GENERIC are replaced by a single control, CONFIG_RMI4_CORE.
You'll need to update your defconfig file appropriately.
* some debugfs and sysfs files have moved around. If you have tools or
scripts that depend on these files, you'll need to update the paths.
* The driver_name field of rmi_device_platform_data has been removed, as
it was no longer necessary.
* Polling support has been added. Polling works on I2C and SPIv1. It
does not work for SPIv2, since that requires a working ATTN line.
* A sensor_type field has been added to the F11 per-sensor platform
data. This allows you to specify whether the device is touchscreen or
touchpad type sensor in cases where the register map does not allow this
to be determined programmatically.
* F11 platform data has been updated to a per-sensor basis (remember that
a single F11 module might have more than one 2D sensor attached to it).
* F11 virtual button maps have been switched to a per-sensor basis.
* F11 Type B support is always on, and removed from Kconfig. Per-sensor
platformdata is provided if you need to force Multifinger Type A input.
* IMPORTANT: the RMI4 driver has been converted over to the Linux kernel
bus and driver model. This means that the sysfs file structure has changed.
Some files have moved to debugfs, and for remaining files, the sysfs tree
structure has changed. Refer to Documentation/ABI/testing/debugfs-rmi4 and
sysfs-rmi4 for full details.
* ALSO IMPORTANT: The Kconfig options have been simplified. Several have
been eliminated, and others have been consolidated. Please consult Kconfig
and make any necessary related changes to your kernel configuration.
* ATTN interrupts are not enabled until the F01 function driver is bound to
the sensor. This should eliminate spurious interrupts that were seen during
the system bootup process.
Bug 960856
Bug 1253719
Change-Id: I773ec9210e0d6c7e8f03d551ca61bbda156080f7
Signed-off-by: Xiaohui Tao <xtao@nvidia.com>
Reviewed-on: http://git-master/r/130310
Reviewed-by: Seema Khowala <seemaj@nvidia.com>
Tested-by: Seema Khowala <seemaj@nvidia.com>
Reviewed-by: Thomas Cherry <tcherry@nvidia.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Input devices which depends on host processor for converting raw
samples to input event needs to report early event so that CPU
frequency governor can act to boost process of converting raw
samples to input event data. Direct touch technology based
device is an example where computation happens on CPU instead
of dedicated controller.
Bug 1229219
Change-Id: I404fb30e2a05f8092d194825488db017e7e935af
Signed-off-by: Yogish Kulkarni <yogishk@nvidia.com>
Reviewed-on: http://git-master/r/196737
(cherry picked from commit 39614533cbc98531d5ecaca08cbb0145161d2eb3)
Reviewed-on: http://git-master/r/200761
GVS: Gerrit_Virtual_Submit
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add an ioctl, EVIOCSSUSPENDBLOCK, to enable a wakelock that will block
suspend while the event queue is not empty. This allows userspace code to
process input events while the device appears to be asleep.
The current code holds the wakelock for up 5 seconds for every input
device and client. This can prevent suspend if sensor with a high data
rate is active, even when that sensor is not capable of waking the
device once it is suspended.
Change-Id: I624d66ef30a0b3abb543685c343382b8419b42b9
Signed-off-by: Arve Hjønnevåg <arve@android.com>
|
| |\
| |
| |
| |
| | |
Merge with mainline to bring in module_platform_driver_probe() and
devm_ioremap_resource().
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Some devices provides the actual timestamp (hid_dg_scan_time in win8 ones)
computed by the hardware itself. This value is global to the frame and is
not specific to the multitouch protocol.
Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
Reviewed-by: Henrik Rydberg <rydberg@euromail.se>
Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
|
| |/
|
|
|
|
|
| |
Entertainment systems used in aircraft need additional keycodes for their
Passenger Control Units, so let's add them.
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
|
|
|
Signed-off-by: David Howells <dhowells@redhat.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Michael Kerrisk <mtk.manpages@gmail.com>
Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Acked-by: Dave Jones <davej@redhat.com>
|
