sysfs-bus-usb 5.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144
  1. What: /sys/bus/usb/devices/.../power/autosuspend
  2. Date: March 2007
  3. KernelVersion: 2.6.21
  4. Contact: Alan Stern <stern@rowland.harvard.edu>
  5. Description:
  6. Each USB device directory will contain a file named
  7. power/autosuspend. This file holds the time (in seconds)
  8. the device must be idle before it will be autosuspended.
  9. 0 means the device will be autosuspended as soon as
  10. possible. Negative values will prevent the device from
  11. being autosuspended at all, and writing a negative value
  12. will resume the device if it is already suspended.
  13. The autosuspend delay for newly-created devices is set to
  14. the value of the usbcore.autosuspend module parameter.
  15. What: /sys/bus/usb/devices/.../power/persist
  16. Date: May 2007
  17. KernelVersion: 2.6.23
  18. Contact: Alan Stern <stern@rowland.harvard.edu>
  19. Description:
  20. If CONFIG_USB_PERSIST is set, then each USB device directory
  21. will contain a file named power/persist. The file holds a
  22. boolean value (0 or 1) indicating whether or not the
  23. "USB-Persist" facility is enabled for the device. Since the
  24. facility is inherently dangerous, it is disabled by default
  25. for all devices except hubs. For more information, see
  26. Documentation/usb/persist.txt.
  27. What: /sys/bus/usb/device/.../power/connected_duration
  28. Date: January 2008
  29. KernelVersion: 2.6.25
  30. Contact: Sarah Sharp <sarah.a.sharp@intel.com>
  31. Description:
  32. If CONFIG_PM and CONFIG_USB_SUSPEND are enabled, then this file
  33. is present. When read, it returns the total time (in msec)
  34. that the USB device has been connected to the machine. This
  35. file is read-only.
  36. Users:
  37. PowerTOP <power@bughost.org>
  38. http://www.lesswatts.org/projects/powertop/
  39. What: /sys/bus/usb/device/.../power/active_duration
  40. Date: January 2008
  41. KernelVersion: 2.6.25
  42. Contact: Sarah Sharp <sarah.a.sharp@intel.com>
  43. Description:
  44. If CONFIG_PM and CONFIG_USB_SUSPEND are enabled, then this file
  45. is present. When read, it returns the total time (in msec)
  46. that the USB device has been active, i.e. not in a suspended
  47. state. This file is read-only.
  48. Tools can use this file and the connected_duration file to
  49. compute the percentage of time that a device has been active.
  50. For example,
  51. echo $((100 * `cat active_duration` / `cat connected_duration`))
  52. will give an integer percentage. Note that this does not
  53. account for counter wrap.
  54. Users:
  55. PowerTOP <power@bughost.org>
  56. http://www.lesswatts.org/projects/powertop/
  57. What: /sys/bus/usb/device/<busnum>-<devnum>...:<config num>-<interface num>/supports_autosuspend
  58. Date: January 2008
  59. KernelVersion: 2.6.27
  60. Contact: Sarah Sharp <sarah.a.sharp@intel.com>
  61. Description:
  62. When read, this file returns 1 if the interface driver
  63. for this interface supports autosuspend. It also
  64. returns 1 if no driver has claimed this interface, as an
  65. unclaimed interface will not stop the device from being
  66. autosuspended if all other interface drivers are idle.
  67. The file returns 0 if autosuspend support has not been
  68. added to the driver.
  69. Users:
  70. USB PM tool
  71. git://git.moblin.org/users/sarah/usb-pm-tool/
  72. What: /sys/bus/usb/device/.../authorized
  73. Date: July 2008
  74. KernelVersion: 2.6.26
  75. Contact: David Vrabel <david.vrabel@csr.com>
  76. Description:
  77. Authorized devices are available for use by device
  78. drivers, non-authorized one are not. By default, wired
  79. USB devices are authorized.
  80. Certified Wireless USB devices are not authorized
  81. initially and should be (by writing 1) after the
  82. device has been authenticated.
  83. What: /sys/bus/usb/device/.../wusb_cdid
  84. Date: July 2008
  85. KernelVersion: 2.6.27
  86. Contact: David Vrabel <david.vrabel@csr.com>
  87. Description:
  88. For Certified Wireless USB devices only.
  89. A devices's CDID, as 16 space-separated hex octets.
  90. What: /sys/bus/usb/device/.../wusb_ck
  91. Date: July 2008
  92. KernelVersion: 2.6.27
  93. Contact: David Vrabel <david.vrabel@csr.com>
  94. Description:
  95. For Certified Wireless USB devices only.
  96. Write the device's connection key (CK) to start the
  97. authentication of the device. The CK is 16
  98. space-separated hex octets.
  99. What: /sys/bus/usb/device/.../wusb_disconnect
  100. Date: July 2008
  101. KernelVersion: 2.6.27
  102. Contact: David Vrabel <david.vrabel@csr.com>
  103. Description:
  104. For Certified Wireless USB devices only.
  105. Write a 1 to force the device to disconnect
  106. (equivalent to unplugging a wired USB device).
  107. What: /sys/bus/usb/drivers/.../remove_id
  108. Date: November 2009
  109. Contact: CHENG Renquan <rqcheng@smu.edu.sg>
  110. Description:
  111. Writing a device ID to this file will remove an ID
  112. that was dynamically added via the new_id sysfs entry.
  113. The format for the device ID is:
  114. idVendor idProduct. After successfully
  115. removing an ID, the driver will no longer support the
  116. device. This is useful to ensure auto probing won't
  117. match the driver to the device. For example:
  118. # echo "046d c315" > /sys/bus/usb/drivers/foo/remove_id
  119. What: /sys/bus/usb/device/.../avoid_reset_quirk
  120. Date: December 2009
  121. Contact: Oliver Neukum <oliver@neukum.org>
  122. Description:
  123. Writing 1 to this file tells the kernel that this
  124. device will morph into another mode when it is reset.
  125. Drivers will not use reset for error handling for
  126. such devices.
  127. Users:
  128. usb_modeswitch