From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 217670] dwc3: regression in USB DWC3 driver in kernel 5.15 branch
Date: Thu, 31 Aug 2023 09:12:27 +0000 [thread overview]
Message-ID: <bug-217670-208809-b2ZDvbzNj2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217670-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217670
The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |regressions@leemhuis.info
--- Comment #9 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) ---
(In reply to Tomasz Rostanski from comment #8)
>>> 7bee318838890 usb: dwc3: reference clock period configuration
>>> a5ae3cbe9dfcc usb: dwc3: Get clocks individually
>>> 5114c3ee24875 usb: dwc3: Calculate REFCLKPER based on reference clock
>>> 596c87856e08d usb: dwc3: Program GFLADJ
>>> a6fc2f1b09278 usb: dwc3: core: add gfladj_refclk_lpm_sel quirk
>>
>> Can you test this to verify that it does actually work for you?
>> thanks,
>>
>> greg k-h
>
> I confirm. It works for me.
Tomasz, was a fix ever merged to 5.15.y – either a revert or the changes listed
above? Doesn't look like it from here, but I have the strong suspicion that I'm
missing something here.
--
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 prev parent reply other threads:[~2023-08-31 9:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 13:18 [Bug 217670] New: Regression in USB DWC3 driver in kernel 5.15 branch bugzilla-daemon
2023-07-14 13:28 ` [Bug 217670] dwc3: regression " 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 [this message]
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-b2ZDvbzNj2@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;
as well as URLs for NNTP newsgroup(s).