diff options
| author | Felipe Balbi <balbi@ti.com> | 2012-10-04 11:58:00 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-10-28 10:56:14 -0700 |
| commit | 740b0a623f05bbb796a441e2c51ebfe37eef1c21 (patch) | |
| tree | be446d9435c065274e73d4479460901b36846c52 | |
| parent | 11c7a299c9846320859916e81f0f5d38fc596a4d (diff) | |
| download | linux-stable-740b0a623f05bbb796a441e2c51ebfe37eef1c21.tar.gz linux-stable-740b0a623f05bbb796a441e2c51ebfe37eef1c21.tar.bz2 linux-stable-740b0a623f05bbb796a441e2c51ebfe37eef1c21.zip | |
usb: dwc3: gadget: fix 'endpoint always busy' bug
commit 041d81f493d90c940ec41f0ec98bc7c4f2fba431 upstream.
If a USB transfer has already been started, meaning
we have already issued StartTransfer command to that
particular endpoint, DWC3_EP_BUSY flag has also
already been set.
When we try to cancel this transfer which is already
in controller's cache, we will not receive XferComplete
event and we must clear DWC3_EP_BUSY in order to allow
subsequent requests to be properly started.
The best place to clear that flag is right after issuing
DWC3_DEPCMD_ENDTRANSFER.
Reported-by: Moiz Sonasath <m-sonasath@ti.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| -rw-r--r-- | drivers/usb/dwc3/gadget.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c index c2813c2b005a..eb0fd100cfa8 100644 --- a/drivers/usb/dwc3/gadget.c +++ b/drivers/usb/dwc3/gadget.c @@ -1899,6 +1899,7 @@ static void dwc3_stop_active_transfer(struct dwc3 *dwc, u32 epnum) ret = dwc3_send_gadget_ep_cmd(dwc, dep->number, cmd, ¶ms); WARN_ON_ONCE(ret); dep->resource_index = 0; + dep->flags &= ~DWC3_EP_BUSY; } static void dwc3_stop_active_transfers(struct dwc3 *dwc) |