From: Peter Hutterer <peter.hutterer@who-t.net>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: linux-input@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Ingo Tuchscherer <ingo.tuchscherer@linux.vnet.ibm.com>,
Stuart Yoder <stuart.yoder@nxp.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
Douglas Anderson <dianders@chromium.org>,
Ping Cheng <pinglinux@gmail.com>, Kamil Debski <kamil@wypas.org>
Subject: Re: [PATCH RFC 3/4] input: add a EV_SW event for ratchet switch
Date: Tue, 28 Mar 2017 10:25:17 +1000 [thread overview]
Message-ID: <20170328002517.GA12967@jelly> (raw)
In-Reply-To: <20170327092731.3fd5db9a@vento.lan>
On Mon, Mar 27, 2017 at 09:27:31AM -0300, Mauro Carvalho Chehab wrote:
> Em Mon, 27 Mar 2017 11:53:57 +1000
> Peter Hutterer <peter.hutterer@who-t.net> escreveu:
>
> > On Sat, Mar 25, 2017 at 07:49:41PM -0300, Mauro Carvalho Chehab wrote:
> > > Some mouses have a switch on their wheel, allowing to switch
> > > between ratchet or free wheel mode. Add support for it.
> >
> > I understand the want to support it because it's there but what do you
> > expect this to be used for?
> >
> > tbh, I wouldn't know what to do with this information, short of displaying
> > some OSD to inform the user. Which is rather superfluous since the physical
> > change will feel obvious anyway.
>
> For this particular device, the main reason is because it is there :-)
> As adding support for it is trivial, I don't see any reason why not
> adding it.
>
> Yet, applications could use it, in order to switch between a "discrete"
> mode, where one wheel position corresponds to one line of scroll, and
> movements below a threshold would be ignored.
fwiw, that would more likely be the result of receiving a different event
code (hires-wheel), more so than a ratchet switch - at least on this device.
the mice I have here don't change the behaviour of the wheel, so the
granularity is the same before and after. But they also don't send events
for the state, so there's that :)
Cheers,
Peter
>
>
> >
> > A Documentation/input/event-codes.txt hunk would be welcomed here too
> > btw.
>
> Sure. Will do on a next patch series, once we agree about the high
> resolution wheel movements API.
> >
> > Cheers,
> > Peter
> >
> > >
> > > Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
> > > ---
> > > include/linux/mod_devicetable.h | 2 +-
> > > include/uapi/linux/input-event-codes.h | 4 +++-
> > > 2 files changed, 4 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/include/linux/mod_devicetable.h b/include/linux/mod_devicetable.h
> > > index 8a57f0b1242d..73534c591b40 100644
> > > --- a/include/linux/mod_devicetable.h
> > > +++ b/include/linux/mod_devicetable.h
> > > @@ -292,7 +292,7 @@ struct pcmcia_device_id {
> > > #define INPUT_DEVICE_ID_LED_MAX 0x0f
> > > #define INPUT_DEVICE_ID_SND_MAX 0x07
> > > #define INPUT_DEVICE_ID_FF_MAX 0x7f
> > > -#define INPUT_DEVICE_ID_SW_MAX 0x0f
> > > +#define INPUT_DEVICE_ID_SW_MAX 0x1f
> > >
> > > #define INPUT_DEVICE_ID_MATCH_BUS 1
> > > #define INPUT_DEVICE_ID_MATCH_VENDOR 2
> > > diff --git a/include/uapi/linux/input-event-codes.h b/include/uapi/linux/input-event-codes.h
> > > index 23b2d377af59..a3eafd0527f1 100644
> > > --- a/include/uapi/linux/input-event-codes.h
> > > +++ b/include/uapi/linux/input-event-codes.h
> > > @@ -782,7 +782,9 @@
> > > #define SW_LINEIN_INSERT 0x0d /* set = inserted */
> > > #define SW_MUTE_DEVICE 0x0e /* set = device disabled */
> > > #define SW_PEN_INSERTED 0x0f /* set = pen inserted */
> > > -#define SW_MAX 0x0f
> > > +#define SW_RATCHET 0x10 /* set = ratchet mode,
> > > + unset: free wheel */
> > > +#define SW_MAX 0x1f
> > > #define SW_CNT (SW_MAX+1)
> > >
> > > /*
> > > --
> > > 2.9.3
> > >
> > >
>
>
>
> Thanks,
> Mauro
next prev parent reply other threads:[~2017-03-28 0:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-25 22:49 [PATCH RFC 0/4] Improve support for Logitech MX Anywhere 2 Mauro Carvalho Chehab
2017-03-25 22:49 ` [PATCH RFC 1/4] input: add an EV_REL event for high-res vertical wheel Mauro Carvalho Chehab
2017-03-25 22:49 ` [PATCH RFC 2/4] hid-logitech-hidpp: add support for high res wheel Mauro Carvalho Chehab
2017-03-25 22:49 ` [PATCH RFC 3/4] input: add a EV_SW event for ratchet switch Mauro Carvalho Chehab
2017-03-25 22:49 ` [PATCH RFC 4/4] hid-logitech-hidpp: add support " Mauro Carvalho Chehab
2017-03-27 1:53 ` [PATCH RFC 3/4] input: add a EV_SW event " Peter Hutterer
2017-03-27 12:27 ` Mauro Carvalho Chehab
2017-03-28 0:25 ` Peter Hutterer [this message]
2017-03-28 9:36 ` Mauro Carvalho Chehab
2017-03-27 1:40 ` [PATCH RFC 1/4] input: add an EV_REL event for high-res vertical wheel Peter Hutterer
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=20170328002517.GA12967@jelly \
--to=peter.hutterer@who-t.net \
--cc=benjamin.tissoires@redhat.com \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hans.verkuil@cisco.com \
--cc=ingo.tuchscherer@linux.vnet.ibm.com \
--cc=kamil@wypas.org \
--cc=linux-input@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mchehab@s-opensource.com \
--cc=pinglinux@gmail.com \
--cc=schwidefsky@de.ibm.com \
--cc=stuart.yoder@nxp.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).