From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
linux-input@vger.kernel.org, Jiri Kosina <jkosina@suse.cz>,
Stuart Yoder <stuart.yoder@nxp.com>,
Ingo Tuchscherer <ingo.tuchscherer@linux.vnet.ibm.com>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Ping Cheng <pinglinux@gmail.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
Kamil Debski <kamil@wypas.org>,
Douglas Anderson <dianders@chromium.org>
Subject: Re: [PATCH v4 1/5] input: event-codes: reserve some space for REL_MISC events
Date: Wed, 21 Jun 2017 14:05:17 +0200 [thread overview]
Message-ID: <20170621120517.GD23046@mail.corp.redhat.com> (raw)
In-Reply-To: <20170415175502.GC33447@dtor-ws>
On Apr 15 2017 or thereabouts, Dmitry Torokhov wrote:
> On Tue, Apr 11, 2017 at 10:29:38AM -0300, Mauro Carvalho Chehab wrote:
> > The HID input layer has a tendency to map usages to REL_MISC
> > +1, +2, +3, etc... When it doesn't know how to map an
> > usage, the core layer maps it to the next one.
>
> We should wean HID off this habit. We should not be adding placeholder
> events without defined meaning.
See https://patchwork.kernel.org/patch/9795625/ for such patch.
Feedbacks welcome :)
Cheers,
Benjamin
>
> >
> > So, reserve some space for such events.
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
> > ---
> > include/linux/mod_devicetable.h | 2 +-
> > include/uapi/linux/input-event-codes.h | 8 +++++++-
> > 2 files changed, 8 insertions(+), 2 deletions(-)
> >
> > diff --git a/include/linux/mod_devicetable.h b/include/linux/mod_devicetable.h
> > index 8850fcaf50db..a3e8c572a046 100644
> > --- a/include/linux/mod_devicetable.h
> > +++ b/include/linux/mod_devicetable.h
> > @@ -286,7 +286,7 @@ struct pcmcia_device_id {
> > #define INPUT_DEVICE_ID_EV_MAX 0x1f
> > #define INPUT_DEVICE_ID_KEY_MIN_INTERESTING 0x71
> > #define INPUT_DEVICE_ID_KEY_MAX 0x2ff
> > -#define INPUT_DEVICE_ID_REL_MAX 0x0f
> > +#define INPUT_DEVICE_ID_REL_MAX 0x1f
> > #define INPUT_DEVICE_ID_ABS_MAX 0x3f
> > #define INPUT_DEVICE_ID_MSC_MAX 0x07
> > #define INPUT_DEVICE_ID_LED_MAX 0x0f
> > diff --git a/include/uapi/linux/input-event-codes.h b/include/uapi/linux/input-event-codes.h
> > index f5a8d96e1e09..444956ba832c 100644
> > --- a/include/uapi/linux/input-event-codes.h
> > +++ b/include/uapi/linux/input-event-codes.h
> > @@ -704,7 +704,13 @@
> > #define REL_DIAL 0x07
> > #define REL_WHEEL 0x08
> > #define REL_MISC 0x09
> > -#define REL_MAX 0x0f
> > +#define REL_MISC_1 0x0a
> > +#define REL_MISC_2 0x0b
> > +#define REL_MISC_3 0x0c
> > +#define REL_MISC_4 0x0d
> > +#define REL_MISC_5 0x0e
> > +#define REL_MISC_6 0x0f
> > +#define REL_MAX 0x1f
> > #define REL_CNT (REL_MAX+1)
> >
> > /*
> > --
> > 2.9.3
> >
>
> --
> Dmitry
next prev parent reply other threads:[~2017-06-21 12:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 13:29 [PATCH v4 0/5] add support for high res wheel found on some Logitech devices Mauro Carvalho Chehab
2017-04-11 13:29 ` [PATCH v4 1/5] input: event-codes: reserve some space for REL_MISC events Mauro Carvalho Chehab
2017-04-15 17:55 ` Dmitry Torokhov
2017-06-21 12:05 ` Benjamin Tissoires [this message]
2017-04-11 13:29 ` [PATCH v4 2/5] input: add an EV_REL event for high-res vertical wheel Mauro Carvalho Chehab
2017-04-11 13:29 ` [PATCH v4 3/5] input: add a EV_SW event for ratchet switch Mauro Carvalho Chehab
2017-04-14 12:54 ` Benjamin Tissoires
2017-04-15 18:04 ` Dmitry Torokhov
2017-04-15 22:50 ` Mauro Carvalho Chehab
2017-04-11 13:29 ` [PATCH v4 4/5] hid-logitech-hidpp: add support for high res wheel Mauro Carvalho Chehab
2017-04-11 13:29 ` [PATCH v4 5/5] hid-logitech-hidpp: add support for ratchet switch Mauro Carvalho Chehab
2017-04-14 12:56 ` Benjamin Tissoires
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=20170621120517.GD23046@mail.corp.redhat.com \
--to=benjamin.tissoires@redhat.com \
--cc=davem@davemloft.net \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hans.verkuil@cisco.com \
--cc=ingo.tuchscherer@linux.vnet.ibm.com \
--cc=jkosina@suse.cz \
--cc=kamil@wypas.org \
--cc=linux-input@vger.kernel.org \
--cc=mchehab@s-opensource.com \
--cc=pinglinux@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.