Lines Matching refs:PM
41 approach, that is referred to as the native PCI power management (native PCI PM)
47 Devices supporting the native PCI PM usually can generate wakeup signals called
62 native PCI PM mechanism, because the method provided by the platform depends on
70 The PCI Bus Power Management Interface Specification (PCI PM Spec) was
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
98 regardless of whether or not it implements the PCI PM Spec. In addition to
99 that, if the PCI PM Spec is implemented by the device, it must support D3hot
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
161 labeled as D0, D1, D2, and D3 that roughly correspond to the native PCI PM
270 the device power management core (PM core) and PCI device drivers.
295 These callbacks are executed by the PM core in various situations related to
307 int pm_cap; /* PM capability offset in the
330 The first of these functions checks if the device supports native PCI PM
353 (runtime PM) framework described in Documentation/power/runtime_pm.txt.
360 that are executed by the core runtime PM routines. It also implements the
381 PM capabilities, if supported.
410 Sometimes pci_pm_runtime_idle() is called automatically by the PM core (for
421 in a specific way and the PM core executes subsystem-level power management
479 state. Just like in the runtime PM case described above, the mechanism of
688 containing pointers to power management (PM) callbacks that will be executed by
689 the PCI subsystem's PM routines in various circumstances. A pointer to the
691 its struct pci_driver object. Once that has happened, the "legacy" PM callbacks
694 The PM callbacks in struct dev_pm_ops are not mandatory and if they are not
748 after device interrupts have been disabled by the PM core.
779 after device interrupts have been disabled by the PM core.
819 PM core has enabled the non-boot CPUs. The driver's interrupt handler will not
833 device interrupts have been enabled by the PM core.
842 system image has been created and the non-boot CPUs have been enabled by the PM
857 interrupts have been enabled by the PM core.
867 PM core.
881 after the PM core has enabled device drivers' interrupt handlers to be invoked.
909 (runtime PM). It is executed by the PM core's runtime PM framework when the
919 The runtime_resume() callback is specific to device runtime PM. It is executed
920 by the PM core's runtime PM framework when the device is about to be resumed
931 The runtime_idle() callback is specific to device runtime PM. It is executed
932 by the PM core's runtime PM framework whenever it may be desirable to suspend
933 the device according to the PM core's information. In particular, it is
967 are responsible for controlling the runtime power management (runtime PM) of
970 The PCI device runtime PM is optional, but it is recommended that PCI device
975 To support the PCI runtime PM the driver first needs to implement the
982 The runtime PM of PCI devices is disabled by default. It is also blocked by
984 driver implements the runtime PM callbacks and intends to use the runtime PM
985 framework provided by the PM core and the PCI subsystem, it should enable this
988 the runtime PM of the device. Instead, it should allow user space or some
991 runtime PM of the device correctly as soon as pm_runtime_allow() is called
994 fact the driver has to be prepared to handle the runtime PM of the device as
997 The runtime PM framework works by processing requests to suspend or resume
1002 queued by the PM core (for example, after processing a request to resume a
1003 device the PM core automatically queues a request to check if the device is
1005 requests for their devices. For this purpose they should use the runtime PM
1006 helper functions provided by the PM core, discussed in
1011 drivers that use helper functions provided by the PM core for this purpose.
1013 For more information on the runtime PM of devices refer to