linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>,
	Tomasz Rostanski <tomasz.rostanski@thalesgroup.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Stable <stable@vger.kernel.org>,
	Linux USB <linux-usb@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Fwd: dwc3: regression in USB DWC3 driver in kernel 5.15 branch
Date: Sat, 15 Jul 2023 18:03:06 +0700	[thread overview]
Message-ID: <bfee63a3-16ee-0061-94c0-9c9af5318634@gmail.com> (raw)

Hi,

I notice a stable-specific regression on Bugzilla [1]. Quoting from it:

> 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.

See Bugzilla for the full thread and attach dmesgs.

Anyway, I'm adding it to regzbot:

#regzbot introduced: 9d4f84a15f9c97 https://bugzilla.kernel.org/show_bug.cgi?id=217670
#regzbot title: regression in USB DWC3 driver due to missing gfladj-refclk-lpm-sel-quirk quirk

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217670

-- 
An old man doll... just what I always wanted! - Clara

             reply	other threads:[~2023-07-15 11:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-15 11:03 Bagas Sanjaya [this message]
2023-07-16 14:58 ` Fwd: dwc3: regression in USB DWC3 driver in kernel 5.15 branch Greg Kroah-Hartman
2023-11-01 18:59 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-21 15:25   ` Thorsten Leemhuis
2023-11-24 16:18     ` Greg Kroah-Hartman

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=bfee63a3-16ee-0061-94c0-9c9af5318634@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tomasz.rostanski@thalesgroup.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).