From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 217670] New: Regression in USB DWC3 driver in kernel 5.15 branch
Date: Fri, 14 Jul 2023 13:18:29 +0000 [thread overview]
Message-ID: <bug-217670-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=217670
Bug ID: 217670
Summary: Regression in USB DWC3 driver in kernel 5.15 branch
Product: Drivers
Version: 2.5
Hardware: ARM
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: tomasz.rostanski@thalesgroup.com
Regression: No
The backport commit to 5.15 branch:
9d4f84a15f9c9727bc07f59d9dafc89e65aadb34 "arm64: dts: imx8mp: Add
snps,gfladj-refclk-lpm-sel quirk to USB nodes" (from upstream commit
5c3d5ecf48ab06c709c012bf1e8f0c91e1fcd7ad)
switched from "snps,dis-u2-freeclk-exists-quirk" to
"snps,gfladj-refclk-lpm-sel-quirk".
The problem is that the gfladj-refclk-lpm-sel-quirk quirk is not implemented /
backported to 5.15 branch.
This commit should be either reverted, or the commit introducing
gfladj-refclk-lpm-sel-quirk needs to be merged to 5.15 kernel branch.
As a result of this patch, on Gateworks Venice GW7400 revB board the USB 3.x
devices which are connected to the USB Type C port does not enumerate and the
following errors are generated:
[ 14.906302] xhci-hcd xhci-hcd.0.auto: Timeout while waiting for setup device
command
[ 15.122383] usb 2-1: device not accepting address 2, error -62
[ 25.282195] xhci-hcd xhci-hcd.0.auto: Abort failed to stop command ring:
-110
[ 25.297408] xhci-hcd xhci-hcd.0.auto: xHCI host controller not responding,
assume dead
[ 25.305345] xhci-hcd xhci-hcd.0.auto: HC died; cleaning up
[ 25.311058] xhci-hcd xhci-hcd.0.auto: Timeout while waiting for stop
endpoint command
[ 25.334361] usb usb2-port1: couldn't allocate usb_device
When the commit is reverted the USB 3.x drives works fine.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2023-07-14 13:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 13:18 bugzilla-daemon [this message]
2023-07-14 13:28 ` [Bug 217670] dwc3: regression in USB DWC3 driver in kernel 5.15 branch bugzilla-daemon
2023-07-14 13:29 ` bugzilla-daemon
2023-07-14 13:30 ` bugzilla-daemon
2023-07-16 14:59 ` [Bug 217670] New: Regression " Greg KH
2023-07-16 15:00 ` [Bug 217670] dwc3: regression " bugzilla-daemon
2023-07-17 5:20 ` bugzilla-daemon
2023-07-17 6:36 ` bugzilla-daemon
2023-07-17 14:30 ` Greg KH
2023-07-17 14:30 ` bugzilla-daemon
2023-07-18 5:25 ` bugzilla-daemon
2023-08-31 9:12 ` bugzilla-daemon
2023-08-31 9:19 ` bugzilla-daemon
2023-08-31 9:31 ` bugzilla-daemon
2023-08-31 10:56 ` Greg KH
2023-08-31 10:56 ` bugzilla-daemon
2023-09-01 9:22 ` bugzilla-daemon
2023-09-01 12:53 ` bugzilla-daemon
2023-09-01 12:53 ` bugzilla-daemon
2023-09-01 12:53 ` bugzilla-daemon
2023-09-01 12:54 ` bugzilla-daemon
2023-09-01 12:54 ` bugzilla-daemon
2023-09-01 12:54 ` bugzilla-daemon
2023-09-01 12:55 ` bugzilla-daemon
2023-09-01 12:55 ` bugzilla-daemon
2023-09-01 12:56 ` bugzilla-daemon
2023-09-01 12:56 ` bugzilla-daemon
2023-09-01 12:57 ` bugzilla-daemon
2023-09-01 13:14 ` Greg KH
2023-09-01 13:13 ` bugzilla-daemon
2023-09-01 13:14 ` bugzilla-daemon
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-217670-208809@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.