[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4042p469-o208-q0qq-7p10-16no004o7s0q@xreary.bet>
Date: Fri, 22 Nov 2024 21:23:31 +0100 (CET)
From: Jiri Kosina <jikos@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
cc: Benjamin Tissoires <bentiss@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] HID for 6.13
On Fri, 22 Nov 2024, Linus Torvalds wrote:
> > please pull from
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git tags/hid-for-linus-2024111801
> >
> > to receive HID subsystem queue for 6.13 merge window.
>
> Hmm. There's something odd going on here. My mouse scroll-wheel
> stopped working (Logitech MX Anywhere 3), and this pull would look
> like the prime suspect.
>
> The mouse otherwise works, so it's not that the mouse isn't found,
> it's literally just the scroll-wheel functionality that doesn't work.
>
> Oddly enough, if I remove and re-insert the Logitech wireless dongle,
> the scroll wheel works again. So it's not some kind of complete
> breakage - but it also wasn't a one-time fluke thing, in that it
> happened twice in a row when rebooting into a new kernel.
>
> Any ideas? Does this make anybody go "Hmm, maybe ..."
Interesting, in this round the only patch to the Logitech driver
(fb6c0583a1435) should really be pretty much nop, so it might be something
slightly more subtle.
How do
/proc/bus/input/devices
and
/sys/kernel/debug/hid/<device>/rdesc
entries look like for this device in working and non-working case? Are
they the same?
Does scrolling the wheel produce any output in
cat /sys/kernel/debug/hid/<device>/events
?
Thanks,
--
Jiri Kosina
SUSE Labs
Powered by blists - more mailing lists