From: Quentin Schulz <quentin.schulz@cherry.de>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: u-boot@lists.u-boot-project.org, marek.vasut@mailbox.org,
trini@konsulko.com, ilias.apalodimas@linaro.org,
michal.simek@amd.com, lukma@nabladev.com, alchark@flipper.net,
jerome.forissier@arm.com, dlechner@baylibre.com, anshuld@ti.com,
sjg@chromium.org, Thinh.Nguyen@synopsys.com,
mkorpershoek@kernel.org, love.kumar@amd.com, s-vadapalli@ti.com
Subject: Re: [PATCH v10 00/30] usb: dwc3: part 2, make the resynced code work
Date: Fri, 6 Nov 2026 11:57:34 +0100 [thread overview]
Message-ID: <548adaa3-9d2f-4fa2-8fdf-7c537c4d153b@cherry.de> (raw)
In-Reply-To: <ca7b3725-cabd-4064-95dd-46c3eaa325f0@cherry.de>
Hi Anders,
On 11/4/26 6:51 PM, Quentin Schulz wrote:
> Hi Anders,
>
> On 11/3/26 2:45 PM, Anders Roxell wrote:
>> On 2026-10-30 15:28, Quentin Schulz wrote:
>>> Hi Andrew,
>>>
>>> On 10/28/26 3:15 PM, Anders Roxell wrote:
>>>> Hi,
>>>>
>>
>> [ ... ]
>>
>>> - Q7 USB P0 (lower) with Sandisk Extreme Pro USB stick,
>>> - Q7 USB P2 (upper) with Sandisk Extreme Pro USB stick,
>>>
>>> RK3399 Puma behaves the same in main and with your series applied.
>>> RK3588 Tiger has some regressions.
>>>
>>> Q7 USB P2 (upper) doesn't detect the Sandisk Ultra Flair USB stick
>>> anymore.
>>> It does on main branch, but on the USB2 controller only.
>>>
>>> Q7 USB P0 (lower) has issues handling the Kingston USB stick. 1st try:
>>
>> Hi Quentin,
>>
>> Thanks for testing both boards.
>>
>> About the OTG port: no need to spend more time on it.
>>
>> v10 had two bugs in the dwc3 core. It never read the core version, so
>> every version check was false. It also cleared the GSBUSCFG0 REQINFO
>> bits on every controller, and main does not touch them. v11 fixes both.
>> My best guess for the Kingston write on P0 is REQINFO, but I have no
>> Tiger to test it on.
>>
>> Did the other sticks pass with v10? That is the Ultra Flair and the
>> Extreme Pro on P0, and the Kingston and the Extreme Pro on P2. I want
>> to know if it is only one stick on each port.
>>
>
> - Q7 USB P0 (lower) with Sandisk Ultra Flair USB stick,
> - Q7 USB P2 (upper) with Sandisk Ultra Flair USB stick,
> - Q7 USB P0 (lower) with Kingston USB stick,
> - Q7 USB P2 (upper) with Kingston USB stick,
> - Q7 USB P0 (lower) with Sandisk Extreme Pro USB stick,
> - Q7 USB P2 (upper) with Sandisk Extreme Pro USB stick,
>
> was what I tested, on both v10 and main, on both RK3588 Tiger and RK3399
> Puma. I only reported the ones that didn't work, so yes to your question
> above.
>
>> Can you run the same tests with v11? It is on [1], on top of main
>> ab4dc5aacf95.
>>
>
> With v11 checked out, I only tested the scenarios with regressions I
> reported in the previous mail, that is only, on RK3588 Tiger only, with
> Kingston USB stick on P0 and Ultra Flair on P2.
>
> 2/2 tries were successful (regression gone) for the Kingston stick on P0.
>
> 5/5 tries for Ultra Flair on P2 (detected on the USB2 controller same as
> on main) were successful (regression gone). I got one try for Ultra
> Flair on P2 that reported the stick on the USB3 controller, funnily
> enough, the only try when I got a "cannot reset port 1!?". All other
> times, the USB stick was attached to the USB2 controller (like on main).
>
> I would like to run all test scenarios again and see if v11 introduces
> other regressions compared to v10, but this takes me about 2h
> uninterrupted and I'm not sure I will have time tomorrow or Friday as
> there are other fires to put out (still have to review the OpenSSL
> provider thing again, and I'm now finally impacted by it myself as I
> updated to Fedora 45 with OpenSSL 4 this morning).
>
For the v11 (commit 6030c4d33099 ("usb: dwc3: enable SUSPHY again after
xhci is registered")):
Tested-by: Quentin Schulz <quentin.schulz@cherry.de> RK3399 Puma
usbdrd_dwc3_1
Tested-by: Quentin Schulz <quentin.schulz@cherry.de> RK3588 Tiger
usb_host1_xhci + usb_host2_xhci
I've just remembered I've now got a Pine64 Quartz64 (RK3566) with two
DWC3, will try it next Monday.
I should have access to a Pine64 Rock64 (RK3328) starting 2027 where I
could test the DWC3 controller in there, if I don't forget (90% I will)
I can then report regressions, if any.
Not having access to any RK3528 device with a DWC3 (MangoPi 28k, NanoPi
R28S, NanoPi Zero 2, Radxa E20C, Radxa Rock 2A/2F), or to any RK3576
device with a DWC3 (Anbernic RG Vita Pro, ArmSom Sige5, Khadas Edge 2L,
NanoPi M5/R76S, Radxa Rock 4D), I cannot test those. I'm assuming Alexey
may be able to help for the RK3576 with the FlipperOne device (or others
since he has quite the collection of RK3576 boards IIRC). For RK3528,
maybe Jonas can help.
I would like to give the v11 a try on RK3566 next Monday before giving a
definitive go for Rockchip platforms, but this looks good to me.
Cheers,
Quentin
next prev parent reply other threads:[~2026-11-06 10:57 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 14:15 [PATCH v10 00/30] usb: dwc3: part 2, make the resynced code work Anders Roxell
2026-10-28 14:15 ` [PATCH v10 01/30] x86: asm: io.h: add rmb() and wmb() Anders Roxell
2026-10-28 14:15 ` [PATCH v10 02/30] dm: add helpers needed by the resynced DWC3 code Anders Roxell
2026-10-28 14:15 ` [PATCH v10 03/30] phy: cadence: use reset_control_assert() from reset.h Anders Roxell
2026-10-28 14:15 ` [PATCH v10 04/30] usb: phy: add the usb_phy helpers needed by the resynced DWC3 code Anders Roxell
2026-10-28 14:15 ` [PATCH v10 05/30] usb: gadget: adapt the gadget API after the resync Anders Roxell
2026-10-28 14:15 ` [PATCH v10 06/30] usb: gadget: udc: make udc-core build in U-Boot Anders Roxell
2026-10-28 14:15 ` [PATCH v10 07/30] usb: dwc3: core: remove the code U-Boot does not use Anders Roxell
2026-10-28 14:15 ` [PATCH v10 08/30] usb: dwc3: core: bring back the U-Boot entry points Anders Roxell
2026-10-28 14:15 ` [PATCH v10 09/30] usb: dwc3: core: adapt to the U-Boot APIs Anders Roxell
2026-10-28 14:15 ` [PATCH v10 10/30] usb: dwc3: adapt io.h, the Makefile and the TI glue Anders Roxell
2026-10-28 14:15 ` [PATCH v10 11/30] usb: dwc3: make gadget and ep0 build in U-Boot Anders Roxell
2026-10-28 14:15 ` [PATCH v10 12/30] usb: gadget: udc: enable async callbacks on bind Anders Roxell
2026-10-28 14:15 ` [PATCH v10 13/30] usb: dwc3: ep0: flush and invalidate cache around ep0 transfers Anders Roxell
2026-10-28 14:15 ` [PATCH v10 14/30] usb: dwc3: gadget: flush and invalidate cache around transfers Anders Roxell
2026-10-28 14:15 ` [PATCH v10 15/30] usb: dwc3: make the am62 glue build in U-Boot Anders Roxell
2026-10-28 14:15 ` [PATCH v10 16/30] usb: gadget: ci_udc: move to the udc-core registration Anders Roxell
2026-10-28 14:15 ` [PATCH v10 17/30] usb: gadget: ci_udc: set endpoint capabilities Anders Roxell
2026-10-28 14:15 ` [PATCH v10 18/30] usb: gadget: dwc2_udc_otg: fix up after the resync Anders Roxell
2026-10-28 14:15 ` [PATCH v10 19/30] usb: gadget: fix up the function drivers " Anders Roxell
2026-10-28 14:15 ` [PATCH v10 20/30] usb: gadget: fix up the last UDC " Anders Roxell
2026-10-28 14:15 ` [PATCH v10 21/30] usb: gadget: atmel_usba_udc: set endpoint capabilities Anders Roxell
2026-10-28 14:15 ` [PATCH v10 22/30] usb: gadget: at91_udc: register with udc-core Anders Roxell
2026-10-28 14:15 ` [PATCH v10 23/30] usb: gadget: at91_udc: set endpoint capabilities Anders Roxell
2026-10-28 14:15 ` [PATCH v10 24/30] usb: musb-new: fix up after the resync Anders Roxell
2026-10-28 14:15 ` [PATCH v10 25/30] usb: musb-new: set endpoint capabilities Anders Roxell
2026-10-28 14:15 ` [PATCH v10 26/30] usb: mtu3: fix up after the resync Anders Roxell
2026-10-28 14:15 ` [PATCH v10 27/30] usb: mtu3: set endpoint capabilities Anders Roxell
2026-10-28 14:15 ` [PATCH v10 28/30] usb: host: xhci: fix up after the resync Anders Roxell
2026-10-28 14:15 ` [PATCH v10 29/30] usb: cdns3: " Anders Roxell
2026-10-28 14:15 ` [PATCH v10 30/30] usb: dwc3: enable SUSPHY again after xhci is registered Anders Roxell
2026-10-30 14:28 ` [PATCH v10 00/30] usb: dwc3: part 2, make the resynced code work Quentin Schulz
2026-11-03 13:45 ` Anders Roxell
2026-11-04 17:51 ` Quentin Schulz
2026-11-06 10:57 ` Quentin Schulz [this message]
2026-11-06 16:04 ` Alexey Charkov
2026-11-07 8:35 ` Anders Roxell
2026-11-07 8:34 ` Anders Roxell
2026-11-03 9:42 ` Love Kumar
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=548adaa3-9d2f-4fa2-8fdf-7c537c4d153b@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=Thinh.Nguyen@synopsys.com \
--cc=alchark@flipper.net \
--cc=anders.roxell@linaro.org \
--cc=anshuld@ti.com \
--cc=dlechner@baylibre.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jerome.forissier@arm.com \
--cc=love.kumar@amd.com \
--cc=lukma@nabladev.com \
--cc=marek.vasut@mailbox.org \
--cc=michal.simek@amd.com \
--cc=mkorpershoek@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.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.