Lines Matching refs:all

87 unless all the devices plugged into that hub are already suspended.)
124 all dynamic suspend events are internal; external agents are not
240 The USB specification states that all USB devices must support power
242 support it very well.  You can suspend them all right, but when you
249 power/control attribute is initialized to "on") for all devices other
254 by default for almost all USB devices.  A number of people experienced
267 it can enable autosuspend all by itself.  For example, the video
276 causing the keyboard to do a remote wakeup all right, will nonetheless
303 	the driver will return 0, in which case it must cancel all
313 	since the device has probably lost most or all of its state
336 force the drivers for those interface to stop all activity) without
337 suspending the other interfaces.  The USB core doesn't allow this; all
338 interfaces are suspended when the device itself is suspended and all
340 to suspend or resume some but not all of a device's interfaces.  The
347 To support autosuspend and autoresume, a driver should implement all
481 If a driver wants to block all suspend/resume calls during some
484 critical section).  Holding the device semaphore will block all
500 policy is to resume all devices during a system resume and let them
568 a shared power well causing power to remain until all ports in the gang
599 rules and require the attached child device and all descendants to be suspended.
609 hub interface driver is unbound, control of its child ports is lost and all
633 another hub.  The expectation is that all superspeed ports have a
667 		Once all children and descendants have suspended the
705 		powered-off at all times.
756 The default configuration is that all ports start with
762 clear pm_qos_no_power_off for all 'not used' ports.  The same can be
767 all ports (set <hubdev-portX>/power/pm_qos_no_power_off to '0') when
769 system.  For example, a distro may want to enable power off all USB