On Mon, Sep 02, 2024, Selvarasu Ganesan wrote: > > I would like to reconfirm from our end that in our failure scenario, we > observe that DWC3_EVENT_PENDING is set in evt->flags when the dwc3 > resume sequence is executed, and the dwc->pending_events flag is not > being set. > If the controller is stopped, no event is generated until it's restarted again. (ie, you should not see GEVNTCOUNT updated after clearing DCTL.run_stop). If there's no event, no interrupt assertion should come from the controller. If the pending_events is not set and you still see this failure, then likely that the controller had started, and the interrupt is generated from the controller event. This occurs along with the interrupt generated from your connection notification from your setup. Check your platform and internal team, what condition would cause the setup to generate the interrupt and what condition would stop this custom connection interrupt assertion? This is outside of what's defined by the flow of the controller. BR, Thinh
