Lines Matching full:execute

167 (1) The callbacks are mutually exclusive (e.g. it is forbidden to execute
175     devices (i.e. the PM core will only execute ->runtime_idle() or
185     PM core will only execute ->runtime_resume() for the devices the runtime
192     to execute it, ->runtime_idle() will not be executed for the same device.
194   * A request to execute or to schedule the execution of ->runtime_suspend()
195     will cancel any pending requests to execute ->runtime_idle() for the same
199     to execute it, the other callbacks will not be executed for the same device.
201   * A request to execute ->runtime_resume() will cancel any pending or
202     scheduled requests to execute the other callbacks for the same device,
316     - execute the subsystem-level idle callback for the device; returns an
322     - execute the subsystem-level suspend callback for the device; returns 0 on
335     - execute the subsystem-level resume callback for the device; returns 0 on
343     - submit a request to execute the subsystem-level idle callback for the
363     - submit a request to execute the subsystem-level resume callback for the
416       to zero, the runtime PM helper functions can execute subsystem-level
425       necessary to execute the subsystem-level resume callback for the device
433       necessary to execute the subsystem-level resume callback for the device to
518 It is safe to execute the following helper functions from interrupt context:
581 Note, if the device may execute pm_runtime calls during the probe (such as
589 request to execute the subsystem-level idle callback for the device at that
694 left in runtime suspend.  If that happens, the PM core will not execute any