summaryrefslogtreecommitdiff
path: root/drivers/usb/common
diff options
context:
space:
mode:
authorSebastian Andrzej Siewior <bigeasy@linutronix.de>2014-10-27 09:49:42 (GMT)
committerFelipe Balbi <balbi@ti.com>2014-11-03 16:01:23 (GMT)
commit3e87d9a3dee0ad5416c3fb599a6019a24bfe6e64 (patch)
tree4adef13b58d5048bac3cfb70c9f2fc2865031b46 /drivers/usb/common
parent7b093f773b85dd816c5717193ec94a7cfec73a09 (diff)
downloadlinux-3e87d9a3dee0ad5416c3fb599a6019a24bfe6e64.tar.xz
usb: musb: core: use ->resume instead ->resume_noirq
In commit 0ec8fd70fb ("USB: musb: fix possible panic while resuming") musb_resume() became musb_resume_early() in order to enable the clocks early on resume. This piece of the resume code was removed later in commit 034917612 ("usb: musb: move clock handling to glue layer"). In between the function was renamed from musb_resume_early() to musb_resume_noirq() by commit commit 48fea9659e ("USB: Rework musb suspend()/resume_early()"). Now I see that first musb_core is resumed followed by phy and glue layer and I ask myself is this really what we intend to do? This kind of revoked the purpose of the first commit (0ec8fd70fb). Because of this and because it looks wrong to resume (core) before the glue layer I push it to the ->resume callback. Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de> Signed-off-by: Felipe Balbi <balbi@ti.com>
Diffstat (limited to 'drivers/usb/common')
0 files changed, 0 insertions, 0 deletions