summaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorPeter Chen <peter.chen@freescale.com>2011-11-15 21:52:29 +0100
committerRafael J. Wysocki <rjw@sisk.pl>2011-11-15 21:52:29 +0100
commitaf8db1508f2c9f3b6e633e2d2d906c6557c617f9 (patch)
tree5df2fc9b5d3fad990c6eaf187ebbe5ba7ecdb872 /include/linux
parent6c81f90588972b8631bda4d538ffd0199a3e1b41 (diff)
downloadlinux-3.10-af8db1508f2c9f3b6e633e2d2d906c6557c617f9.tar.gz
linux-3.10-af8db1508f2c9f3b6e633e2d2d906c6557c617f9.tar.bz2
linux-3.10-af8db1508f2c9f3b6e633e2d2d906c6557c617f9.zip
PM / driver core: disable device's runtime PM during shutdown
There may be an issue when the user issue "reboot/shutdown" command, then the device has shut down its hardware, after that, this runtime-pm featured device's driver will probably be scheduled to do its suspend routine, and at its suspend routine, it may access hardware, but the device has already shutdown physically, then the system hang may be occurred. I ran out this issue using an auto-suspend supported USB devices, like 3G modem, keyboard. The usb runtime suspend routine may be scheduled after the usb controller has been shut down, and the usb runtime suspend routine will try to suspend its roothub(controller), it will access register, then the system hang occurs as the controller is shutdown. Signed-off-by: Peter Chen <peter.chen@freescale.com> Acked-by: Ming Lei <tom.leiming@gmail.com> Acked-by: Greg Kroah-Hartman <gregkh@suse.de> Cc: stable@kernel.org Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions