diff options
| author | Gary Bisson <gary.bisson@boundarydevices.com> | 2021-01-25 17:19:34 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2021-02-10 09:21:07 +0100 |
| commit | 0bd7046e42448e974b564d297d59ea29b2cf222f (patch) | |
| tree | 1d325011392844ff2606a084f714a40dd1d2e496 /drivers | |
| parent | e5fc959f1a4ba4b6ba9d9c1d045017fa6a6b3ac7 (diff) | |
| download | linux-0bd7046e42448e974b564d297d59ea29b2cf222f.tar.gz linux-0bd7046e42448e974b564d297d59ea29b2cf222f.tar.bz2 linux-0bd7046e42448e974b564d297d59ea29b2cf222f.zip | |
usb: dwc3: fix clock issue during resume in OTG mode
commit 0e5a3c8284a30f4c43fd81d7285528ece74563b5 upstream.
Commit fe8abf332b8f ("usb: dwc3: support clocks and resets for DWC3
core") introduced clock support and a new function named
dwc3_core_init_for_resume() which enables the clock before calling
dwc3_core_init() during resume as clocks get disabled during suspend.
Unfortunately in this commit the DWC3_GCTL_PRTCAP_OTG case was forgotten
and therefore during resume, a platform could call dwc3_core_init()
without re-enabling the clocks first, preventing to resume properly.
So update the resume path to call dwc3_core_init_for_resume() as it
should.
Fixes: fe8abf332b8f ("usb: dwc3: support clocks and resets for DWC3 core")
Cc: stable@vger.kernel.org
Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
Link: https://lore.kernel.org/r/20210125161934.527820-1-gary.bisson@boundarydevices.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers')
| -rw-r--r-- | drivers/usb/dwc3/core.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c index 86b1cfbe48a0..e890c26b6c82 100644 --- a/drivers/usb/dwc3/core.c +++ b/drivers/usb/dwc3/core.c @@ -1700,7 +1700,7 @@ static int dwc3_resume_common(struct dwc3 *dwc, pm_message_t msg) if (PMSG_IS_AUTO(msg)) break; - ret = dwc3_core_init(dwc); + ret = dwc3_core_init_for_resume(dwc); if (ret) return ret; |