Lines Matching full:autosuspend
20 * The driver interface for autosuspend and autoresume
104 device. This is called ``autosuspend`` for short. In general, a device
116 autosuspend. In fact, at the time of this writing (Linux 2.6.23) the
128 triggered within the USB stack: autosuspend and autoresume. Note that
142 ``control`` file. In 2.6.38 the ``autosuspend`` file will be deprecated
146 but only ``autosuspend`` works.)
166 autosuspend is not allowed. (Of course, system
170 allowed to autosuspend and autoresume the device.
181 before the kernel will autosuspend it (the idle-delay
182 time). The default is 2000. 0 means to autosuspend
184 values mean never to autosuspend. You can write a
185 number to the file to change the autosuspend
193 (In 2.6.21 writing ``0`` to ``power/autosuspend`` would prevent the device
195 ``power/autosuspend`` attribute did not exist prior to 2.6.21, and the
204 The default autosuspend idle-delay time (in seconds) is controlled by
209 modprobe usbcore autosuspend=5
214 options usbcore autosuspend=5
224 usbcore.autosuspend=5
231 echo 5 >/sys/module/usbcore/parameters/autosuspend
233 then each new USB device will have its autosuspend idle-delay
238 autosuspend of any USB device. This has the benefit of allowing you
239 then to enable autosuspend for selected devices.
253 For this reason, by default the kernel disables autosuspend (the
258 (In 2.6.21 and 2.6.22 this wasn't the case. Autosuspend was enabled
272 it can enable autosuspend all by itself. For example, the video
278 autosuspend there are still problems. For example, the usbhid driver,
279 which manages keyboards and mice, has autosuspend support. Tests with
286 The kernel will not prevent you from enabling autosuspend on devices
349 The driver interface for autosuspend and autoresume
352 To support autosuspend and autoresume, a driver should implement all
354 that it supports autosuspend by setting the ``.supports_autosuspend`` flag
369 autosuspend the interface's device. When the usage counter is = 0
371 autosuspend the device.
391 attempts an autosuspend if the new value is = 0.
404 an autoresume or an autosuspend. Hence they can be called in
412 The autosuspend attempts mentioned above will often fail for one
417 carry out the operation automatically when the autosuspend idle-delay
422 autosuspend, there's no idle-delay for an autoresume.
428 Drivers can enable autosuspend for their devices by calling::
435 drivers can disable autosuspend by calling::
442 during autosuspend. For example, there's not much point
445 ``intf->needs_remote_wakeup`` to 1, the kernel won't autosuspend the
460 busy and therefore the next autosuspend idle-delay expiration should
474 only autosuspend calls. The driver can tell them apart by applying
476 method; it will return True for internal PM events (autosuspend) and
483 For external events -- but not necessarily for autosuspend or
488 this is true of autosuspend/autoresume events as well.
624 Note, some interface devices/drivers do not support autosuspend. Userspace may
684 child device can suspend (autosuspend-delay) and resume (reset-resume