| Message ID | 20240103023023.477-1-quic_wcheng@quicinc.com (mailing list archive) |
|---|---|
| State | Superseded |
| Headers | show |
| Series | usb: dwc3: gadget: Queue PM runtime idle on disconnect event | expand |
On Tue, Jan 02, 2024 at 06:30:23PM -0800, Wesley Cheng wrote: > There is a scenario where DWC3 runtime suspend is blocked due to the > dwc->connected flag still being true while PM usage_count is zero after > DWC3 giveback is completed and the USB gadget session is being terminated. > This leads to a case where nothing schedules a PM runtime idle for the > device. > > The exact condition is seen with the following sequence: > 1. USB bus reset is issued by the host > 2. Shortly after, or concurrently, a USB PD DR SWAP request is received > (sink->source) > 3. USB bus reset event handler runs and issues > dwc3_stop_active_transfers(), and pending transfer are stopped > 4. DWC3 usage_count decremented to 0, and runtime idle occurs while > dwc->connected == true, returns -EBUSY > 5. DWC3 disconnect event seen, dwc->connected set to false due to DR > swap handling > 6. No runtime idle after this point > > Address this by issuing an asynchronous PM runtime idle call after the > disconnect event is completed, as it modifies the dwc->connected flag, > which is what blocks the initial runtime idle. > > Fixes: fc8bb91bc83e ("usb: dwc3: implement runtime PM") > Signed-off-by: Wesley Cheng <quic_wcheng@quicinc.com> > --- > drivers/usb/dwc3/gadget.c | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c > index 858fe4c299b7..de6056277f94 100644 > --- a/drivers/usb/dwc3/gadget.c > +++ b/drivers/usb/dwc3/gadget.c > @@ -3973,6 +3973,13 @@ static void dwc3_gadget_disconnect_interrupt(struct dwc3 *dwc) > usb_gadget_set_state(dwc->gadget, USB_STATE_NOTATTACHED); > > dwc3_ep0_reset_state(dwc); > + > + /* > + * Request PM idle to address condition where usage count is > + * already decremented to zero, but waiting for the disconnect > + * interrupt to set dwc->connected to FALSE. > + */ > + pm_request_idle(dwc->dev); > } > > static void dwc3_gadget_reset_interrupt(struct dwc3 *dwc) Hi, This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree. You are receiving this message because of the following common error(s) as indicated below: - You have marked a patch with a "Fixes:" tag for a commit that is in an older released kernel, yet you do not have a cc: stable line in the signed-off-by area at all, which means that the patch will not be applied to any older kernel releases. To properly fix this, please follow the documented rules in the Documentation/process/stable-kernel-rules.rst file for how to resolve this. If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers. thanks, greg k-h's patch email bot
diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c index 858fe4c299b7..de6056277f94 100644 --- a/drivers/usb/dwc3/gadget.c +++ b/drivers/usb/dwc3/gadget.c @@ -3973,6 +3973,13 @@ static void dwc3_gadget_disconnect_interrupt(struct dwc3 *dwc) usb_gadget_set_state(dwc->gadget, USB_STATE_NOTATTACHED); dwc3_ep0_reset_state(dwc); + + /* + * Request PM idle to address condition where usage count is + * already decremented to zero, but waiting for the disconnect + * interrupt to set dwc->connected to FALSE. + */ + pm_request_idle(dwc->dev); } static void dwc3_gadget_reset_interrupt(struct dwc3 *dwc)
There is a scenario where DWC3 runtime suspend is blocked due to the dwc->connected flag still being true while PM usage_count is zero after DWC3 giveback is completed and the USB gadget session is being terminated. This leads to a case where nothing schedules a PM runtime idle for the device. The exact condition is seen with the following sequence: 1. USB bus reset is issued by the host 2. Shortly after, or concurrently, a USB PD DR SWAP request is received (sink->source) 3. USB bus reset event handler runs and issues dwc3_stop_active_transfers(), and pending transfer are stopped 4. DWC3 usage_count decremented to 0, and runtime idle occurs while dwc->connected == true, returns -EBUSY 5. DWC3 disconnect event seen, dwc->connected set to false due to DR swap handling 6. No runtime idle after this point Address this by issuing an asynchronous PM runtime idle call after the disconnect event is completed, as it modifies the dwc->connected flag, which is what blocks the initial runtime idle. Fixes: fc8bb91bc83e ("usb: dwc3: implement runtime PM") Signed-off-by: Wesley Cheng <quic_wcheng@quicinc.com> --- drivers/usb/dwc3/gadget.c | 7 +++++++ 1 file changed, 7 insertions(+)