Lines Matching refs:callbacks

23 * Three device runtime PM callbacks in 'struct dev_pm_ops' (defined in
31 The runtime PM callbacks present in 'struct dev_pm_ops', the device runtime PM
37 There are three device runtime PM callbacks defined in 'struct dev_pm_ops':
47 The ->runtime_suspend(), ->runtime_resume() and ->runtime_idle() callbacks
66 priority order of callbacks from high to low is: PM domain, device type, class
68 a low-priority one.  The PM domain, bus type, device type and class callbacks
69 are referred to as subsystem-level callbacks in what follows.
71 By default, the callbacks are always invoked in process context with interrupts
74 and ->runtime_idle() callbacks for the given device in atomic context with
158 that the following constraints are met with respect to runtime PM callbacks for
161 (1) The callbacks are mutually exclusive (e.g. it is forbidden to execute
166     of the other callbacks is being executed for the same device).
193     to execute it, the other callbacks will not be executed for the same device.
196     scheduled requests to execute the other callbacks for the same device,
237     - if set, there was a fatal error (one of the callbacks returned error code
271     - indicates that the device does not use the runtime PM callbacks (see
276     - indicates that the ->runtime_suspend() and ->runtime_resume() callbacks
400       callbacks described in Section 2 for the device
405       callbacks from being run for the device), make sure that all of the
465       callbacks to be invoked with interrupts off
469       the runtime-PM callbacks to be invoked with interrupts off
567 Moreover, the driver core prevents runtime PM callbacks from racing with the bus
579 drivers to make their ->remove() callbacks avoid races with runtime PM directly,
664 system suspend and resume callbacks for all of those devices, except for the
671 the runtime PM and system suspend/resume (and hibernation) callbacks by carrying
687 7. Generic subsystem callbacks
690 management callbacks provided by the PM core, defined in
756 provide its own callbacks for ->runtime_idle(), ->runtime_suspend(),
774 need of runtime PM callbacks; if the callbacks did exist, ->runtime_suspend()
785 ->runtime_idle(), ->runtime_suspend(), or ->runtime_resume() callbacks.
845 synchronize ->runtime_suspend() callbacks with the arrival of I/O requests.