Lines Matching refs:execute

161 (1) The callbacks are mutually exclusive (e.g. it is forbidden to execute
169     devices (i.e. the PM core will only execute ->runtime_idle() or
179     PM core will only execute ->runtime_resume() for the devices the runtime
186     to execute it, ->runtime_idle() will not be executed for the same device.
188   * A request to execute or to schedule the execution of ->runtime_suspend()
189     will cancel any pending requests to execute ->runtime_idle() for the same
193     to execute it, the other callbacks will not be executed for the same device.
195   * A request to execute ->runtime_resume() will cancel any pending or
196     scheduled requests to execute the other callbacks for the same device,
311     - execute the subsystem-level idle callback for the device; returns an
317     - execute the subsystem-level suspend callback for the device; returns 0 on
330     - execute the subsystem-level resume callback for the device; returns 0 on
338     - submit a request to execute the subsystem-level idle callback for the
358     - submit a request to execute the subsystem-level resume callback for the
399       to zero, the runtime PM helper functions can execute subsystem-level
408       necessary to execute the subsystem-level resume callback for the device
416       necessary to execute the subsystem-level resume callback for the device to
493 It is safe to execute the following helper functions from interrupt context:
555 Note, if the device may execute pm_runtime calls during the probe (such as
563 request to execute the subsystem-level idle callback for the device at that
663 left in runtime suspend.  If that happens, the PM core will not execute any