From: "José Expósito" <jose.exposito89@gmail.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: spbnick@gmail.com, jikos@kernel.org,
benjamin.tissoires@redhat.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] UCLogic: Filtering unsupported HUION tablets
Date: Sun, 24 Jul 2022 13:14:53 +0200 [thread overview]
Message-ID: <20220724111453.GA31129@elementary> (raw)
In-Reply-To: <20debb4d623f057b77ad9d2f5909540baf750c13.camel@hadess.net>
On Thu, Jul 21, 2022 at 11:39:06AM +0200, Bastien Nocera wrote:
> On Mon, 2022-07-18 at 19:29 +0200, José Expósito wrote:
> > Hi!
> >
> > No code yet, just a kind request for comments and hopefully some
> > wisdom
> > and experience from Nikolai dealing with HUION devices.
> >
> > HUION keeps reusing the same vendor and product IDs for their
> > devices.
> > This makes it really difficult to differentiate between devices and
> > handle them in the kernel and also in user space.
> >
> > Reusing IDs could introduce a problem:
> >
> > If HUION, or other vendor following the same practices, releases a
> > new
> > tablet with a duplicated product ID, the UCLogic driver would handle
> > it.
> > The device might work with the existing code or it might fail because
> > of
> > a new feature or a whole different firmware.
> >
> > As far as I know, at the moment there is not a mechanism in place to
> > avoid this situation.
> > I think that it'd be better to ignore those devices in UCLogic and
> > let
> > the HID generic driver handle them because using HID generic would
> > provide a basic user experience while using UCLogic might fail to
> > probe
> > the tablet.
> >
> > DIGImend's web already provides a nice list of supported devices:
> > http://digimend.github.io/tablets/
> >
> > So, I wonder:
> >
> > - Do you think it makes sense to ignore untested devices?
> > - If the answer is yes, do we have a better option than checking the
> > device name against an allow-list? It'd be great to hear other
> > people's ideas.
>
> I don't think it makes sense to ignore untested devices, unless you
> know for a fact they won't work.
>
> But if the name is part of detecting the device, it would certainly
> make sense to use that as part of the identifier for the device, rather
> than just the USB VIP:PID.
Agreed, I also think that adding the name to the vendor/product IDs
pair would be a better identifier. However, at this point, we don't
have that information for all supported tablets, so I guess that we
will have to fix new tablets reusing the VIP:PID as they are
released.
It is unfortunate, but we'll have to deal with it.
Thanks a lot for your comments!
Jose
> You should be able to add the product strings in the .driver_data, and
> check them in probe().
>
> Cheers
prev parent reply other threads:[~2022-07-24 11:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 17:29 [RFC] UCLogic: Filtering unsupported HUION tablets José Expósito
2022-07-19 9:57 ` Nikolai Kondrashov
2022-07-20 17:36 ` José Expósito
2022-07-20 17:45 ` Nikolai Kondrashov
2022-07-20 17:54 ` José Expósito
2022-07-20 18:13 ` Nikolai Kondrashov
2022-07-24 11:05 ` José Expósito
2022-08-08 7:44 ` Nikolai Kondrashov
2022-08-08 16:15 ` José Expósito
2022-07-21 9:39 ` Bastien Nocera
2022-07-24 11:14 ` José Expósito [this message]
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=20220724111453.GA31129@elementary \
--to=jose.exposito89@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=hadess@hadess.net \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=spbnick@gmail.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).