Lines Matching refs:device
1 What: /sys/bus/usb/device/.../authorized
6 Authorized devices are available for use by device
12 device has been authenticated.
14 What: /sys/bus/usb/device/.../wusb_cdid
23 What: /sys/bus/usb/device/.../wusb_ck
30 Write the device's connection key (CK) to start the
31 authentication of the device. The CK is 16
34 What: /sys/bus/usb/device/.../wusb_disconnect
41 Write a 1 to force the device to disconnect
42 (equivalent to unplugging a wired USB device).
48 Writing a device ID to this file will attempt to
49 dynamically add a new device ID to a USB device driver.
51 was included in the driver's static device ID support
52 table at compile time. The format for the device ID is:
54 The vendor ID and device ID fields are required, the
56 driver to use the same driver_data for the new device as
57 it is used for the reference device.
59 for the device and attempt to bind to it. For example:
62 Here add a new device (0458:7045) using driver_data from
63 an already supported device (0458:704c):
67 device IDs in the same format, with one entry per
90 Writing a device ID to this file will remove an ID
92 The format for the device ID is:
95 device. This is useful to ensure auto probing won't
96 match the driver to the device. For example:
100 device IDs, exactly like reading from the entry
107 If CONFIG_PM is set and a USB 2.0 lpm-capable device is plugged
111 device and the USB device directory will contain a file named
114 enabled for the device. Developer can write y/Y/1 or n/N/0 to
121 Some information about whether a given USB device is
135 If that bit is set for the device, ltm_capable will read "yes".
136 If the device doesn't support LTM, the file will read "no".
145 is usb port device's sysfs directory.
163 needed inactivity time before host requests the device to go to L1 sleep.
173 indicate the best effort to resumption of service to the device after the
175 If the device does not have a preferred besl value then the host can select