sysfs-driver-hid-wiimote 3.7 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485
  1. What: /sys/bus/hid/drivers/wiimote/<dev>/led1
  2. What: /sys/bus/hid/drivers/wiimote/<dev>/led2
  3. What: /sys/bus/hid/drivers/wiimote/<dev>/led3
  4. What: /sys/bus/hid/drivers/wiimote/<dev>/led4
  5. Date: July 2011
  6. KernelVersion: 3.1
  7. Contact: David Herrmann <dh.herrmann@googlemail.com>
  8. Description: Make it possible to set/get current led state. Reading from it
  9. returns 0 if led is off and 1 if it is on. Writing 0 to it
  10. disables the led, writing 1 enables it.
  11. What: /sys/bus/hid/drivers/wiimote/<dev>/extension
  12. Date: August 2011
  13. KernelVersion: 3.2
  14. Contact: David Herrmann <dh.herrmann@gmail.com>
  15. Description: This file contains the currently connected and initialized
  16. extensions. It can be one of: none, motionp, nunchuck, classic,
  17. motionp+nunchuck, motionp+classic
  18. motionp is the official Nintendo Motion+ extension, nunchuck is
  19. the official Nintendo Nunchuck extension and classic is the
  20. Nintendo Classic Controller extension. The motionp extension can
  21. be combined with the other two.
  22. Starting with kernel-version 3.11 Motion Plus hotplugging is
  23. supported and if detected, it's no longer reported as static
  24. extension. You will get uevent notifications for the motion-plus
  25. device then.
  26. What: /sys/bus/hid/drivers/wiimote/<dev>/devtype
  27. Date: May 2013
  28. KernelVersion: 3.11
  29. Contact: David Herrmann <dh.herrmann@gmail.com>
  30. Description: While a device is initialized by the wiimote driver, we perform
  31. a device detection and signal a "change" uevent after it is
  32. done. This file shows the detected device type. "pending" means
  33. that the detection is still ongoing, "unknown" means, that the
  34. device couldn't be detected or loaded. "generic" means, that the
  35. device couldn't be detected but supports basic Wii Remote
  36. features and can be used.
  37. Other strings for each device-type are available and may be
  38. added if new device-specific detections are added.
  39. Currently supported are:
  40. ============= =======================================
  41. gen10: First Wii Remote generation
  42. gen20: Second Wii Remote Plus generation
  43. (builtin MP)
  44. balanceboard: Wii Balance Board
  45. ============= =======================================
  46. What: /sys/bus/hid/drivers/wiimote/<dev>/bboard_calib
  47. Date: May 2013
  48. KernelVersion: 3.11
  49. Contact: David Herrmann <dh.herrmann@gmail.com>
  50. Description: This attribute is only provided if the device was detected as a
  51. balance board. It provides a single line with 3 calibration
  52. values for all 4 sensors. The values are separated by colons and
  53. are each 2 bytes long (encoded as 4 digit hexadecimal value).
  54. First, 0kg values for all 4 sensors are written, followed by the
  55. 17kg values for all 4 sensors and last the 34kg values for all 4
  56. sensors.
  57. Calibration data is already applied by the kernel to all input
  58. values but may be used by user-space to perform other
  59. transformations.
  60. What: /sys/bus/hid/drivers/wiimote/<dev>/pro_calib
  61. Date: October 2013
  62. KernelVersion: 3.13
  63. Contact: David Herrmann <dh.herrmann@gmail.com>
  64. Description: This attribute is only provided if the device was detected as a
  65. pro-controller. It provides a single line with 4 calibration
  66. values for all 4 analog sticks. Format is: "x1:y1 x2:y2". Data
  67. is prefixed with a +/-. Each value is a signed 16bit number.
  68. Data is encoded as decimal numbers and specifies the offsets of
  69. the analog sticks of the pro-controller.
  70. Calibration data is already applied by the kernel to all input
  71. values but may be used by user-space to perform other
  72. transformations.
  73. Calibration data is detected by the kernel during device setup.
  74. You can write "scan\n" into this file to re-trigger calibration.
  75. You can also write data directly in the form "x1:y1 x2:y2" to
  76. set the calibration values manually.