From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Tero Kristo <tero.kristo@linux.intel.com>,
linux-input@vger.kernel.org, benjamin.tissoires@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: input: Add support for USI style events
Date: Fri, 30 Sep 2022 11:15:46 -0700 [thread overview]
Message-ID: <YzcyUgLbZ2pVJSMO@google.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.2209301109030.16823@cbobk.fhfr.pm>
On Fri, Sep 30, 2022 at 11:09:12AM +0200, Jiri Kosina wrote:
> On Thu, 25 Aug 2022, Jiri Kosina wrote:
>
> > > Add support for Universal Stylus Interface (USI) style events to the HID
> > > input layers. The events are mapped as follows:
> > >
> > > type id event
> > > ---- -- -----
> > > MSC(4) 6 Pen ID
> > > MSC(4) 7 Pen Color
> > > MSC(4) 8 Pen Line Style Ink
> > > MSC(4) 9 Pen Line Style Pencil
> > > MSC(4) 0xa Pen Line Style Highlighter
> > > MSC(4) 0xb Pen Line Style Chisel Marker
> > > MSC(4) 0xc Pen Line Style Brush
> > > MSC(4) 0xd Pen No Preferred Line Style
> > > ABS(3) 0x1c Pen Line Width
> > >
> > > All the listed MSC events are new, the ABS one is mapped to an existing
> > > event.
> >
> > Dmitry, could you please Ack the MSC_PEN_* additions?
>
> Dmitry, friendly ping on this one.
Very sorry, I meant to answer and forgot...
We need good descriptions of what exactly these events are, and when and
how userspace should expect/use them.
In general, I am wary of MISC_* namespace as it needs to be sent in
every packet as we do not retain state and do not give userspace way of
querying it, unlike ABS_* or KEY_* or number of other events.
Also, what do we do with multiple pens used at once? Maybe we do not
have such devices now, but multitouch devices did not exist in the
beginning either, and now are ubiquitous.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2022-09-30 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 10:35 [PATCH] HID: input: Add support for USI style events Tero Kristo
2022-08-25 9:41 ` Jiri Kosina
2022-09-30 9:09 ` Jiri Kosina
2022-09-30 18:15 ` Dmitry Torokhov [this message]
2022-10-07 11:25 ` Tero Kristo
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=YzcyUgLbZ2pVJSMO@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tero.kristo@linux.intel.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).