diff options
| author | Roger Quadros <rogerq@ti.com> | 2019-01-10 17:04:28 +0200 |
|---|---|---|
| committer | Felipe Balbi <felipe.balbi@linux.intel.com> | 2019-01-28 12:51:29 +0200 |
| commit | 169e3b68cadb5775daca009ced4faf01ffd97dcf (patch) | |
| tree | b2d9301d52f637240e8f69f125683ba0e6d5e94b /drivers/usb/dwc3 | |
| parent | 1c1a3ddae9782ba748f5ceb775ed13ef554e8994 (diff) | |
| download | linux-169e3b68cadb5775daca009ced4faf01ffd97dcf.tar.gz linux-169e3b68cadb5775daca009ced4faf01ffd97dcf.tar.bz2 linux-169e3b68cadb5775daca009ced4faf01ffd97dcf.zip | |
usb: dwc3: gadget: Fix OTG events when gadget driver isn't loaded
On v3.10a in dual-role mode, if port is in device mode
and gadget driver isn't loaded, the OTG event interrupts don't
come through.
It seems that if the core is configured to be OTG2.0 only,
then we can't leave the DCFG.DEVSPD at Super-speed (default)
if we expect OTG to work properly. It must be set to High-speed.
Fix this issue by configuring DCFG.DEVSPD to the supported
maximum speed at gadget init. Device tree still needs to provide
correct supported maximum speed for this to work.
This issue wasn't present on v2.40a but is seen on v3.10a.
It doesn't cause any side effects on v2.40a.
Signed-off-by: Roger Quadros <rogerq@ti.com>
Signed-off-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>
Diffstat (limited to 'drivers/usb/dwc3')
| -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 bed2ff42780b..d478d46847b6 100644 --- a/drivers/usb/dwc3/gadget.c +++ b/drivers/usb/dwc3/gadget.c @@ -3339,6 +3339,8 @@ int dwc3_gadget_init(struct dwc3 *dwc) goto err4; } + dwc3_gadget_set_speed(&dwc->gadget, dwc->maximum_speed); + return 0; err4: |