Lines Matching refs:its

89 its usbfs file open, whether or not any I/O is going on.
91 If a USB device has no driver, its usbfs file isn't open, and it isn't
103 Of course, nothing the kernel does on its own initiative should
104 prevent the computer or its devices from working properly.  If a
228 then each new USB device will have its autosuspend idle-delay
266 If a driver knows that its device has proper suspend/resume support,
297 methods in its usb_driver structure, and the reset_resume method is
313 	since the device has probably lost most or all of its state
350 in its usb_driver structure.  It is then responsible for informing the
351 USB core whenever one of its interfaces becomes busy or idle.  The
370 is unbound from its interface.  As a corollary, drivers must not call
399 usb_autopm_get_interface() in its open routine and
400 usb_autopm_put_interface() in its close or release routine.  But other
439 autoresume it.  Normally a driver would set this flag in its probe
443 If a driver does its I/O asynchronously in interrupt context, it
559 connection with its device, not respond to hotplug events, and not
588 This mechanism is dependent on the hub advertising port power switching in its
597 hub interface driver is unbound, control of its child ports is lost and all
632 While a superspeed port is powered off a device may downgrade its
639    the port to power-off until its highspeed peer has gone to its runtime suspend
643 2/ Port resume is sequenced to force a superspeed port to power-on prior to its
728 		its driver.