Home
last modified time | relevance | path

Searched refs:autosuspended (Results 1 – 6 of 6) sorted by relevance

/Linux-v5.4/Documentation/ABI/stable/
Dsysfs-bus-usb21 the device must be idle before it will be autosuspended.
22 0 means the device will be autosuspended as soon as
24 being autosuspended at all, and writing a negative value
70 autosuspended if all other interface drivers are idle.
/Linux-v5.4/sound/usb/
Dusbaudio.h29 unsigned int autosuspended:1; member
Dcard.c809 chip->autosuspended = !!PMSG_IS_AUTO(message); in usb_audio_suspend()
810 if (!chip->autosuspended) in usb_audio_suspend()
862 if (!chip->autosuspended) in __usb_audio_resume()
864 chip->autosuspended = 0; in __usb_audio_resume()
/Linux-v5.4/Documentation/driver-api/usb/
Dpower-management.rst105 won't be autosuspended unless it has been idle for some minimum period
110 device has been autosuspended and a program tries to use it, the
112 same reason, an autosuspended device will usually have remote wakeup
120 autosuspended. In effect, the kernel pretends the device is never
190 device from being autosuspended. Yes, this is a redundancy in the
194 from being autosuspended; the behavior was changed in 2.6.22. The
262 This means that non-hub devices won't be autosuspended unless the user
275 autosuspended.
447 autosuspended, though, setting this flag won't cause the kernel to
450 autosuspended.)
[all …]
/Linux-v5.4/kernel/power/
DKconfig159 (autosuspended), and woken up in response to a hardware-generated
/Linux-v5.4/Documentation/admin-guide/
Dkernel-parameters.txt4978 autosuspended. Devices for which the delay is set
4979 to a negative value won't be autosuspended at all.