From: Ondrej Zary <linux@zary.sk>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Jiri Kosina <jikos@kernel.org>,
"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hid-multitouch: Fix Iiyama ProLite T1931SAW (0eef:0001 again!)
Date: Mon, 15 Nov 2021 09:37:31 +0100 [thread overview]
Message-ID: <202111150937.31306.linux@zary.sk> (raw)
In-Reply-To: <CAO-hwJLZ8roXUxnB5Umyjd_22KFGbFMouxdVM0GLSSLrktteAg@mail.gmail.com>
On Friday 12 November 2021, Benjamin Tissoires wrote:
> Hi Ondrej,
>
> On Fri, Nov 12, 2021 at 3:00 PM Ondrej Zary <linux@zary.sk> wrote:
> >
> > Iiyama ProLite T1931SAW does not work with Linux - input devices are
> > created but cursor does not move.
> >
> > It has the infamous 0eef:0001 ID which has been reused for various
> > devices before.
> >
> > It seems to require export_all_inputs = true.
> > Add it to mt_devices[] as MT_CLS_WIN_8 to fix the problem.
> > Hopefully there are no HID devices using this ID that will break.
> > It should not break non-HID devices (handled by usbtouchscreen).
>
> Hmm, this is worrisome. I am pretty sure there were some eGalax 0001
> devices that were Win 7 compatible and I am not sure if they are
> compatible with Win8...
>
> I guess that if you have to set MT_CLS_WIN_8, the device is not
> detected as such. so how about you use:
> MT_CLS_EXPORT_ALL_INPUTS instead, (to keep MT_CLS_DEFAULT for those
> devices), and restrict the VID/PID matching to the non Win8 devices:
It works with MT_CLS_EXPORT_ALL_INPUTS.
> HID_DEVICE(BUS_USB, HID_GROUP_GENERIC, USB_VENDOR_ID_DWAV,
> USB_DEVICE_ID_EGALAX_TOUCHCONTROLLER)
But does not match HID_GROUP_GENERIC.
>
> ?
>
> Cheers,
> Benjamin
>
> >
> > Signed-off-by: Ondrej Zary <linux@zary.sk>
> > ---
> > drivers/hid/hid-multitouch.c | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/drivers/hid/hid-multitouch.c b/drivers/hid/hid-multitouch.c
> > index e1afddb7b33d..099daf590392 100644
> > --- a/drivers/hid/hid-multitouch.c
> > +++ b/drivers/hid/hid-multitouch.c
> > @@ -1888,6 +1888,11 @@ static const struct hid_device_id mt_devices[] = {
> > MT_USB_DEVICE(USB_VENDOR_ID_CVTOUCH,
> > USB_DEVICE_ID_CVTOUCH_SCREEN) },
> >
> > + /* eGalax devices (SAW) */
> > + { .driver_data = MT_CLS_WIN_8,
> > + MT_USB_DEVICE(USB_VENDOR_ID_DWAV,
> > + USB_DEVICE_ID_EGALAX_TOUCHCONTROLLER) },
> > +
> > /* eGalax devices (resistive) */
> > { .driver_data = MT_CLS_EGALAX,
> > MT_USB_DEVICE(USB_VENDOR_ID_DWAV,
> > --
> > Ondrej Zary
> >
>
>
--
Ondrej Zary
next prev parent reply other threads:[~2021-11-15 8:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 13:55 [PATCH] hid-multitouch: Fix Iiyama ProLite T1931SAW (0eef:0001 again!) Ondrej Zary
2021-11-12 15:17 ` Benjamin Tissoires
2021-11-15 8:37 ` Ondrej Zary [this message]
2021-11-16 9:11 ` Benjamin Tissoires
2021-11-16 11:07 ` Ondrej Zary
2021-11-16 12:13 ` Benjamin Tissoires
2021-11-16 13:15 ` [PATCH v2] " Ondrej Zary
2021-11-16 17:07 ` Benjamin Tissoires
2021-11-19 15:00 ` Jiri Kosina
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=202111150937.31306.linux@zary.sk \
--to=linux@zary.sk \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).