diff options
| author | Xiaohui Tao <xtao@nvidia.com> | 2012-06-15 11:58:25 -0700 |
|---|---|---|
| committer | Dan Willemsen <dwillemsen@nvidia.com> | 2013-09-14 13:04:53 -0700 |
| commit | 7368b11b9e4c5a81f5fc13a146cd8ad43d65e688 (patch) | |
| tree | df9743b2e254fb3e7ce82f0cfd9bf5a24c26b22c /include/uapi | |
| parent | bd6f854ef6159a61b59d95f87ed1c41007a11d4d (diff) | |
Input: touch: synaptics: Direct Touch kernel files.
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>
Diffstat (limited to 'include/uapi')
| -rw-r--r-- | include/uapi/linux/input.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/include/uapi/linux/input.h b/include/uapi/linux/input.h index 9190bd2e5616..fefb330db869 100644 --- a/include/uapi/linux/input.h +++ b/include/uapi/linux/input.h @@ -930,6 +930,7 @@ struct input_keymap_entry { #define BUS_GSC 0x1A #define BUS_ATARI 0x1B #define BUS_SPI 0x1C +#define BUS_RMI 0x1D /* * MT_TOOL types |