Lines Matching refs:resume

16   hibernation and resume from system sleep states).  pm_wq is declared in
92     RAM until the appropriate resume callback is executed for it.  The runtime
115 The subsystem-level resume callback, if present, is _entirely_ _responsible_ for
116 handling the resume of the device as appropriate, which may, but need not
119 callback in a device driver as long as the subsystem-level resume callback knows
122   * Once the subsystem-level resume callback (or the driver resume callback, if
128   * If the resume callback returns an error code, the PM core regards this as a
254       suspend to complete; means "start a resume as soon as you've suspended"
330     - execute the subsystem-level resume callback for the device; returns 0 on
333       resume the device again in future, but 'power.runtime_error' should be
358     - submit a request to execute the subsystem-level resume callback for the
407       canceled; returns 1 if there was a resume request pending and it was
408       necessary to execute the subsystem-level resume callback for the device
412     - check if there's a resume request pending for the device and resume it
415       complete; returns 1 if there was a resume request pending and it was
416       necessary to execute the subsystem-level resume callback for the device to
605 suspend routine).  It may be necessary to resume the device and suspend it again
609 During system resume, the simplest approach is to bring all devices back to full
618     to resume themselves.
621     physical state.  This can happen during resume from hibernation.
626     likely it would need a runtime resume in the near future anyway.
629 brought back to full power during resume, then its runtime PM status will have
638 ->suspend() callback and decrements it after calling the ->resume() callback.
641 following the return of the ->resume() callback, the ->runtime_idle() callback
650 gives control away and the states of all devices during resume are precisely
662 system suspend and resume callbacks for all of those devices, except for the
669 the runtime PM and system suspend/resume (and hibernation) callbacks by carrying
680   * During system resume pm_runtime_enable() and pm_runtime_put() are called for
710     - invoke the ->resume() callback provided by the driver of this device and,
755 ->runtime_resume(), ->suspend(), ->suspend_noirq(), ->resume(),
761 poweroff and runtime suspend callback, and similarly for system resume, thaw,
762 restore, and runtime resume, can achieve this with the help of the
892 		/* ... resume the device ... */