Lines Matching refs:subsystem

48 are executed by the PM core for the device's subsystem that may be either of
61 If the subsystem chosen by applying the above rules doesn't provide the relevant
69 are referred to as subsystem-level callbacks in what follows.
80 The subsystem-level suspend callback, if present, is _entirely_ _responsible_
84 callback in a device driver as long as the subsystem-level suspend callback
87   * Once the subsystem-level suspend callback (or the driver suspend callback,
115 The subsystem-level resume callback, if present, is _entirely_ _responsible_ for
119 callback in a device driver as long as the subsystem-level resume callback knows
122   * Once the subsystem-level resume callback (or the driver resume callback, if
134 The idle callback (a subsystem-level one, if present, or the driver one) is
144 The action performed by the idle callback is totally dependent on the subsystem
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
343     - schedule the execution of the subsystem-level suspend callback for the
348     - schedule the execution of the subsystem-level suspend 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
404       field was previously zero, this prevents subsystem-level runtime PM
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
561 request to execute the subsystem-level idle callback for the device at that
603 the subsystem-level system suspend callback is responsible for changing the
673     right before executing the subsystem-level .prepare() callback for it and
675     subsystem-level .suspend() callback for it.  In addition to that the PM core
677     device right before executing the subsystem-level .suspend_late() callback
681     every device right after executing the subsystem-level .resume_early()
682     callback and right after executing the subsystem-level .complete() callback
685 7. Generic subsystem callbacks
753 These functions are the defaults used by the PM core, if a subsystem doesn't
758 subsystem-level dev_pm_ops structure.
787 As a consequence, the PM core will never directly inform the device's subsystem
804 device is automatically suspended (the subsystem or driver still has to call
831 Under some circumstances a driver or subsystem may want to prevent a device