diff options
authorPeter Hutterer <peter.hutterer@who-t.net>2016-04-06 10:14:46 -0700
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2016-04-06 10:23:09 -0700
commit7eb5ca09e48ec671586218ec4f381c43d534f2f4 (patch)
parentd63b0f0c0f19dc8687387ead5a28148dcad1a4b9 (diff)
Input: clarify we want BTN_TOOL_<name> on proximity
This explicitly states behavior we already use for some touchpads and tablet devices. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
1 files changed, 4 insertions, 0 deletions
diff --git a/Documentation/input/event-codes.txt b/Documentation/input/event-codes.txt
index 3f0f5ce3338b..36ea940e5bb9 100644
--- a/Documentation/input/event-codes.txt
+++ b/Documentation/input/event-codes.txt
@@ -173,6 +173,10 @@ A few EV_ABS codes have special meanings:
proximity of the device and while the value of the BTN_TOUCH code is 0. If
the input device may be used freely in three dimensions, consider ABS_Z
+ - BTN_TOOL_<name> should be set to 1 when the tool comes into detectable
+ proximity and set to 0 when the tool leaves detectable proximity.
+ BTN_TOOL_<name> signals the type of tool that is currently detected by the
+ hardware and is otherwise independent of ABS_DISTANCE and/or BTN_TOUCH.
* ABS_MT_<name>:
- Used to describe multitouch input events. Please see