Documentation/power/pci.rst

286 	.resume = pci_pm_resume,
404 callback need not worry about the PCI-specific aspects of the device resume.
504 2.4.2. System Resume
511 	resume_noirq, resume, complete.
521 state, restores its standard configuration registers and applies early resume
526 when their interrupt handlers are invoked for the first time during resume,
530 early resume callback is executed and its result is returned.  Otherwise, the
536 only is necessary in the error path during a failing suspend).  Next, resume
539 Section 3), the driver's legacy resume callback is executed and its result is
541 its driver's pm->resume() callback is executed, if defined (the callback's
544 The resume phase is carried out asynchronously for PCI devices, like the
609 driver's pm->thaw() callback instead of pm->resume().  It is executed
613 The complete phase is the same as for system resume.
667 The first two of these are analogous to the resume_noirq and resume phases
679 resume.
695 the "legacy" one, in which the .suspend() and .resume() callbacks from struct
840 The resume_noirq() callback is only executed during system resume, after the
846 state in the resume_noirq phase of system resume and restores their standard
849 conditions if carried out by resume().
851 3.1.9. resume()
854 The resume() callback is only executed during system resume, after
860 able to process I/O in a usual way after resume() has returned.
898 suspend-resume cycle.
910 This callback is analogous to resume(), just like restore_noirq() is analogous
912 restore() is analogous to the difference between resume_noirq() and resume().
915 resume() and restore().
922   - during system resume, after resume() callbacks have been executed for all
968 resume of the device has happened as a result of a spurious event.
984 members and one resume routine pointed to by the .resume(), .thaw(), and
990 .resume() (and .thaw(), and .restore()) and the .runtime_suspend() pointer to
995 .suspend(), .freeze(), and .poweroff() members and one resume routine is to
996 be pointed to by the .resume(), .thaw(), and .restore() members.
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
1094 out a runtime resume of the device and bumps up the device's usage counter
1100 The runtime PM framework works by processing requests to suspend or resume
1105 queued by the PM core (for example, after processing a request to resume a