Lines Matching refs:executed
144 methods" that may be executed by the kernel to perform specific tasks, such as
175 3.0) control method defined for it has to be executed before _PSx. Power
295 These callbacks are executed by the PM core in various situations related to
360 that are executed by the core runtime PM routines. It also implements the
392 the driver's callback is executed, pci_pm_runtime_resume() brings the device
422 callbacks for this purpose. They are executed in phases such that each phase
447 suspend callback is executed, if present, and its result is returned. Next, if
453 callback is executed, if defined, and its result is returned if it fails.
458 the pci_pm_suspend() callback may be executed in parallel for any pair of PCI
462 The pci_pm_suspend_noirq() routine is executed after suspend_device_irqs() has
471 executed, if present, and its result is returned if it fails. Next, if the
473 device driver's callbacks executed before might do that), pci_pm_suspend_noirq()
502 The following PCI bus type's callbacks, respectively, are executed in these
519 early resume callback is executed and its result is returned. Otherwise, the
520 device driver's pm->resume_noirq() callback is executed, if defined, and its
528 Section 3), the driver's legacy resume callback is executed and its result is
530 its driver's pm->resume() callback is executed, if defined (the callback's
535 on each other in a known way, the pci_pm_resume() routine may be executed for
565 and it doesn't apply the suspend-related hardware quirks. It is executed
597 driver's pm->thaw() callback instead of pm->resume(). It is executed
675 executed by the PCI subsystem's power management routines described above and by
688 containing pointers to power management (PM) callbacks that will be executed by
702 The prepare() callback is executed during system suspend, during hibernation
720 The suspend() callback is only executed during system suspend, after prepare()
721 callbacks have been executed for all devices in the system.
739 While the suspend() callback is being executed, the driver's interrupt handler
746 The suspend_noirq() callback is only executed during system suspend, after
747 suspend() callbacks have been executed for all devices in the system and
757 The freeze() callback is hibernation-specific and is executed in two situations,
758 during hibernation, after prepare() callbacks have been executed for all devices
761 prepare() callbacks have been executed for all devices.
774 The freeze_noirq() callback is hibernation-specific. It is executed during
775 hibernation, after prepare() and freeze() callbacks have been executed for all
778 freeze() callbacks have been executed for all devices. It is always executed
790 The poweroff() callback is hibernation-specific. It is executed when the system
792 storage. prepare() callbacks are executed for all devices before poweroff() is
806 The poweroff_noirq() callback is hibernation-specific. It is executed after
807 poweroff() callbacks have been executed for all devices in the system.
818 The resume_noirq() callback is only executed during system resume, after the
831 The resume() callback is only executed during system resume, after
832 resume_noirq() callbacks have been executed for all devices in the system and
841 The thaw_noirq() callback is hibernation-specific. It is executed after a
843 core, in the thaw_noirq phase of hibernation. It also may be executed if the
844 loading of a hibernation image fails during system restore (it is then executed
849 difference between these two callbacks is that thaw_noirq() is executed after
855 The thaw() callback is hibernation-specific. It is executed after thaw_noirq()
856 callbacks have been executed for all devices in the system and after device
864 The restore_noirq() callback is hibernation-specific. It is executed in the
879 The restore() callback is hibernation-specific. It is executed after
880 restore_noirq() callbacks have been executed for all devices in the system and
892 The complete() callback is executed in the following situations:
893 - during system resume, after resume() callbacks have been executed for all
896 have been executed for all devices,
898 state, after restore() callbacks have been executed for all devices.
899 It also may be executed if the loading of a hibernation image into memory fails
900 (in that case it is run after thaw() callbacks have been executed for all
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
931 The runtime_idle() callback is specific to device runtime PM. It is executed
934 automatically executed right after runtime_resume() has returned in case the
939 cause the driver's runtime_suspend() callback to be executed.