Lines Matching refs:may

73 device is enabled for remote wakeup and it is suspended, it may resume
135 autosuspend_delay_ms.  (There may also be a file named "level"; this
308 	operation.  URBs may once more be submitted.
365 then the interface is considered to be idle, and the kernel may
456 driver may call the usb_autopm_get_interface_async() routine at a time
495 Firstly, a device may already be autosuspended when a system suspend
498 resume.  But this theory may not work out well in practice; over time
503 Secondly, a dynamic power-management event may occur as a system
506 For example, a suspended device may send a remote-wakeup signal while
507 the system is suspending.  The remote wakeup may succeed, which would
509 succeed, it may still remain active and thus cause the system to
511 wakeup may fail and get lost.  Which outcome occurs depends on timing
566 logically off, and may trigger the actual loss of VBUS to the port [3].
567 VBUS may be maintained in the case where a hub gangs multiple ports into
569 are turned off.  VBUS may also be maintained by hub ports configured for
574 WARNING: turning off a port may result in the inability to hot add a device.
603 Note, some interface devices/drivers do not support autosuspend.  Userspace may
632 In addition to these files some ports may have a 'peer' link to a port on
644 While a superspeed port is powered off a device may downgrade its
650    that the setting pm_qos_no_power_off to zero on a superspeed port may not cause
659    power session is lost the device may have been removed, or need reset.
668 		port may suspend/poweroff provided that
702 		to never have a device connected to it.  These may be
713 		information correct, the USB port descriptions may be
769 system.  For example, a distro may want to enable power off all USB
771 active.  Smart phones and tablets may want to power off USB ports when