diff options
| author | Thinh Nguyen <Thinh.Nguyen@synopsys.com> | 2020-03-29 16:13:16 -0700 |
|---|---|---|
| committer | Felipe Balbi <balbi@kernel.org> | 2020-05-05 11:00:13 +0300 |
| commit | f7ac582effc6ee416eb51e0c3e55836aaf7231ac (patch) | |
| tree | 3149155bdb3f3acc401f2cf8adf9a148cdb7d536 /drivers/usb/dwc3/gadget.c | |
| parent | 36f05d36b03523da906cf2ae70ec31af6f57e94c (diff) | |
| download | linux-f7ac582effc6ee416eb51e0c3e55836aaf7231ac.tar.bz2 | |
usb: dwc3: gadget: WARN on no-resource status
If the driver issued START_TRANSFER and received a no-resource status,
then generally there are a few reasons for this:
1) The driver did not allocate resource for the endpoint during
power-on-reset initialization.
2) The transfer resource was reset. At this moment, we don't do this in
the driver, but it occurs when the driver issues START_CONFIG cmd to ep0
with resource index=2.
3) The driver issues the START_TRANSFER command to an already started
endpoint. Usually, this is because the END_TRANSFER command hasn't
completed yet.
Print out a warning to help debug this issue in the driver.
Signed-off-by: Thinh Nguyen <thinhn@synopsys.com>
Signed-off-by: Felipe Balbi <balbi@kernel.org>
Diffstat (limited to 'drivers/usb/dwc3/gadget.c')
| -rw-r--r-- | drivers/usb/dwc3/gadget.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c index dc03c04677b2..a0555252dee0 100644 --- a/drivers/usb/dwc3/gadget.c +++ b/drivers/usb/dwc3/gadget.c @@ -356,6 +356,8 @@ int dwc3_send_gadget_ep_cmd(struct dwc3_ep *dep, unsigned cmd, ret = 0; break; case DEPEVT_TRANSFER_NO_RESOURCE: + dev_WARN(dwc->dev, "No resource for %s\n", + dep->name); ret = -EINVAL; break; case DEPEVT_TRANSFER_BUS_EXPIRY: |