diff options
| author | Felipe Balbi <balbi@ti.com> | 2015-11-16 23:20:34 +0100 |
|---|---|---|
| committer | Felipe Balbi <balbi@ti.com> | 2015-12-15 16:12:41 +0100 |
| commit | b5d335e5ea6a60f5254c1f3d5fddd47f4531bccf (patch) | |
| tree | 5ae922db25fb3bd3c5dab47789506aa562c83408 /drivers/usb/dwc3/gadget.c | |
| parent | usb: dwc3: gadget: simplify next_request() return check (diff) | |
| download | linux-b5d335e5ea6a60f5254c1f3d5fddd47f4531bccf.tar.xz linux-b5d335e5ea6a60f5254c1f3d5fddd47f4531bccf.zip | |
usb: dwc3: ep0: fix setup_packet_pending initialization
It just ocurred to me that dwc3 already gives a
really hint of when a setup packet is pending and
that's the SETUP_PENDING TRB Status for EP0 IRQs.
Fix setup_packet_pending initialization based on
that. While at that, also make sure the comment in
gadget.c matches what code is doing.
Signed-off-by: Felipe Balbi <balbi@ti.com>
Diffstat (limited to 'drivers/usb/dwc3/gadget.c')
| -rw-r--r-- | drivers/usb/dwc3/gadget.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c index 3d131b7aae59..e4203b79908a 100644 --- a/drivers/usb/dwc3/gadget.c +++ b/drivers/usb/dwc3/gadget.c @@ -2230,8 +2230,8 @@ static void dwc3_gadget_reset_interrupt(struct dwc3 *dwc) * * Our suggested workaround is to follow the Disconnect * Event steps here, instead, based on a setup_packet_pending - * flag. Such flag gets set whenever we have a XferNotReady - * event on EP0 and gets cleared on XferComplete for the + * flag. Such flag gets set whenever we have a SETUP_PENDING + * status for EP0 TRBs and gets cleared on XferComplete for the * same endpoint. * * Refers to: |