Lines Matching refs:callbacks

273 pointers to several device power management callbacks:
295 These callbacks are executed by the PM core in various situations related to
296 device power management and they, in turn, execute power management callbacks
302 that these callbacks operate on:
354 Namely, it provides subsystem-level callbacks:
422 callbacks for this purpose.  They are executed in phases such that each phase
434 The following PCI bus type's callbacks, respectively, are used in these phases:
449 pointers to the driver's callbacks), pci_pm_default_suspend() is called, which
473 device driver's callbacks executed before might do that), pci_pm_suspend_noirq()
484 PCI device drivers (that don't implement legacy power management callbacks) are
486 into low-power states.  However, if one of the driver's suspend callbacks
502 The following PCI bus type's callbacks, respectively, are executed in these
513 legacy PCI power management callbacks (this way all PCI devices are in the
518 callbacks (see Section 3) are implemented by the device's driver, the legacy
527 device's driver implements legacy PCI power management callbacks (see
554 that correspond to the PCI bus type's callbacks:
574 of the driver's callbacks.
583 using the following PCI bus type's callbacks:
611 The PCI subsystem-level callbacks they correspond to
656 callbacks:
661 These callbacks work in analogy with pci_pm_resume_noirq() and pci_pm_resume(),
663 pm->restore() callbacks, if available.
674 PCI device drivers participate in power management by providing callbacks to be
679 callbacks for a PCI device driver, the recommended one, based on using a
682 .resume() callbacks from struct pci_driver are used.  The legacy approach,
683 however, doesn't allow one to define runtime power management callbacks and is
688 containing pointers to power management (PM) callbacks that will be executed by
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
710 one of the resume_noirq(), thaw_noirq(), or restore_noirq() callbacks is run.
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.
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
792 storage.  prepare() callbacks are executed for all devices before poweroff() is
796 callbacks described above, although it does not need to save the contents of
807 poweroff() callbacks have been executed for all devices in the system.
810 freeze_noirq() callbacks described above, but it does not need to save the
832 resume_noirq() callbacks have been executed for all devices in the system and
849 difference between these two callbacks is that thaw_noirq() is executed after
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
893   - during system resume, after resume() callbacks have been executed for all
895   - during hibernation, before saving the system image, after thaw() callbacks
898     state, after restore() callbacks have been executed for all devices.
900 (in that case it is run after thaw() callbacks have been executed for all
943 Although in principle each of the callbacks described in the previous
966 In addition to providing device power management callbacks PCI device drivers
976 runtime_suspend() and runtime_resume() callbacks.  It also may need to implement
989 If a PCI driver implements the runtime PM callbacks and intends to use the