Lines Matching full:subsystem

59  *	subsystem and generally the rest of the kernel is supposed to prevent
77  *	The PM core executes subsystem-level @prepare() for all devices before
95  *	The PM core executes subsystem-level @complete() after it has executed
109  *	depends on the device's subsystem (PM domain, device type, class or bus
110  *	type), but generally the device must be quiescent after subsystem-level
112  *	Subsystem-level @suspend() is executed for all devices after invoking
113  *	subsystem-level @prepare() for all of them.
121  *	depends on the device's subsystem, but generally the driver is expected
125  *	driver's @resume() callback is run depends on the platform and subsystem
128  *	Subsystem-level @resume() is executed for all devices after invoking
129  *	subsystem-level @resume_noirq() for all of them.
141  *	Subsystem-level @freeze() is executed for all devices after invoking
142  *	subsystem-level @prepare() for all of them.
153  *	Subsystem-level @thaw() is executed for all devices after invoking
154  *	subsystem-level @thaw_noirq() for all of them.  It also may be executed
163  *	Subsystem-level @poweroff() is executed for all devices after invoking
164  *	subsystem-level @prepare() for all of them.
179  *	(appropriate for the target system sleep state) after subsystem-level
183  *	and device's subsystem, @suspend() or @suspend_late() may be allowed to
243  * domains, device types, classes and bus types.  They are the subsystem-level
246  * have to collaborate with the subsystem-level callbacks to achieve the goals
248  * subsystem the device belongs to.
269  * (PM domains, device types, classes and bus types) and the subsystem-level
272  * the platform and subsystem the device belongs to.
429  *			initiated by the subsystem.
620 	struct pm_subsys_data	*subsys_data;  /* Owned by the subsystem. */
640  * subsystem-level and driver-level callbacks.