Documentation/power/runtime_pm.rst

28 * Three device runtime PM callbacks in 'struct dev_pm_ops' (defined in
36 The runtime PM callbacks present in 'struct dev_pm_ops', the device runtime PM
40 2. Device Runtime PM Callbacks
43 There are three device runtime PM callbacks defined in 'struct dev_pm_ops'::
53 The ->runtime_suspend(), ->runtime_resume() and ->runtime_idle() callbacks
72 priority order of callbacks from high to low is: PM domain, device type, class
74 a low-priority one.  The PM domain, bus type, device type and class callbacks
75 are referred to as subsystem-level callbacks in what follows.
77 By default, the callbacks are always invoked in process context with interrupts
80 and ->runtime_idle() callbacks for the given device in atomic context with
164 that the following constraints are met with respect to runtime PM callbacks for
167 (1) The callbacks are mutually exclusive (e.g. it is forbidden to execute
172     of the other callbacks is being executed for the same device).
199     to execute it, the other callbacks will not be executed for the same device.
202     scheduled requests to execute the other callbacks for the same device,
244     - if set, there was a fatal error (one of the callbacks returned error code
279     - indicates that the device does not use the runtime PM callbacks (see
284     - indicates that the ->runtime_suspend() and ->runtime_resume() callbacks
431       callbacks described in Section 2 for the device
436       callbacks from being run for the device), make sure that all of the
496       callbacks to be invoked with interrupts off
500       the runtime-PM callbacks to be invoked with interrupts off
607 Moreover, the driver core prevents runtime PM callbacks from racing with the bus
619 drivers to make their ->remove() callbacks avoid races with runtime PM directly,
709 system suspend and resume callbacks for all of those devices, except for the
716 the runtime PM and system suspend/resume (and hibernation) callbacks by carrying
732 7. Generic subsystem callbacks
735 management callbacks provided by the PM core, defined in
801 provide its own callbacks for ->runtime_idle(), ->runtime_suspend(),
820 need of runtime PM callbacks; if the callbacks did exist, ->runtime_suspend()
831 ->runtime_idle(), ->runtime_suspend(), or ->runtime_resume() callbacks.
842 the runtime PM callbacks needs to be implemented, a platform dependent PM
845 in subsystems/drivers, the PM core allows runtime PM callbacks to be
900 synchronize ->runtime_suspend() callbacks with the arrival of I/O requests.