From: "José Expósito" <jose.exposito89@gmail.com>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Stefan Hansson <newbie13xd@gmail.com>,
Jiri Kosina <jikos@kernel.org>, Ping Cheng <ping.cheng@wacom.com>,
Peter Hutterer <peter.hutterer@who-t.net>,
"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: Regression likely in hid_uclogic driver breaks Huion Inspiroy H640 drawing tablet
Date: Sun, 28 Aug 2022 12:07:14 +0200 [thread overview]
Message-ID: <20220828100714.GA182607@elementary> (raw)
In-Reply-To: <CAO-hwJ+MtU5w9M5rqbOPYjUUZtJ609Q0GwPJpy-9egDEjo9m7g@mail.gmail.com>
On Mon, Aug 22, 2022 at 08:25:52AM +0200, Benjamin Tissoires wrote:
> On Sun, Aug 21, 2022 at 1:45 AM Stefan Hansson <newbie13xd@gmail.com> wrote:
> >
> > > FWIW, I found the issue: the hid-uclogic driver is emitting input data
> > > behind hid-input, and the state between the 2 is desynchronized.
> > >
> > > The following patch seems to be working (with the Huion v1 protocol I
> > > have here that I have tweaked to resemble a v2):
> > > ---
> > > From aeedd318e6cb4dbee551f67616302cc7c4308c58 Mon Sep 17 00:00:00 2001
> > > From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> > > Date: Thu, 18 Aug 2022 15:09:25 +0200
> > > Subject: [PATCH] Fix uclogic
> > >
> > > ---
> > > drivers/hid/hid-input.c | 5 ++++-
> > > 1 file changed, 4 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/hid/hid-input.c b/drivers/hid/hid-input.c
> > > index c6b27aab9041..a3e2397bb3a7 100644
> > > --- a/drivers/hid/hid-input.c
> > > +++ b/drivers/hid/hid-input.c
> > > @@ -1530,7 +1530,10 @@ void hidinput_hid_event(struct hid_device *hid,
> > > struct hid_field *field, struct
> > > * assume ours
> > > */
> > > if (!report->tool)
> > > - hid_report_set_tool(report, input, usage->code);
> > > + report->tool = usage->code;
> > > +
> > > + /* drivers may have changed the value behind our back,
> > > resend it */
> > > + hid_report_set_tool(report, input, report->tool);
> > > } else {
> > > hid_report_release_tool(report, input, usage->code);
> > > }
> >
> > What branch should this be applied on top of?
> >
>
> Sorry for that. I had some local commits in my tree that made the
> patch unusable. I just formally sent the patch [0] based on the
> hid.git/for-next branch which is actually applying on top of v5.19 or
> even v5.18.
>
> Cheers,
> Benjamin
>
> [0] https://lore.kernel.org/linux-input/20220822062247.1146141-1-benjamin.tissoires@redhat.com/T/#u
>
As I already commented in the patch, the problem is now solved on
hid/for-next.
Thanks!
prev parent reply other threads:[~2022-08-28 10:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 2:14 PROBLEM: Regression likely in hid_uclogic driver breaks Huion Inspiroy H640 drawing tablet Stefan Hansson
2022-07-23 11:40 ` Jiri Kosina
2022-07-24 11:48 ` José Expósito
2022-07-25 22:48 ` José Expósito
2022-07-26 17:58 ` Stefan Hansson
2022-07-26 21:48 ` José Expósito
2022-07-27 2:56 ` Stefan Hansson
2022-07-27 16:27 ` José Expósito
2022-08-04 18:24 ` José Expósito
2022-08-11 15:23 ` Benjamin Tissoires
2022-08-13 11:09 ` José Expósito
2022-08-19 14:15 ` Benjamin Tissoires
2022-08-20 23:45 ` Stefan Hansson
2022-08-22 6:25 ` Benjamin Tissoires
2022-08-28 10:07 ` 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=20220828100714.GA182607@elementary \
--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=newbie13xd@gmail.com \
--cc=peter.hutterer@who-t.net \
--cc=ping.cheng@wacom.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).