PM: runtime: add might_sleep to PM runtime functions
authorColin Cross <ccross@android.com>
Wed, 10 Aug 2011 16:41:59 +0000 (11:41 -0500)
committerDan Willemsen <dwillemsen@nvidia.com>
Thu, 1 Dec 2011 05:39:08 +0000 (21:39 -0800)
commitd69a23cedf782704f6155c2971e836d9b30a2157
tree4cbfa17bff2e47aaeb49fc372580c8b3f755615d
parentb761d8388ec21a1da06851ac9ab33bdf755f50ec
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>
Documentation/power/runtime_pm.txt
drivers/base/power/runtime.c