summaryrefslogtreecommitdiff
path: root/block
diff options
context:
space:
mode:
authorNeil Zhang <zhangwm@marvell.com>2012-07-10 10:07:07 +0800
committerFelipe Balbi <balbi@ti.com>2012-08-23 11:04:17 +0300
commit11c37c8b64b9d9d4ab19d387e6028eee3ec188d3 (patch)
treec346f8d7afdcdc22deac0b18e1cd627cc83fce31 /block
parent1dcaa252fdf01e4ba49ece156812043baf01c7cc (diff)
downloadlinux-3.10-11c37c8b64b9d9d4ab19d387e6028eee3ec188d3.tar.gz
linux-3.10-11c37c8b64b9d9d4ab19d387e6028eee3ec188d3.tar.bz2
linux-3.10-11c37c8b64b9d9d4ab19d387e6028eee3ec188d3.zip
usb: gadget: mv_udc: fix boot up hang
Fix boot up hang when enable udc without otg enabled. The root cause is that the clock will be shut down when probe routine is finished because of clock gating. When a gadget driver is registered at this time, it will call mv_udc_start which in turn will call mv_udc_vbus_session. If there is no cable attached at the boot up time, the vbus is low, so it will call stop_activity path without clock enabled which will cause system hang then. Actually, we need't go this path when clock is disabled, what we need to do is just jump out. Signed-off-by: Neil Zhang <zhangwm@marvell.com> Signed-off-by: Felipe Balbi <balbi@ti.com>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions