Lines Matching refs:devices
10 devices. For general description of the kernel's interfaces related to device
11 power management refer to Documentation/power/devices.txt and
28 devices into states in which they draw less power (low-power states) at the
38 PCI devices may be put into low-power states in two ways, by using the device
75 The implementation of the PCI PM Spec is optional for conventional PCI devices,
76 but it is mandatory for PCI Express devices. If a device supports the PCI PM
81 The PCI PM Spec defines 4 operating states for devices (D0-D3) and for buses
87 one is D3hot, referred to as the software accessible D3, because devices can be
88 programmed to go into it. The second one, D3cold, is the state that PCI devices
92 removed from all devices on the bus.
102 PCI devices supporting the PCI PM Spec can be programmed to go to any of the
128 PCI devices supporting the PCI PM Spec can be programmed to generate PMEs
137 The platform firmware support for the power management of PCI devices is
154 associated with any particular devices, and device control methods, that have
157 only be used to handle devices that the BIOS writer knew about in advance. The
160 The ACPI specification assumes that devices can be in one of four power states
181 However, quite often the power states of devices are changed during a
197 Wakeup signals generated by PCI devices, either as native PCI PMEs, or as
202 put the devices generating them into the full-power state and take care of the
206 On ACPI-based systems wakeup signals sent by conventional PCI devices are
218 devices below the bridge (this also is the case for root bridges) and, for
219 example, native PCI PMEs from devices unknown to the system's ACPI BIOS may be
238 conventional PCI devices on systems that are not ACPI-based, but there is one
239 for PCI Express devices. Namely, the PCI Express Base Specification introduced
241 root ports. For conventional PCI devices native PMEs are out-of-band, so they
243 may be routed directly to the system's core logic), but for PCI Express devices
247 interrupt whenever it receives a PME message from one of the devices below it.
268 The PCI Subsystem participates in the power management of PCI devices in a
298 involving some standard configuration registers of PCI devices that device
345 At this point the device is ready for power management. For driverless devices,
352 devices. For this purpose it uses the general runtime power management
361 entire mechanics necessary for handling runtime wakeup signals from PCI devices
367 of pm_schedule_suspend() or pm_runtime_suspend() which for PCI devices call
390 pci_pm_runtime_resume() for PCI devices. Again, this only works if the device's
406 The pci_pm_runtime_idle() function, called for PCI devices by pm_runtime_idle()
420 Documentation/power/devices.txt. Each of them requires devices to be handled
457 Note that the suspend phase is carried out asynchronously for PCI devices, so
459 devices that don't depend on each other in a known way (i.e. none of the paths
485 generally not expected to prepare devices for signaling wakeup or to put them
513 legacy PCI power management callbacks (this way all PCI devices are in the
517 by drivers whose devices are still suspended). If legacy PCI power management
533 The resume phase is carried out asynchronously for PCI devices, like the
534 suspend phase described above, which means that if two PCI devices don't depend
545 image is created atomically and all devices are quiesced, or frozen, before that
548 The freezing of devices is carried out after enough memory has been freed (at
566 asynchronously for different PCI devices that don't depend on each other in a
577 devices are frozen and they cannot handle I/O, while their ability to handle
598 asynchronously for different PCI devices that don't depend on each other in a
603 After saving the image, devices need to be powered down before the system can
626 As described in Documentation/power/devices.txt, the hibernation image is loaded
631 kernel. For this purpose all devices are frozen just like before creating
636 phases described above. However, the devices affected by these phases are only
637 those having drivers in the boot kernel; other devices will still be in whatever
642 thaw_noirq, thaw, and complete phases (that will only affect the devices having
648 it must restore the devices' pre-hibernation functionality, which is done much
676 controlling the runtime power management of their devices.
680 dev_pm_ops structure described in Documentation/power/devices.txt, and the
721 callbacks have been executed for all devices in the system.
747 suspend() callbacks have been executed for all devices in the system and
758 during hibernation, after prepare() callbacks have been executed for all devices
761 prepare() callbacks have been executed for all devices.
776 devices in preparation for the creation of a system image, and during restore,
778 freeze() callbacks have been executed for all devices. It is always executed
792 storage. prepare() callbacks are executed for all devices before poweroff() is
807 poweroff() callbacks have been executed for all devices in the system.
823 Since the PCI subsystem unconditionally puts all devices into the full power
832 resume_noirq() callbacks have been executed for all devices in the system and
856 callbacks have been executed for all devices in the system and after device
880 restore_noirq() callbacks have been executed for all devices in the system and
894 devices,
896 have been executed for all devices,
898 state, after restore() callbacks have been executed for all devices.
901 devices that have drivers in the boot kernel).
968 their devices.
973 from an Ethernet adapter or there are no devices attached to a USB controller).
982 The runtime PM of PCI devices is enabled by default by the PCI core. PCI
997 just needs to call a function that decrements the devices usage counter
1023 devices, or to check if they are idle (in which cases it is reasonable to
1030 requests for their devices. For this purpose they should use the runtime PM
1038 For more information on the runtime PM of devices refer to
1049 Documentation/power/devices.txt