From: Peter Hutterer <peter.hutterer@who-t.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Charles Mooney <charliemooney@google.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Henrik Rydberg <rydberg@bitmath.org>,
Linux Input <linux-input@vger.kernel.org>
Subject: [PATCH] Documentation: event-codes.txt: clarify we want BTN_TOOL_<name> on proximity
Date: Wed, 24 Feb 2016 14:12:03 +1000 [thread overview]
Message-ID: <20160224041203.GA32566@jelly.redhat.com> (raw)
In-Reply-To: <20160223230855.GD30638@dtor-ws>
This explicitly states behavior we already use for some touchpads and tablet
devices.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
---
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
next prev parent reply other threads:[~2016-02-24 4:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 21:56 Question about ABS_DISTANCE's intended usage Charles Mooney
2016-02-18 18:19 ` Dmitry Torokhov
2016-02-21 22:04 ` Peter Hutterer
2016-02-22 16:35 ` Charles Mooney
2016-02-22 22:04 ` Peter Hutterer
2016-02-23 22:02 ` Dmitry Torokhov
2016-02-23 22:39 ` Peter Hutterer
2016-02-23 23:08 ` Dmitry Torokhov
2016-02-24 4:12 ` Peter Hutterer [this message]
2016-04-06 5:09 ` [PATCH] Documentation: event-codes.txt: clarify we want BTN_TOOL_<name> on proximity Peter Hutterer
2016-04-06 17:16 ` Dmitry Torokhov
2016-02-29 16:16 ` Question about ABS_DISTANCE's intended usage Charles Mooney
2016-02-23 22:42 ` Henrik Rydberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160224041203.GA32566@jelly.redhat.com \
--to=peter.hutterer@who-t.net \
--cc=benjamin.tissoires@redhat.com \
--cc=charliemooney@google.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=rydberg@bitmath.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).