Lines Matching refs:idle

12 	* When is a USB device idle?
15 	* Changing the default idle-delay time
79 	When is a USB device idle?
82 A device is idle whenever the kernel thinks it's not busy doing
85 to declare that a device isn't idle even when there's no actual
86 communication taking place.  (For example, a hub isn't considered idle
88 In addition, a device isn't considered idle so long as a program keeps
92 being accessed through sysfs, then it definitely is idle.
98 Dynamic suspends occur when the kernel decides to suspend an idle
100 won't be autosuspended unless it has been idle for some minimum period
101 of time, the so-called idle-delay time.
116 idle.
175 		number of milliseconds the device should remain idle
176 		before the kernel will autosuspend it (the idle-delay
178 		as soon as the device becomes idle, and negative
181 		idle-delay time.
196 	Changing the default idle-delay time
199 The default autosuspend idle-delay time (in seconds) is controlled by
228 then each new USB device will have its autosuspend idle-delay
229 initialized to 5.  (The idle-delay values for already existing devices
232 Setting the initial default idle-delay to -1 will prevent any
263 also change the idle-delay time; 2 seconds is not the best choice for
351 USB core whenever one of its interfaces becomes busy or idle.  The
365 then the interface is considered to be idle, and the kernel may
406 idle.  This is perfectly normal.  If the reason for failure was that
407 the device hasn't been idle for long enough, a timer is scheduled to
408 carry out the operation automatically when the autosuspend idle-delay
413 autosuspend, there's no idle-delay for an autoresume.
451 busy and therefore the next autosuspend idle-delay expiration should
457 when the core has just finished deciding the device has been idle for
654 		This writable flag controls the state of an idle port.