diff options
author | Douglas Anderson <dianders@chromium.org> | 2019-04-16 14:53:49 -0700 |
---|---|---|
committer | Felipe Balbi <felipe.balbi@linux.intel.com> | 2019-05-03 09:13:47 +0300 |
commit | c40cf7705e13d288d900e044c0a2f756e9e4909a (patch) | |
tree | 31ab9133f03c69cda3587744766a8ce59a72eddb /mm/page-writeback.c | |
parent | cc389eaabd7082a14e46aaa5a02f87c9eef37d7f (diff) | |
download | linux-c40cf7705e13d288d900e044c0a2f756e9e4909a.tar.bz2 |
usb: dwc2: optionally assert phy reset when waking up
On the rk3288 USB host-only port (the one that's not the OTG-enabled
port) the PHY can get into a bad state when a wakeup is asserted (not
just a wakeup from full system suspend but also a wakeup from
autosuspend).
We can get the PHY out of its bad state by asserting its "port reset",
but unfortunately that seems to assert a reset onto the USB bus so it
could confuse things if we don't actually deenumerate / reenumerate the
device.
We can also get the PHY out of its bad state by fully resetting it using
the reset from the CRU (clock reset unit), which does a more full
reset. The CRU-based reset appears to actually cause devices on the bus
to be removed and reinserted, which fixes the problem (albeit in a hacky
way).
It's unfortunate that we need to do a full re-enumeration of devices at
wakeup time, but this is better than alternative of letting the bus get
wedged.
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Signed-off-by: Yunzhi Li <lyz@rock-chips.com>
Signed-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>
Diffstat (limited to 'mm/page-writeback.c')
0 files changed, 0 insertions, 0 deletions