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. Can you run the same tests with v11? It is on [1], on top of main ab4dc5aacf95. If it still fails, a register dump would help. No patch is needed, md is enough. Please run this on main and on v11, once after "usb reset" and once after the failed write. Not before "usb reset", because the controllers may not be probed then. # P0 lower, usb@fc400000 md.l 0xfc40c100 0x14 md.l 0xfc40c19c 1 md.l 0xfc40c200 1 md.l 0xfc40c2c0 1 md.l 0xfc40c630 1 md.l 0xfc400000 2 md.l 0xfc400420 8 # P2 upper, usb@fcd00000 md.l 0xfcd0c100 0x14 md.l 0xfcd0c19c 1 md.l 0xfcd0c200 1 md.l 0xfcd0c2c0 1 md.l 0xfcd0c630 1 md.l 0xfcd00000 2 md.l 0xfcd00420 8 If CAPLENGTH (low byte at the base) is not 0x20, PORTSC is at base + CAPLENGTH + 0x400 instead of base + 0x420. Cheers, Anders [1] https://github.com/roxell/u-boot/tree/usb_dwc3_sync_v11
