From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Hutterer Subject: Re: [PATCH] Documentation: event-codes.txt: clarify we want BTN_TOOL_ on proximity Date: Wed, 6 Apr 2016 15:09:01 +1000 Message-ID: <20160406050901.GA21230@jelly.redhat.com> References: <20160223230855.GD30638@dtor-ws> <20160224041203.GA32566@jelly.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from leo.clearchain.com ([199.73.29.74]:22358 "EHLO mail.clearchain.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754514AbcDFFXy (ORCPT ); Wed, 6 Apr 2016 01:23:54 -0400 Content-Disposition: inline In-Reply-To: <20160224041203.GA32566@jelly.redhat.com> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Dmitry Torokhov Cc: Charles Mooney , Benjamin Tissoires , Henrik Rydberg , Linux Input 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 > --- > 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_ should be set to 1 when the tool comes into detectable > + proximity and set to 0 when the tool leaves detectable proximity. > + BTN_TOOL_ 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_: > - Used to describe multitouch input events. Please see > -- > 2.5.0 almost forgot about this one, Dmitry, you happy with this one? Cheers, Peter