Re: [PATCH] Documentation: event-codes.txt: clarify we want BTN_TOOL_<name> on proximity
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date: 2016-04-06 17:16:17
On Wed, Feb 24, 2016 at 02:12:03PM +1000, Peter Hutterer wrote:
This explicitly states behavior we already use for some touchpads and tablet devices. Signed-off-by: Peter Hutterer <redacted>
Applied, thank you.
quoted hunk ↗ jump to hunk
--- Documentation/input/event-codes.txt | 4 ++++ 1 file changed, 4 insertions(+)diff --git a/Documentation/input/event-codes.txt b/Documentation/input/event-codes.txt index 3f0f5ce..36ea940 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 instead. + - 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-- 2.5.0
-- Dmitry