mirror of
https://github.com/torvalds/linux.git
synced 2026-06-08 14:42:37 +02:00
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> |
||
|---|---|---|
| .. | ||
| clock_ops.c | ||
| generic_ops.c | ||
| main.c | ||
| Makefile | ||
| opp.c | ||
| power.h | ||
| runtime.c | ||
| sysfs.c | ||
| trace.c | ||
| wakeup.c | ||