diff options
| author | Colin Cross <ccross@android.com> | 2011-08-10 11:41:59 -0500 |
|---|---|---|
| committer | mgross <mark.gross@intel.com> | 2011-11-09 12:24:30 -0800 |
| commit | 6202c2789c401f3b8e4aa1fd61e78277b4574fea (patch) | |
| tree | 90871d817e5e23ffce41efe2f0517d3757c32177 /Documentation | |
| parent | ba121e2c85a8daab10bd394a5a1e28f1fad41233 (diff) | |
| download | kernel-mfld-blackbay-6202c2789c401f3b8e4aa1fd61e78277b4574fea.tar.gz kernel-mfld-blackbay-6202c2789c401f3b8e4aa1fd61e78277b4574fea.tar.bz2 kernel-mfld-blackbay-6202c2789c401f3b8e4aa1fd61e78277b4574fea.zip | |
PM: runtime: add might_sleep to PM runtime functions
The list of functions that can be called in atomic context is
non-intuitive (pm_runtime_put_sync can not, but
pm_runtime_put_sync_suspend can, if pm_runtime_irq_safe has
been called?). The code is actively misleading - the entry
points all start with spin_lock_irqsave, suggesting they
are safe to call in atomic context, but may later
enable interrupts.
Add might_sleep_if to all the __pm_runtime_* entry points
to enforce correct usage.
Also add pm_runtime_put_sync_autosuspend to the list of
functions that can be called in atomic context.
Change-Id: Icac17a10d77c64d44bd2761a91a588dfd1d0c6f0
Signed-off-by: Colin Cross <ccross@android.com>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/power/runtime_pm.txt | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/Documentation/power/runtime_pm.txt b/Documentation/power/runtime_pm.txt index b24875b1ced..22852b3cf49 100644 --- a/Documentation/power/runtime_pm.txt +++ b/Documentation/power/runtime_pm.txt @@ -469,6 +469,7 @@ pm_runtime_autosuspend() pm_runtime_resume() pm_runtime_get_sync() pm_runtime_put_sync_suspend() +pm_runtime_put_sync_autosuspend() 5. Run-time PM Initialization, Device Probing and Removal |