From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 222000] USB: xhci_hcd: Goodix USB Fingerprint sensor keep resetting
Date: Thu, 01 Oct 2026 08:41:09 +0000 [thread overview]
Message-ID: <bug-222000-208809-kh2SbFFxus@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-222000-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=222000
rppxj178543@163.com (rppxj178543@163.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rppxj178543@163.com
--- Comment #1 from rppxj178543@163.com (rppxj178543@163.com) ---
The repeated "reset full-speed USB device" messages likely come from
usb_reset_device() in drivers/usb/core/hub.c. The device 27c6:6090 has no entry
in the USB quirk table (drivers/usb/core/quirks.c), and autosuspend is enabled
by default with a 2-second delay — the sensor autosuspends frequently and may
fail to resume cleanly, triggering a reset-resume fallback.
Could you test this kernel boot parameter (no rebuild needed):
usbcore.quirks=27c6:6090:kr
k = disable LPM, r = force reset-resume. If this stops the resets, the fix is
to add the device to usb_quirk_list[] in drivers/usb/core/quirks.c:
{ USB_DEVICE(0x27c6, 0x6090), .driver_info = USB_QUIRK_NO_LPM |
USB_QUIRK_RESET_RESUME },
Also note: disabling power/control on the device alone via udev is insufficient
— the parent hub's autosuspend can still affect it.
It would also help to know whether the resets happen during idle or only during
authentication — that would distinguish autosuspend issues from a device
firmware problem.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2026-10-01 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 0:31 [Bug 222000] New: USB: xhci_hcd: Goodix USB Fingerprint sensor keep resetting bugzilla-daemon
2026-10-01 8:41 ` bugzilla-daemon [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=bug-222000-208809-kh2SbFFxus@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@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