Lines Matching full:subsystem

58  *	subsystem and generally the rest of the kernel is supposed to prevent
76  *	The PM core executes subsystem-level @prepare() for all devices before
94  *	The PM core executes subsystem-level @complete() after it has executed
108  *	depends on the device's subsystem (PM domain, device type, class or bus
109  *	type), but generally the device must be quiescent after subsystem-level
111  *	Subsystem-level @suspend() is executed for all devices after invoking
112  *	subsystem-level @prepare() for all of them.
120  *	depends on the device's subsystem, but generally the driver is expected
124  *	driver's @resume() callback is run depends on the platform and subsystem
127  *	Subsystem-level @resume() is executed for all devices after invoking
128  *	subsystem-level @resume_noirq() for all of them.
140  *	Subsystem-level @freeze() is executed for all devices after invoking
141  *	subsystem-level @prepare() for all of them.
152  *	Subsystem-level @thaw() is executed for all devices after invoking
153  *	subsystem-level @thaw_noirq() for all of them.  It also may be executed
162  *	Subsystem-level @poweroff() is executed for all devices after invoking
163  *	subsystem-level @prepare() for all of them.
178  *	(appropriate for the target system sleep state) after subsystem-level
182  *	and device's subsystem, @suspend() or @suspend_late() may be allowed to
242  * domains, device types, classes and bus types.  They are the subsystem-level
245  * have to collaborate with the subsystem-level callbacks to achieve the goals
247  * subsystem the device belongs to.
268  * (PM domains, device types, classes and bus types) and the subsystem-level
271  * the platform and subsystem the device belongs to.
428  *			initiated by the subsystem.
622 	struct pm_subsys_data	*subsys_data;  /* Owned by the subsystem. */
642  * subsystem-level and driver-level callbacks.