Lines Matching refs:callbacks
280 pointers to several device power management callbacks::
302 These callbacks are executed by the PM core in various situations related to
303 device power management and they, in turn, execute power management callbacks
309 that these callbacks operate on::
363 Namely, it provides subsystem-level callbacks::
431 management callbacks for this purpose. They are executed in phases such that
444 The following PCI bus type's callbacks, respectively, are used in these phases::
459 pointers to the driver's callbacks), pci_pm_default_suspend() is called, which
483 device driver's callbacks executed before might do that), pci_pm_suspend_noirq()
494 PCI device drivers (that don't implement legacy power management callbacks) are
496 into low-power states. However, if one of the driver's suspend callbacks
513 The following PCI bus type's callbacks, respectively, are executed in these
524 legacy PCI power management callbacks (this way all PCI devices are in the
529 callbacks (see Section 3) are implemented by the device's driver, the legacy
538 device's driver implements legacy PCI power management callbacks (see
566 that correspond to the PCI bus type's callbacks::
586 of the driver's callbacks.
595 using the following PCI bus type's callbacks::
623 The PCI subsystem-level callbacks they correspond to::
669 callbacks::
674 These callbacks work in analogy with pci_pm_resume_noirq() and pci_pm_resume(),
676 pm->restore() callbacks, if available.
688 PCI device drivers participate in power management by providing callbacks to be
693 callbacks for a PCI device driver, the recommended one, based on using a
695 the "legacy" one, in which the .suspend() and .resume() callbacks from struct
697 runtime power management callbacks and is not really suitable for any new
702 containing pointers to power management (PM) callbacks that will be executed by
705 its struct pci_driver object. Once that has happened, the "legacy" PM callbacks
708 The PM callbacks in struct dev_pm_ops are not mandatory and if they are not
725 one of the resume_noirq(), thaw_noirq(), or restore_noirq() callbacks is run.
737 callbacks have been executed for all devices in the system.
764 suspend() callbacks have been executed for all devices in the system and
776 during hibernation, after prepare() callbacks have been executed for all devices
779 prepare() callbacks have been executed for all devices.
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
812 storage. prepare() callbacks are executed for all devices before poweroff() is
816 callbacks described above, although it does not need to save the contents of
828 poweroff() callbacks have been executed for all devices in the system.
831 freeze_noirq() callbacks described above, but it does not need to save the
855 resume_noirq() callbacks have been executed for all devices in the system and
873 difference between these two callbacks is that thaw_noirq() is executed after
881 callbacks have been executed for all devices in the system and after device
907 restore_noirq() callbacks have been executed for all devices in the system and
922 - during system resume, after resume() callbacks have been executed for all
924 - during hibernation, before saving the system image, after thaw() callbacks
927 state, after restore() callbacks have been executed for all devices.
930 (in that case it is run after thaw() callbacks have been executed for all
977 Although in principle each of the callbacks described in the previous
1008 direct-complete mechanism allowing device suspend/resume callbacks to be skipped
1031 "noirq" and "early" resume callbacks to be skipped if the device can be left
1036 resume callbacks should be skipped, the dev_pm_skip_resume() helper function
1039 executing the driver callbacks.
1044 In addition to providing device power management callbacks PCI device drivers
1054 runtime_suspend() and runtime_resume() callbacks. It also may need to implement
1067 If a PCI driver implements the runtime PM callbacks and intends to use the