summaryrefslogtreecommitdiff
path: root/drivers/usb/musb/musb_io.h
diff options
context:
space:
mode:
authorAndreas Kemnade <andreas@kemnade.info>2018-02-20 16:30:10 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-02-20 17:02:46 +0300
commit17539f2f4f0b7fa906b508765c8ada07a1e45f52 (patch)
tree0f9396e4daf484cbf0842cd50aa9fe690646fcc8 /drivers/usb/musb/musb_io.h
parentfc19b1d09414912a327cf0a4b5ba2050ac7ad59d (diff)
downloadlinux-17539f2f4f0b7fa906b508765c8ada07a1e45f52.tar.xz
usb: musb: fix enumeration after resume
On dm3730 there are enumeration problems after resume. Investigation led to the cause that the MUSB_POWER_SOFTCONN bit is not set. If it was set before suspend (because it was enabled via musb_pullup()), it is set in musb_restore_context() so the pullup is enabled. But then musb_start() is called which overwrites MUSB_POWER and therefore disables MUSB_POWER_SOFTCONN, so no pullup is enabled and the device is not enumerated. So let's do a subset of what musb_start() does in the same way as musb_suspend() does it. Platform-specific stuff it still called as there might be some phy-related stuff which needs to be enabled. Also interrupts are enabled, as it was the original idea of calling musb_start() in musb_resume() according to Commit 6fc6f4b87cb3 ("usb: musb: Disable interrupts on suspend, enable them on resume") Signed-off-by: Andreas Kemnade <andreas@kemnade.info> Tested-by: Tony Lindgren <tony@atomide.com> Signed-off-by: Bin Liu <b-liu@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/usb/musb/musb_io.h')
0 files changed, 0 insertions, 0 deletions