From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Peter Hutterer <peter.hutterer@who-t.net>,
linux-input@vger.kernel.org,
Benjamin Tissoires <benjamin.tissoires@gmail.com>,
Ping Cheng <pingc@wacom.com>, Hans de Goede <hdegoede@redhat.com>,
Bastien Nocera <hadess@hadess.net>
Subject: Re: [PATCH] Documentation: input - define INPUT_PROP_ACCELEROMETER behavior
Date: Fri, 27 Mar 2015 09:59:34 -0700 [thread overview]
Message-ID: <20150327165934.GC17364@dtor-ws> (raw)
In-Reply-To: <alpine.LNX.2.00.1503270112460.6781@pobox.suse.cz>
On Fri, Mar 27, 2015 at 01:17:20AM +0100, Jiri Kosina wrote:
> On Fri, 27 Mar 2015, Peter Hutterer wrote:
>
> > Spell out what this property means to userspace. If the property is set, all
> > directional axes must be accelerometer axes, any other axes are left as-is.
> > This allows an accelerometer device to e.g. have an ABS_WHEEL.
> >
> > It is not permitted to mix normal directional axes and accelerometer axes on
> > the same device node.
> >
> > Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
> > ---
> > I think this is the most sensible definition of what to expect when this
> > property is set on a device.
>
> First, I am quilty here. I've let INPUT_PROP_ACCELEROMETER slip through my
> tree without Dmitry's Ack, which is what I normally require for everything
> touching input.h. Mea culpa maxima, I missed it, sorry for that.
>
> This makes sense to me though. So
>
> Acked-by: Jiri Kosina <jkosina@suse.cz>
>
> but let's see what Dmitry has to say.
>
> Good thing is that this went only into 4.0-rc1, so if the whole
> INPUT_PROP_ACCELEROMETER turns out to be absolute no-go for some reason,
> we can still revert it.
No, I think that's fine. In the past I was hesitant of defining device
types, but at least for accelerometers, given that we state that we will
not be mixing them with regular directional axes, that should be fine.
I will apply this.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2015-03-27 16:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 0:11 [PATCH] Documentation: input - define INPUT_PROP_ACCELEROMETER behavior Peter Hutterer
2015-03-27 0:17 ` Jiri Kosina
2015-03-27 16:59 ` Dmitry Torokhov [this message]
2015-03-27 0:43 ` Bastien Nocera
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=20150327165934.GC17364@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=benjamin.tissoires@gmail.com \
--cc=hadess@hadess.net \
--cc=hdegoede@redhat.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--cc=pingc@wacom.com \
/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).