Lines Matching +full:usb +full:- +full:c
1 What: /sys/bus/usb/devices/INTERFACE/authorized
9 by writing INTERFACE to /sys/bus/usb/drivers_probe
10 This allows to avoid side-effects with drivers
15 What: /sys/bus/usb/devices/usbX/interface_authorized_default
22 What: /sys/bus/usb/device/.../authorized
28 drivers, non-authorized one are not. By default, wired
29 USB devices are authorized.
31 Certified Wireless USB devices are not authorized
35 What: /sys/bus/usb/device/.../wusb_cdid
40 For Certified Wireless USB devices only.
42 A devices's CDID, as 16 space-separated hex octets.
44 What: /sys/bus/usb/device/.../wusb_ck
49 For Certified Wireless USB devices only.
53 space-separated hex octets.
55 What: /sys/bus/usb/device/.../wusb_disconnect
60 For Certified Wireless USB devices only.
63 (equivalent to unplugging a wired USB device).
65 What: /sys/bus/usb/drivers/.../new_id
67 Contact: linux-usb@vger.kernel.org
70 dynamically add a new device ID to a USB device driver.
82 # echo "8086 10f5" > /sys/bus/usb/drivers/foo/new_id
85 an already supported device (0458:704c)::
87 # echo "0458 7045 0 0458 704c" > /sys/bus/usb/drivers/foo/new_id
93 # cat /sys/bus/usb/drivers/foo/new_id
101 What: /sys/bus/usb-serial/drivers/.../new_id
103 Contact: linux-usb@vger.kernel.org
105 For serial USB drivers, this attribute appears under the
106 extra bus folder "usb-serial" in sysfs; apart from that
108 "/sys/bus/usb/drivers/.../new_id" apply.
110 What: /sys/bus/usb/drivers/.../remove_id
121 # echo "046d c315" > /sys/bus/usb/drivers/foo/remove_id
125 "/sys/bus/usb/drivers/.../new_id"
127 What: /sys/bus/usb/devices/.../power/usb2_hardware_lpm
131 If CONFIG_PM is set and a USB 2.0 lpm-capable device is plugged
135 device and the USB device directory will contain a file named
141 What: /sys/bus/usb/devices/.../power/usb3_hardware_lpm_u1
142 /sys/bus/usb/devices/.../power/usb3_hardware_lpm_u2
147 If CONFIG_PM is set and a USB 3.0 lpm-capable device is plugged
151 USB3 hardware LPM will be enabled for the device and the USB
157 What: /sys/bus/usb/devices/.../removable
161 Some information about whether a given USB device is
163 combination of hub descriptor bits and platform-specific data
168 What: /sys/bus/usb/devices/.../ltm_capable
172 USB 3.0 devices may optionally support Latency Tolerance
177 The file will be present for all speeds of USB devices, and will
178 always read "no" for USB 1.1 and USB 2.0 devices.
180 What: /sys/bus/usb/devices/.../(hub interface)/portX
184 The /sys/bus/usb/devices/.../(hub interface)/portX
185 is usb port device's sysfs directory.
187 What: /sys/bus/usb/devices/.../(hub interface)/portX/connect_type
191 Some platforms provide usb port connect types through ACPI.
196 What: /sys/bus/usb/devices/.../(hub interface)/portX/location
200 Some platforms provide usb port physical location through
206 What: /sys/bus/usb/devices/.../(hub interface)/portX/quirks
210 In some cases, we care about time-to-active for devices
211 connected on a specific port (e.g. non-standard USB port like
214 This attribute is a bit-field that controls the behavior of
217 - Bit 0 of this field selects the "old" enumeration scheme,
218 as it is considerably faster (it only causes one USB reset
225 - Bit 1 reduces TRSTRCY to the 10 ms that are required by the
226 USB 2.0 specification, instead of the 50 ms that are normally
230 What: /sys/bus/usb/devices/.../(hub interface)/portX/over_current_count
234 Most hubs are able to detect over-current situations on their
236 the number of over-current situation occurred on a specific port
244 OVER_CURRENT_PORT=/sys/bus/usb/devices/.../(hub interface)/portX
247 What: /sys/bus/usb/devices/.../(hub interface)/portX/usb3_lpm_permit
253 effect both before and after a usb device is enumerated. Supported
258 What: /sys/bus/usb/devices/.../power/usb2_lpm_l1_timeout
262 USB 2.0 devices may support hardware link power management (LPM)
267 Supported values are 0 - 65535 microseconds.
269 What: /sys/bus/usb/devices/.../power/usb2_lpm_besl
273 USB 2.0 devices that support hardware link power management (LPM)
281 Supported values are 0 - 15.
283 USB 2.0 ECN Errata for Link Power Management, section 4.10)
285 What: /sys/bus/usb/devices/.../rx_lanes
290 USB 3.2 adds Dual-lane support, 2 rx and 2 tx lanes over Type-C.
291 Inter-Chip SSIC devices support asymmetric lanes up to 4 lanes per
292 direction. Devices before USB 3.2 are single lane (rx_lanes = 1)
294 What: /sys/bus/usb/devices/.../tx_lanes
299 USB 3.2 adds Dual-lane support, 2 rx and 2 tx -lanes over Type-C.
300 Inter-Chip SSIC devices support asymmetric lanes up to 4 lanes per
301 direction. Devices before USB 3.2 are single lane (tx_lanes = 1)