summaryrefslogtreecommitdiffstats
path: root/scripts/gcc-version.sh
diff options
context:
space:
mode:
authorJon Hunter <jon-hunter@ti.com>2009-08-12 17:57:59 +0200
committerGreg Kroah-Hartman <gregkh@suse.de>2009-09-23 15:46:33 +0200
commit015798b2f166725b1dae2b07b5ffb127ab187be0 (patch)
tree8e737d2a85ba93bbe135051c426993f9cc272f2a /scripts/gcc-version.sh
parentUSB: otg: twl4030-usb.c: mark .init as subsys_initcall_sync (diff)
downloadlinux-015798b2f166725b1dae2b07b5ffb127ab187be0.tar.xz
linux-015798b2f166725b1dae2b07b5ffb127ab187be0.zip
USB: EHCI: ensure all watchdog timer events are deleted when suspending usb
This patch was previously discussed in the following thread: http://thread.gmane.org/gmane.linux.usb.general/19472/focus=19484 On the OMAP3 device the usbhost controller is in a separate internal power-domain. So when the usbhost is inactive or suspend is called, we can disable clocks and power-down the usbhost to save power. Recently we found that after calling ehci_bus_suspend() and disabling the usbhost clocks we would see the ehci watchdog timer event fire. This was causing a kernel panic because the usbhost controllers clocks were disabled and inside the watchdog timer function the clocks were not being re-enabled, so when the ehci registers were accessed this resulted in a CPU data-abort. To avoid this panic, per recommendation from Alan Stern (see above thread), we make sure any pending timer events (that may have been scheduled by calling ehci_work within the ehci_bus_suspend() function) are deleted before returning. Signed-off-by: Fei Yang <fei.yang@motorola.com> Signed-off-by: Jon Hunter <jon-hunter@ti.com> Acked-by: Alan Stern <stern@rowland.harvard.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'scripts/gcc-version.sh')
0 files changed, 0 insertions, 0 deletions