Documentation/power/pci.rst

149 methods" that may be executed by the kernel to perform specific tasks, such as
180 3.0) control method defined for it has to be executed before _PSx.  Power
302 These callbacks are executed by the PM core in various situations related to
369 that are executed by the core runtime PM routines.  It also implements the
401 the driver's callback is executed, pci_pm_runtime_resume() brings the device
431 management callbacks for this purpose.  They are executed in phases such that
457 suspend callback is executed, if present, and its result is returned.  Next, if
463 callback is executed, if defined, and its result is returned if it fails.
468 the pci_pm_suspend() callback may be executed in parallel for any pair of PCI
472 The pci_pm_suspend_noirq() routine is executed after suspend_device_irqs() has
481 executed, if present, and its result is returned if it fails.  Next, if the
483 device driver's callbacks executed before might do that), pci_pm_suspend_noirq()
513 The following PCI bus type's callbacks, respectively, are executed in these
530 early resume callback is executed and its result is returned.  Otherwise, the
531 device driver's pm->resume_noirq() callback is executed, if defined, and its
539 Section 3), the driver's legacy resume callback is executed and its result is
541 its driver's pm->resume() callback is executed, if defined (the callback's
546 on each other in a known way, the pci_pm_resume() routine may be executed for
577 and it doesn't apply the suspend-related hardware quirks.  It is executed
609 driver's pm->thaw() callback instead of pm->resume().  It is executed
689 executed by the PCI subsystem's power management routines described above and by
702 containing pointers to power management (PM) callbacks that will be executed by
717 The prepare() callback is executed during system suspend, during hibernation
736 The suspend() callback is only executed during system suspend, after prepare()
737 callbacks have been executed for all devices in the system.
755 While the suspend() callback is being executed, the driver's interrupt handler
763 The suspend_noirq() callback is only executed during system suspend, after
764 suspend() callbacks have been executed for all devices in the system and
775 The freeze() callback is hibernation-specific and is executed in two situations,
776 during hibernation, after prepare() callbacks have been executed for all devices
779 prepare() callbacks have been executed for all devices.
793 The freeze_noirq() callback is hibernation-specific.  It is executed during
794 hibernation, after prepare() and freeze() callbacks have been executed for all
797 freeze() callbacks have been executed for all devices.  It is always executed
810 The poweroff() callback is hibernation-specific.  It is executed when the system
812 storage.  prepare() callbacks are executed for all devices before poweroff() is
827 The poweroff_noirq() callback is hibernation-specific.  It is executed after
828 poweroff() callbacks have been executed for all devices in the system.
840 The resume_noirq() callback is only executed during system resume, after the
854 The resume() callback is only executed during system resume, after
855 resume_noirq() callbacks have been executed for all devices in the system and
865 The thaw_noirq() callback is hibernation-specific.  It is executed after a
867 core, in the thaw_noirq phase of hibernation.  It also may be executed if the
868 loading of a hibernation image fails during system restore (it is then executed
873 difference between these two callbacks is that thaw_noirq() is executed after
880 The thaw() callback is hibernation-specific.  It is executed after thaw_noirq()
881 callbacks have been executed for all devices in the system and after device
890 The restore_noirq() callback is hibernation-specific.  It is executed in the
906 The restore() callback is hibernation-specific.  It is executed after
907 restore_noirq() callbacks have been executed for all devices in the system and
920 The complete() callback is executed in the following situations:
922   - during system resume, after resume() callbacks have been executed for all
925     have been executed for all devices,
927     state, after restore() callbacks have been executed for all devices.
929 It also may be executed if the loading of a hibernation image into memory fails
930 (in that case it is run after thaw() callbacks have been executed for all
940 (runtime PM).  It is executed by the PM core's runtime PM framework when the
951 The runtime_resume() callback is specific to device runtime PM.  It is executed
964 The runtime_idle() callback is specific to device runtime PM.  It is executed
967 automatically executed right after runtime_resume() has returned in case the
972 cause the driver's runtime_suspend() callback to be executed.
1078 may be executed right after the usage counter has been decremented, because