diff options
author | Rafael J. Wysocki <rjw@sisk.pl> | 2011-09-27 21:54:52 +0200 |
---|---|---|
committer | Rafael J. Wysocki <rjw@sisk.pl> | 2011-09-27 21:54:52 +0200 |
commit | ad3c36a534bc7b945d7bffdda1c62e13bf93489a (patch) | |
tree | 5f7520f575891716577de33176713b8cb13a22d5 /kernel/trace | |
parent | 30b1a7a32ca48fd8758f8ca44d60deebc0aa3d72 (diff) | |
download | op-kernel-dev-ad3c36a534bc7b945d7bffdda1c62e13bf93489a.zip op-kernel-dev-ad3c36a534bc7b945d7bffdda1c62e13bf93489a.tar.gz |
PM / Runtime: Don't run callbacks under lock for power.irq_safe set
The rpm_suspend() and rpm_resume() routines execute subsystem or PM
domain callbacks under power.lock if power.irq_safe is set for the
given device. This is inconsistent with that rpm_idle() does after
commit 02b2677 (PM / Runtime: Allow _put_sync() from
interrupts-disabled context) and is problematic for subsystems and PM
domains wanting to use power.lock for synchronization in their
runtime PM callbacks.
This change requires the code checking if the device's runtime PM
status is RPM_SUSPENDING or RPM_RESUMING to be modified too, to take
the power.irq_safe set case into account (that code wasn't reachable
before with power.irq_safe set, because it's executed with the
device's power.lock held).
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Reviewed-by: Ming Lei <tom.leiming@gmail.com>
Reviewed-by: Kevin Hilman <khilman@ti.com>
Diffstat (limited to 'kernel/trace')
0 files changed, 0 insertions, 0 deletions