Searched refs:autosuspended (Results 1 – 6 of 6) sorted by relevance
21 the device must be idle before it will be autosuspended.22 0 means the device will be autosuspended as soon as24 being autosuspended at all, and writing a negative value70 autosuspended if all other interface drivers are idle.
694 chip->autosuspended = !!PMSG_IS_AUTO(message); in usb_audio_suspend()695 if (!chip->autosuspended) in usb_audio_suspend()739 if (!chip->autosuspended) in __usb_audio_resume()741 chip->autosuspended = 0; in __usb_audio_resume()
40 unsigned int autosuspended:1; member
100 won't be autosuspended unless it has been idle for some minimum period105 device has been autosuspended and a program tries to use it, the107 same reason, an autosuspended device will usually have remote wakeup115 autosuspended. In effect, the kernel pretends the device is never185 device from being autosuspended. Yes, this is a redundancy in the189 from being autosuspended; the behavior was changed in 2.6.22. The257 This means that non-hub devices won't be autosuspended unless the user270 autosuspended.438 autosuspended, though, setting this flag won't cause the kernel to441 autosuspended.)[all …]
148 (autosuspended), and woken up in response to a hardware-generated
3871 autosuspended. Devices for which the delay is set3872 to a negative value won't be autosuspended at all.