Lines Matching refs:suspend

278 	.suspend = pci_pm_suspend,
412 cases it is expected to suspend the device if that makes sense.  Usually,
432 	prepare, suspend, suspend_noirq.
446 legacy PCI suspend routines (see Section 3), in which case the driver's legacy
447 suspend callback is executed, if present, and its result is returned.  Next, if
452 bridges are ignored by this routine).  Next, the device driver's pm->suspend()
454 Finally, pci_fixup_device() is called to apply hardware suspend quirks related
457 Note that the suspend phase is carried out asynchronously for PCI devices, so
466 late suspend routine is called and its result is returned (the standard
486 into low-power states.  However, if one of the driver's suspend callbacks
487 (pm->suspend() or pm->suspend_noirq()) saves the device's standard configuration
525 only is necessary in the error path during a failing suspend).  Next, resume
534 suspend phase described above, which means that if two PCI devices don't depend
543 System hibernation is more complicated than system suspend, because it requires
560 This means that the prepare phase is exactly the same as for system suspend.
564 the device driver's pm->freeze() callback, if defined, instead of pm->suspend(),
565 and it doesn't apply the suspend-related hardware quirks.  It is executed
609 where the prepare phase is exactly the same as for system suspend.  The other
610 two phases are analogous to the suspend and suspend_noirq phases, respectively.
681 "legacy" one, in which the .suspend(), .suspend_late(), .resume_early(), and
702 The prepare() callback is executed during system suspend, during hibernation
714 (if additional memory is required to suspend the device, it has to be
715 preallocated earlier, for example in a suspend/hibernate notifier as described
718 3.1.2. suspend()
720 The suspend() callback is only executed during system suspend, after prepare()
725 not recommended) that a PCI driver's suspend() callback save the standard
739 While the suspend() callback is being executed, the driver's interrupt handler
740 can be invoked to handle an interrupt from the device, so all suspend-related
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
750 The difference between suspend_noirq() and suspend() is that the driver's
753 arise if they were performed in suspend().
763 The role of this callback is analogous to the role of the suspend() callback
786 difference between suspend_noirq() and suspend().
795 The role of this callback is analogous to the role of the suspend() and freeze()
814 difference between suspend_noirq() and suspend().
835 This callback is responsible for restoring the pre-suspend configuration of the
872 suspend-resume cycle.
932 by the PM core's runtime PM framework whenever it may be desirable to suspend
949 suspend routine pointed to by the .suspend(), .freeze(), and .poweroff()
957 the same value as .suspend() (and .freeze() and .poweroff()).
960 dev_pm_ops to indicate that one suspend routine is to be pointed to by the
961 .suspend(), .freeze(), and .poweroff() members and one resume routine is to
1022 The runtime PM framework works by processing requests to suspend or resume