# Human Interface Device Game Controller [Linux Kernel Drivers HID Kconfig](https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/hid/Kconfig) ```bash # # HID driver configuration # menu "HID support" depends on INPUT config HID tristate "HID bus support" depends on INPUT default y ---help--- A human interface device (HID) is a type of computer device that interacts directly with and takes input from humans. The term "HID" most commonly used to refer to the USB-HID specification, but other devices (such as, but not strictly limited to, Bluetooth) are designed using HID specification (this involves certain keyboards, mice, tablets, etc). This option adds the HID bus to the kernel, together with generic HID layer code. The HID devices are added and removed from the HID bus by the transport-layer drivers, such as usbhid (USB_HID) and hidp (BT_HIDP). For docs and specs, see http://www.usb.org/developers/hidpage/ ``` ```bash config HID_GENERIC tristate "Generic HID driver" depends on HID default HID ---help--- Support for generic devices on the HID bus. This includes most keyboards and mice, joysticks, tablets and digitizers. To compile this driver as a module, choose M here: the module will be called hid-generic. ``` ```bash root@edison:~# bluetoothctl [NEW] Controller 98:4F:EE:04:21:2A edison [default] [NEW] Device 58:51:00:00:41:4D BT MINI [NEW] Device 6F:E8:92:3B:FB:06 6F-E8-92-3B-FB-06 [NEW] Device F1:C1:83:A4:17:0C Evolutel ``` ```bash [bluetooth]# scan on Discovery started [CHG] Controller 98:4F:EE:04:21:2A Discovering: yes [CHG] Device F1:C1:83:A4:17:0C RSSI: -53 [CHG] Device F1:C1:83:A4:17:0C TxPower: -12 [NEW] Device 20:16:04:13:03:CE 20-16-04-13-03-CE [CHG] Device 20:16:04:13:03:CE LegacyPairing: no [CHG] Device 20:16:04:13:03:CE Name: VR-PARK [CHG] Device 20:16:04:13:03:CE Alias: VR-PARK [CHG] Device 20:16:04:13:03:CE LegacyPairing: yes ``` ```bash [bluetooth]# scan off [CHG] Device 20:16:04:13:03:CE RSSI is nil [CHG] Device F1:C1:83:A4:17:0C TxPower is nil [CHG] Device F1:C1:83:A4:17:0C RSSI is nil [CHG] Controller 98:4F:EE:04:21:2A Discovering: no Discovery stopped [bluetooth]# ``` ```bash [bluetooth]# pair 20:16:04:13:03:CE Attempting to pair with 20:16:04:13:03:CE [CHG] Device 20:16:04:13:03:CE Connected: yes [CHG] Device 20:16:04:13:03:CE Modalias: usb:v05ACp3232d0001 [CHG] Device 20:16:04:13:03:CE UUIDs: 00001124-0000-1000-8000-00805f9b34fb [CHG] Device 20:16:04:13:03:CE UUIDs: 00001200-0000-1000-8000-00805f9b34fb [CHG] Device 20:16:04:13:03:CE Paired: yes Pairing successful [CHG] Device 20:16:04:13:03:CE Connected: no ``` ```bash [bluetooth]# connect 20:16:04:13:03:CE Attempting to connect to 20:16:04:13:03:CE [CHG] Device 20:16:04:13:03:CE Connected: yes Connection successful [VR-PARK]# [ 1811.274092] hid-generic 0005:05AC:3232.0002: unknown main item tag 0x0 ``` ```bash [VR-PARK]# paired-devices Device 20:16:04:13:03:CE VR-PARK [VR-PARK]# exit [DEL] Controller 98:4F:EE:04:21:2A edison [default] ``` ```bash root@edison:~# dmesg [ 1404.240260] pmic_ccsm pmic_ccsm: USB VBUS Removed. Notifying OTG driver [ 1685.170050] hid-generic 0005:05AC:3232.0001: unknown main item tag 0x0 [ 1685.171030] input: VR-PARK as /devices/pci0000:00/0000:00:04.1/tty/ttyMFD0/h ci0/hci0:12/input3 [ 1685.179288] hid-generic 0005:05AC:3232.0001: input,hidraw0: BLUETOOTH HID v0 .01 Mouse [VR-PARK] on 98:4f:ee:04:21:2a [ 1811.274092] hid-generic 0005:05AC:3232.0002: unknown main item tag 0x0 [ 1811.275029] input: VR-PARK as /devices/pci0000:00/0000:00:04.1/tty/ttyMFD0/h ci0/hci0:11/input4 [ 1811.288008] hid-generic 0005:05AC:3232.0002: input,hidraw0: BLUETOOTH HID v0 .01 Mouse [VR-PARK] on 98:4f:ee:04:21:2a [ 2323.876693] perf samples too long (2540 > 2500), lowering kernel.perf_event_ max_sample_rate to 50000 ``` ```bash root@edison:~# cat /sys/class/bluetooth/hci0/name edison root@edison:~# ls /sys/class/bluetooth/hci0 hci0/ hci0:11/ root@edison:~# ls /sys/class/bluetooth/hci0:11/ 0005:05AC:3232.0002 device input4 subsystem uevent address features power type root@edison:~# cat /sys/class/bluetooth/hci0:11/type ACL root@edison:~# ls /sys/class/bluetooth/hci0:11/input4/ capabilities event2 modalias phys properties uevent device id name power subsystem uniq root@edison:~# cat /sys/class/bluetooth/hci0:11/input4/name VR-PARK root@edison:~# ``` ```bash root@edison:~#wget https://raw.githubusercontent.com/TheIoTLearningInitiative/EmbeddedLinux/master/tools/evtest.c --2016-10-17 02:33:48-- https://raw.githubusercontent.com/TheIoTLearningInitiative/EmbeddedLinux/master/tools/evtest.c Resolving raw.githubusercontent.com... 151.101.48.133 Connecting to raw.githubusercontent.com|151.101.48.133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 15169 (15K) [text/plain] Saving to: 'evtest.c' 100%[======================================>] 15,169 --.-K/s in 0.1s 2016-10-17 02:33:50 (124 KB/s) - 'evtest.c' saved [15169/15169] FINISHED --2016-10-17 02:33:50-- Total wall clock time: 17s Downloaded: 1 files, 15K in 0.1s (124 KB/s) ``` ```bash root@edison:~# gcc -o evtest evtest.c ``` ```bash root@edison:~# ./evtest /dev/input/event2 ... Testing ... (interrupt to exit) Event: time 1476671884.164894, type 4 (Misc), code 4 (ScanCode), value 90005 Event: time 1476671884.164894, type 1 (Key), code 308 (BtnY), value 1 Event: time 1476671884.164894, -------------- Report Sync ------------ Event: time 1476671884.296148, type 4 (Misc), code 4 (ScanCode), value 90005 Event: time 1476671884.296148, type 1 (Key), code 308 (BtnY), value 0 Event: time 1476671884.296148, -------------- Report Sync ------------ ``` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://theiotlearninginitiative.gitbook.io/embedded-linux/subsystems/bluetooth/human-interface-device-game-controller.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.