Lines Matching full:resume

72  *	transition and during the subsequent resume if all of its descendants
75  *	functioning of the device after the system resume.
78  *	devices may be assumed to be functional or to respond to runtime resume
88  *	all kinds of resume transitions, following one of the resume callbacks:
89  *	@resume(), @thaw(), @restore().  Also called if the state transition
95  *	the appropriate resume callbacks for all devices.  If the corresponding
98  *	executing any suspend and resume callbacks for it), @complete() will be
99  *	the only callback executed for the device during resume.  In that case,
101  *	proper functioning of the device after the system resume.  To this end,
103  *	learn whether (unset) or not (set) the previous suspend and resume
118  * @resume: Executed after waking the system up from a sleep state in which the
123  *	for a runtime resume to occur).  The state of the device at the time its
124  *	driver's @resume() callback is run depends on the platform and subsystem
126  *	availability of resources like clocks during @resume().
127  *	Subsystem-level @resume() is executed for all devices after invoking
130  * @resume_early: Prepare to execute @resume().  For a number of devices
132  *	resume callback.
139  *	during the subsequent resume from hibernation.
169  *	memory from a hibernation image, analogous to @resume().
187  * @resume_noirq: Prepare for the execution of @resume() by carrying out any
250  * However, the error codes returned by @resume(), @thaw(), @restore(),
252  * core to abort the resume transition during which they are returned.  The
255  * codes from their resume methods in case of an unrecoverable failure (i.e.
256  * when the device being handled refuses to resume and becomes unusable) to
258  * attempting to handle devices that failed to resume and their children.
281 	int (*resume)(struct device *dev);  member
306 	.resume = resume_fn, \
349  * Use this if you want to use the same suspend and resume callbacks for suspend
360  * NOTE: In general, system suspend callbacks, .suspend() and .resume(), should
366  * suspend and "early" resume callback pointers, .suspend_late() and
405  * RESUME	System is resuming, call ->resume() and ->complete() for all
423  * USER_RESUME		Manual selective resume was issued by userspace.
430  * AUTO_RESUME		Automatic (device needed) runtime resume was
549  * Driver flags to control system suspend/resume behavior.
641  * hibernation, system resume and during runtime PM transitions instead of
655  * suspend framework, based on the ->suspend() and ->resume() callbacks common
663  * One transition is triggered by resume(), after a suspend() call; the
671  *		availability of resources like clocks during resume().
698  * reinitializes its device during resume() -- whether or not it was reset
699  * during the suspend/resume cycle -- and can't issue wakeup events.