Lines Matching full:resume

81  *	transition and during the subsequent resume if all of its descendants
84  *	functioning of the device after the system resume.
87  *	devices may be assumed to be functional or to respond to runtime resume
97  *	all kinds of resume transitions, following one of the resume callbacks:
98  *	@resume(), @thaw(), @restore().  Also called if the state transition
104  *	the appropriate resume callbacks for all devices.  If the corresponding
107  *	executing any suspend and resume callbacks for it), @complete() will be
108  *	the only callback executed for the device during resume.  In that case,
110  *	proper functioning of the device after the system resume.  To this end,
112  *	learn whether (unset) or not (set) the previous suspend and resume
127  * @resume: Executed after waking the system up from a sleep state in which the
132  *	for a runtime resume to occur).  The state of the device at the time its
133  *	driver's @resume() callback is run depends on the platform and subsystem
135  *	availability of resources like clocks during @resume().
136  *	Subsystem-level @resume() is executed for all devices after invoking
139  * @resume_early: Prepare to execute @resume().  For a number of devices
141  *	resume callback.
148  *	during the subsequent resume from hibernation.
178  *	memory from a hibernation image, analogous to @resume().
196  * @resume_noirq: Prepare for the execution of @resume() by carrying out any
259  * However, the error codes returned by @resume(), @thaw(), @restore(),
261  * core to abort the resume transition during which they are returned.  The
264  * codes from their resume methods in case of an unrecoverable failure (i.e.
265  * when the device being handled refuses to resume and becomes unusable) to
267  * attempting to handle devices that failed to resume and their children.
290 	int (*resume)(struct device *dev);  member
314 	.resume = pm_sleep_ptr(resume_fn), \
397  * Use this if you want to use the same suspend and resume callbacks for suspend
432  * NOTE: In general, system suspend callbacks, .suspend() and .resume(), should
438  * suspend and "early" resume callback pointers, .suspend_late() and
452  * Use this if you want to have the suspend and resume callbacks be called
486  * RESUME	System is resuming, call ->resume() and ->complete() for all
504  * USER_RESUME		Manual selective resume was issued by userspace.
511  * AUTO_RESUME		Automatic (device needed) runtime resume was
631  * Driver flags to control system suspend/resume behavior.
724  * hibernation, system resume and during runtime PM transitions instead of
738  * suspend framework, based on the ->suspend() and ->resume() callbacks common
746  * One transition is triggered by resume(), after a suspend() call; the
754  *		availability of resources like clocks during resume().
781  * reinitializes its device during resume() -- whether or not it was reset
782  * during the suspend/resume cycle -- and can't issue wakeup events.