Re: [PATCH v9 00/26] usb: dwc3: part 2, make the resynced code work

[Anders Roxell <anders.roxell@linaro.org>]

On 2026-09-25 16:09, Siddharth Vadapalli wrote:

[...]

> I didn't see "unknown endpoint event 0" at that point, so this series seems
> to introduce a regression.

Hi Siddharth,

Thanks for looking. But that line can not show up on mainline.
dwc3_ep0_interrupt() has no default case there, so an event 0 on ep0
is dropped and nothing is printed. The dev_err() came with the resync
from Linux. So your logs do not tell us if the event is new.

To know if it is a regression we need the same print on both. Can you
run ums on AM62p twice, once on plain master and once with my series,
and send me what it prints?

On plain master:

  --- a/drivers/usb/dwc3/ep0.c
  +++ b/drivers/usb/dwc3/ep0.c
  @@ void dwc3_ep0_interrupt(struct dwc3 *dwc,
   	case DWC3_DEPEVT_EPCMDCMPLT:
   		break;
  +	default:
  +		printf("unknown ep0 event %d raw %08x\n",
  +		       event->endpoint_event, *(const u32 *)event);
  +		break;
   	}
   }

With my series:

  --- a/drivers/usb/dwc3/ep0.c
  +++ b/drivers/usb/dwc3/ep0.c
  @@ void dwc3_ep0_interrupt(struct dwc3 *dwc,
   	default:
   		dev_err(dwc->dev, "unknown endpoint event %d\n", event->endpoint_event);
  +		printf("unknown ep0 event %d raw %08x\n",
  +		       event->endpoint_event, *(const u32 *)event);
   		break;
   	}

If it shows up on master too then it is older than the series, and I can
look at it separately. If master is clean, then I broke it and it has
to be fixed in this series.

If it is easier for you, I can also do it myself with remote access
to an AM62p. Then I need the serial console and a way to power cycle
the board and load my own U-Boot. I also need the host that the USB
port is connected to, so I can run ums.

Cheers,
Anders