diff options
| author | Peter Chen <[email protected]> | 2011-11-15 21:52:29 +0100 |
|---|---|---|
| committer | Rafael J. Wysocki <[email protected]> | 2011-11-15 21:52:29 +0100 |
| commit | af8db1508f2c9f3b6e633e2d2d906c6557c617f9 (patch) | |
| tree | 5df2fc9b5d3fad990c6eaf187ebbe5ba7ecdb872 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 6c81f90588972b8631bda4d538ffd0199a3e1b41 (diff) | |
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 <[email protected]>
Acked-by: Ming Lei <[email protected]>
Acked-by: Greg Kroah-Hartman <[email protected]>
Cc: [email protected]
Signed-off-by: Rafael J. Wysocki <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions