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