Lines Matching full:resume

21   hibernation and resume from system sleep states).  pm_wq is declared in
98     RAM until the appropriate resume callback is executed for it.  The runtime
121 The subsystem-level resume callback, if present, is **entirely responsible** for
122 handling the resume of the device as appropriate, which may, but need not
125 callback in a device driver as long as the subsystem-level resume callback knows
128   * Once the subsystem-level resume callback (or the driver resume callback, if
134   * If the resume callback returns an error code, the PM core regards this as a
261       suspend to complete; means "start a resume as soon as you've suspended"
335     - execute the subsystem-level resume callback for the device; returns 0 on
338       resume the device again in future, but 'power.runtime_error' should be
363     - submit a request to execute the subsystem-level resume callback for the
424       canceled; returns 1 if there was a resume request pending and it was
425       necessary to execute the subsystem-level resume callback for the device
429     - check if there's a resume request pending for the device and resume it
432       complete; returns 1 if there was a resume request pending and it was
433       necessary to execute the subsystem-level resume callback for the device to
638 suspend routine).  It may be necessary to resume the device and suspend it again
642 During system resume, the simplest approach is to bring all devices back to full
651     to resume themselves.
654     physical state.  This can happen during resume from hibernation.
659     likely it would need a runtime resume in the near future anyway.
662 brought back to full power during resume, then its runtime PM status will have
671 ->suspend() callback and decrements it after calling the ->resume() callback.
674 following the return of the ->resume() callback, the ->runtime_idle() callback
683 gives control away and the states of all devices during resume are precisely
695 system suspend and resume callbacks for all of those devices, except for the
702 the runtime PM and system suspend/resume (and hibernation) callbacks by carrying
713   * During system resume pm_runtime_enable() and pm_runtime_put() are called for
743     - invoke the ->resume() callback provided by the driver of this device and,
788 ->runtime_resume(), ->suspend(), ->suspend_noirq(), ->resume(),
794 poweroff and runtime suspend callback, and similarly for system resume, thaw,
795 restore, and runtime resume, can achieve this with the help of the
926 		/* ... resume the device ... */