From: Michal Pecio <michal.pecio@gmail.com>
To: Quinn Schive <quinnschive@hotmail.com>
Cc: linux-input@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] HID: logitech-hidpp: G502 LIGHTSPEED loses hi-res scroll state after S3 resume
Date: Wed, 9 Sep 2026 22:27:24 +0200 [thread overview]
Message-ID: <20260909222724.30fc8f52.michal.pecio@gmail.com> (raw)
In-Reply-To: <CY8PR14MB59809F95431FC6FFB0D0A56DA0B02@CY8PR14MB5980.namprd14.prod.outlook.com>
On Wed, 9 Sep 2026 09:58:28 -0600, Quinn Schive wrote:
> After some S3 resumes, mouse wheel scrolling becomes approximately 8
> times slower.
>
> Turning the G502 off and back on immediately restores normal
> scrolling.
>
> I captured the failure before power-cycling the mouse.
>
> During the resume that triggered the problem, both PROM21 xHCI
> controllers reported:
>
> xhci-pci-prom21 0000:11:00.0: xHC error in resume, USBSTS 0x401, Reinit
> usb usb10: root hub lost power or was reset
> usb usb11: root hub lost power or was reset
Hi,
You could try if this problem is fixed by the following patch:
https://lore.kernel.org/linux-usb/178832755831.50581.1058201741431375556@gmail.com/
That being said,
> My interpretation, with the caveat that I am not familiar with the
> HID++ driver internals, is:
>
> 1. Before suspend, the G502 is configured for high-resolution
> scrolling and hid-logitech-hidpp stores wheel_multiplier=8.
>
> 2. During S3 resume, the PROM21 xHCI controller fails normal resume
> and is reinitialized.
>
> 3. The LIGHTSPEED receiver gets a USB reset while USB persistence
> keeps the logical receiver/HID device present.
>
> 4. The G502 appears to lose its high-resolution wheel reporting
> configuration. In the affected state, one physical detent generates
> only one raw increment.
>
> 5. hid-logitech-hidpp retains wheel_multiplier=8 and apparently does
> not re-run the necessary high-resolution configuration on this
> recovery path.
this still looks like missing functionality in the driver.
Needs to handle reset_resume() perhaps?
Regards,
Michal
next prev parent reply other threads:[~2026-09-09 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 15:58 Quinn Schive
2026-09-09 20:27 ` Michal Pecio [this message]
2026-09-10 0:13 ` Quinn Schive
2026-09-10 8:38 ` Michal Pecio
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=20260909222724.30fc8f52.michal.pecio@gmail.com \
--to=michal.pecio@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=quinnschive@hotmail.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
all inboxes | Powered by JetHome®