Lines Matching refs:devices

7 Device power management (PM) on Zephyr is a feature that enables devices to
26 devices, the decision to suspend or resume a device can also be
35   power state of devices. They interact directly with the hardware to
36   put devices into low-power states (suspend) when they are not in
39   by Zephyr to control the power state of devices.
45   when to suspend or resume devices. For example, a networking
65 does not need to spend time suspending and resuming devices that are
76 devices are suspended along with the system entering a CPU (or SoC) power state.
83 management and then suspend devices before changing state. The subsystem takes
84 care of suspending devices following their initialization order, ensuring that
86 from a sleep state, devices are resumed in the opposite order that they were
89 The decision about suspending devices when entering a low power state is done based on the
126 - For devices that can not make any power management decision and have to be
128   external entity (e.g Host CPU). In this scenario, some devices have to be
150    state and devices are resumed by the first core that becomes active.
198 Drivers initialize devices using macros. See :ref:`device_model_api` for
273         devices:
283         devices:
298 subsystem can suspend devices, as described in :ref:`pm-device-system-pm`. This
317 state. Some devices may have dependencies on the system power
319 supply power to peripheral devices, leading to problems if the device
323 To avoid this sort of problem, devices must :ref:`get and release lock <pm-policy-power-states>`
326 Zephyr provides a mechanism for devices to declare which power states cause power
330 Once this feature is enabled, devices must declare in devicetree which
371 After that devices can lock these state calling
403 Some devices are capable of waking the system up from a sleep state.
425 By default, "wakeup" capable devices do not have this functionality enabled
432    devices that should not be suspended.