Lines Matching full:subsystem

54 are executed by the PM core for the device's subsystem that may be either of
67 If the subsystem chosen by applying the above rules doesn't provide the relevant
75 are referred to as subsystem-level callbacks in what follows.
86 The subsystem-level suspend callback, if present, is _entirely_ _responsible_
90 callback in a device driver as long as the subsystem-level suspend callback
93   * Once the subsystem-level suspend callback (or the driver suspend callback,
121 The subsystem-level resume callback, if present, is **entirely responsible** for
125 callback in a device driver as long as the subsystem-level resume callback knows
128   * Once the subsystem-level resume callback (or the driver resume callback, if
140 The idle callback (a subsystem-level one, if present, or the driver one) is
150 The action performed by the idle callback is totally dependent on the subsystem
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
347     - submit a request to execute the subsystem-level idle callback for the
352     - schedule the execution of the subsystem-level suspend callback for the
357     - schedule the execution of the subsystem-level suspend callback for the
367     - submit a request to execute the subsystem-level resume callback for the
424       to zero, the runtime PM helper functions can execute subsystem-level
429       field was previously zero, this prevents subsystem-level runtime PM
433       necessary to execute the subsystem-level resume callback for the device
441       necessary to execute the subsystem-level resume callback for the device to
590 if it is registered with a subsystem that may call back in) then the
597 request to execute the subsystem-level idle callback for the device at that
644 the subsystem-level system suspend callback is responsible for changing the
714     right before executing the subsystem-level .prepare() callback for it and
716     subsystem-level .suspend() callback for it.  In addition to that the PM core
718     device right before executing the subsystem-level .suspend_late() callback
722     every device right after executing the subsystem-level .resume_early()
723     callback and right after executing the subsystem-level .complete() callback
726 7. Generic subsystem callbacks
794 These functions are the defaults used by the PM core if a subsystem doesn't
799 subsystem-level dev_pm_ops structure.
829 As a consequence, the PM core will never directly inform the device's subsystem
856 device is automatically suspended (the subsystem or driver still has to call
882 Under some circumstances a driver or subsystem may want to prevent a device