Lines Matching refs:resume

279 	.resume = pci_pm_resume,
395 callback need not worry about the PCI-specific aspects of the device resume.
500 	resume_noirq, resume, complete.
510 state, restores its standard configuration registers and applies early resume
515 when their interrupt handlers are invoked for the first time during resume,
519 early resume callback is executed and its result is returned.  Otherwise, the
525 only is necessary in the error path during a failing suspend).  Next, resume
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
533 The resume phase is carried out asynchronously for PCI devices, like the
597 driver's pm->thaw() callback instead of pm->resume().  It is executed
601 The complete phase it the same as for system resume.
654 The first two of these are analogous to the resume_noirq and resume phases
666 resume.
682 .resume() callbacks from struct pci_driver are used.  The legacy approach,
818 The resume_noirq() callback is only executed during system resume, after the
824 state in the resume_noirq phase of system resume and restores their standard
827 conditions if carried out by resume().
829 3.1.9. resume()
831 The resume() callback is only executed during system resume, after
837 able to process I/O in a usual way after resume() has returned.
872 suspend-resume cycle.
883 This callback is analogous to resume(), just like restore_noirq() is analogous
885 restore() is analogous to the difference between resume_noirq() and resume().
888 resume() and restore().
893   - during system resume, after resume() callbacks have been executed for all
935 resume of the device has happened as a result of a spurious event.
950 members and one resume routine pointed to by the .resume(), .thaw(), and
956 .resume() (and .thaw(), and .restore()) and the .runtime_suspend() pointer to
961 .suspend(), .freeze(), and .poweroff() members and one resume routine is to
962 be pointed to by the .resume(), .thaw(), and .restore() members.
1016 out a runtime resume of the device and bumps up the device's usage counter
1022 The runtime PM framework works by processing requests to suspend or resume
1027 queued by the PM core (for example, after processing a request to resume a