summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorCharlie Mooney <charliemooney@chromium.org>2015-03-20 17:40:17 +0100
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2015-03-20 17:45:28 +0100
commita736775db683174269c65c7c5cc8e5ee534e7681 (patch)
tree7771241d9f3e0eb75125ea5f16c1877a8cd78995 /include
parentRevert "Input: synaptics - use dmax in input_mt_assign_slots" (diff)
downloadlinux-a736775db683174269c65c7c5cc8e5ee534e7681.tar.xz
linux-a736775db683174269c65c7c5cc8e5ee534e7681.zip
Input: add MT_TOOL_PALM
Currently there are only two "tools" that can be specified by a multi-touch driver: MT_TOOL_FINGER and MT_TOOL_PEN. In working with Elan (The touch vendor) and discussing their next-gen devices it seems that it will be useful to have more tools so that their devices can give the upper layers of the stack hints as to what is touching the sensor. In particular they have new experimental firmware that can better differentiate between palms vs fingertips and would like to plumb a patch so that we can use their hints in higher-level gesture soft- ware. The firmware on the device can reasonably do a better job of palm detection because it has access to all of the raw sensor readings as opposed to just the width/pressure/etc that are exposed by the driver. As such, the firmware can characterize what a palm looks like in much finer-grained detail and this change would allow such a device to share its findings with the kernel. Signed-off-by: Charlie Mooney <charliemooney@chromium.org> Acked-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'include')
-rw-r--r--include/uapi/linux/input.h3
1 files changed, 2 insertions, 1 deletions
diff --git a/include/uapi/linux/input.h b/include/uapi/linux/input.h
index a1d7e931ab72..2320b0ce7579 100644
--- a/include/uapi/linux/input.h
+++ b/include/uapi/linux/input.h
@@ -972,7 +972,8 @@ struct input_keymap_entry {
*/
#define MT_TOOL_FINGER 0
#define MT_TOOL_PEN 1
-#define MT_TOOL_MAX 1
+#define MT_TOOL_PALM 2
+#define MT_TOOL_MAX 2
/*
* Values describing the status of a force-feedback effect