linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "José Expósito" <jose.exposito89@gmail.com>
To: spbnick@gmail.com
Cc: jikos@kernel.org, benjamin.tissoires@redhat.com,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC] UCLogic: Filtering unsupported HUION tablets
Date: Mon, 18 Jul 2022 19:29:53 +0200	[thread overview]
Message-ID: <20220718172953.6817-1-jose.exposito89@gmail.com> (raw)

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.

Best wishes,
José Expósito


             reply	other threads:[~2022-07-18 17:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 17:29 José Expósito [this message]
2022-07-19  9:57 ` [RFC] UCLogic: Filtering unsupported HUION tablets 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

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=20220718172953.6817-1-jose.exposito89@gmail.com \
    --to=jose.exposito89@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --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).