PM / Runtime: Make documentation follow the new behavior of irq_safe
The runtime PM core code behavior related to the power.irq_safe device flag has changed recently and the documentation should be modified to reflect it. Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
This commit is contained in:
parent
fa8ce72393
commit
9075659219
@ -65,11 +65,12 @@ are referred to as subsystem-level callbacks in what follows.
|
|||||||
|
|
||||||
By default, the callbacks are always invoked in process context with interrupts
|
By default, the callbacks are always invoked in process context with interrupts
|
||||||
enabled. However, subsystems can use the pm_runtime_irq_safe() helper function
|
enabled. However, subsystems can use the pm_runtime_irq_safe() helper function
|
||||||
to tell the PM core that a device's ->runtime_suspend() and ->runtime_resume()
|
to tell the PM core that their ->runtime_suspend(), ->runtime_resume() and
|
||||||
callbacks should be invoked in atomic context with interrupts disabled.
|
->runtime_idle() callbacks may be invoked in atomic context with interrupts
|
||||||
This implies that these callback routines must not block or sleep, but it also
|
disabled for a given device. This implies that the callback routines in
|
||||||
means that the synchronous helper functions listed at the end of Section 4 can
|
question must not block or sleep, but it also means that the synchronous helper
|
||||||
be used within an interrupt handler or in an atomic context.
|
functions listed at the end of Section 4 may be used for that device within an
|
||||||
|
interrupt handler or generally in an atomic context.
|
||||||
|
|
||||||
The subsystem-level suspend callback is _entirely_ _responsible_ for handling
|
The subsystem-level suspend callback is _entirely_ _responsible_ for handling
|
||||||
the suspend of the device as appropriate, which may, but need not include
|
the suspend of the device as appropriate, which may, but need not include
|
||||||
|
Loading…
Reference in New Issue
Block a user