2 # HID driver configuration
8 tristate "HID bus support"
12 A human interface device (HID) is a type of computer device that
13 interacts directly with and takes input from humans. The term "HID"
14 most commonly used to refer to the USB-HID specification, but other
15 devices (such as, but not strictly limited to, Bluetooth) are
16 designed using HID specification (this involves certain keyboards,
17 mice, tablets, etc). This option adds the HID bus to the kernel,
18 together with generic HID layer code. The HID devices are added and
19 removed from the HID bus by the transport-layer drivers, such as
20 usbhid (USB_HID) and hidp (BT_HIDP).
22 For docs and specs, see http://www.usb.org/developers/hidpage/
28 config HID_BATTERY_STRENGTH
29 bool "Battery level reporting for HID devices"
30 depends on HID && POWER_SUPPLY && HID = POWER_SUPPLY
33 This option adds support of reporting battery strength (for HID devices
34 that support this feature) through power_supply class so that userspace
35 tools, such as upower, can display it.
38 bool "/dev/hidraw raw HID device support"
41 Say Y here if you want to support HID devices (from the USB
42 specification standpoint) that aren't strictly user interface
43 devices, like monitor controls and Uninterruptable Power Supplies.
45 This module supports these devices separately using a separate
46 event interface on /dev/hidraw.
48 There is also a /dev/hiddev configuration option in the USB HID
49 configuration menu. In comparison to hiddev, this device does not process
50 the hid events at all (no parsing, no lookups). This lets applications
51 to work on raw hid events when they want to, and avoid using transport-specific
52 userspace libhid/libusb libraries.
57 tristate "User-space I/O driver support for HID subsystem"
61 Say Y here if you want to provide HID I/O Drivers from user-space.
62 This allows to write I/O drivers in user-space and feed the data from
63 the device into the kernel. The kernel parses the HID reports, loads the
64 corresponding HID Device Driver or provides input devices on top of your
67 This driver cannot be used to parse HID-reports in user-space and write
68 special HID-drivers. You should use hidraw for that.
69 Instead, this driver allows to write the transport-layer driver in
70 user-space like USB-HID and Bluetooth-HID do in kernel-space.
74 To compile this driver as a module, choose M here: the
75 module will be called uhid.
78 tristate "Generic HID driver"
82 Support for generic devices on the HID bus. This includes most
83 keyboards and mice, joysticks, tablets and digitizers.
85 To compile this driver as a module, choose M here: the module
86 will be called hid-generic.
90 menu "Special HID drivers"
94 tristate "A4 tech mice" if EXPERT
98 Support for A4 tech X5 and WOP-35 / Trust 450L mice.
101 tristate "ACRUX game controller support"
104 Say Y here if you want to enable support for ACRUX game controllers.
107 bool "ACRUX force feedback support"
109 select INPUT_FF_MEMLESS
111 Say Y here if you want to enable force feedback support for ACRUX
115 tristate "Apple {i,Power,Mac}Books" if EXPERT
119 Support for some Apple devices which less or more break
122 Say Y here if you want support for keyboards of Apple iBooks, PowerBooks,
123 MacBooks, MacBook Pros and Apple Aluminum.
126 tristate "Apple infrared receiver"
129 Support for Apple infrared remote control. All the Apple computers from
130 2005 onwards include such a port, except the unibody Macbook (2009),
131 and Mac Pros. This receiver is also used in the Apple TV set-top box
132 prior to the 2010 model.
134 Say Y here if you want support for Apple infrared remote control.
140 Support for Aureal Cy se W-01RN Remote Controller and other Aureal derived remotes.
143 tristate "Belkin Flip KVM and Wireless keyboard" if EXPERT
147 Support for Belkin Flip KVM and Wireless keyboard.
150 tristate "Cherry Cymotion keyboard" if EXPERT
154 Support for Cherry Cymotion keyboard.
157 tristate "Chicony Tactical pad" if EXPERT
161 Support for Chicony Tactical pad.
164 tristate "Prodikeys PC-MIDI Keyboard support"
165 depends on HID && SND
168 Support for Prodikeys PC-MIDI Keyboard device support.
169 Say Y here to enable support for this device.
170 - Prodikeys PC-MIDI keyboard.
171 The Prodikeys PC-MIDI acts as a USB Audio device, with one MIDI
172 input and one MIDI output. These MIDI jacks appear as
173 a sound "card" in the ALSA sound system.
174 Note: if you say N here, this device will still function as a basic
175 multimedia keyboard, but will lack support for the musical keyboard
176 and some additional multimedia keys.
179 tristate "Cypress mouse and barcode readers" if EXPERT
183 Support for cypress mouse and barcode readers.
185 config HID_DRAGONRISE
186 tristate "DragonRise Inc. game controller"
189 Say Y here if you have DragonRise Inc. game controllers.
190 These might be branded as:
192 - Media-tech MT1504 "Rogue"
194 - Defender Game Master
197 bool "DragonRise Inc. force feedback"
198 depends on HID_DRAGONRISE
199 select INPUT_FF_MEMLESS
201 Say Y here if you want to enable force feedback support for DragonRise Inc.
205 tristate "EMS Production Inc. force feedback support"
207 select INPUT_FF_MEMLESS
209 Say Y here if you want to enable force feedback support for devices by
211 Currently the following devices are known to be supported:
212 - Trio Linker Plus II
215 tristate "ELECOM BM084 bluetooth mouse"
218 Support for the ELECOM BM084 (bluetooth mouse).
221 tristate "ELO USB 4000/4500 touchscreen"
224 Support for the ELO USB 4000/4500 touchscreens. Note that this is for
225 different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
228 tristate "Ezkey BTC 8193 keyboard" if EXPERT
232 Support for Ezkey BTC 8193 keyboard.
235 tristate "Holtek HID devices"
238 Support for Holtek based devices:
239 - Holtek On Line Grip based game controller
240 - Trust GXT 18 Gaming Keyboard
241 - Sharkoon Drakonia / Perixx MX-2000 gaming mice
242 - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
244 - SHARKOON DarkGlider Gaming mouse
247 bool "Holtek On Line Grip force feedback support"
248 depends on HID_HOLTEK
249 select INPUT_FF_MEMLESS
251 Say Y here if you have a Holtek On Line Grip based game controller
252 and want to have force feedback support for it.
255 tristate "Huion tablets"
258 Support for Huion 580 tablet.
261 tristate "Keytouch HID devices"
264 Support for Keytouch HID devices not fully compliant with
265 the specification. Currently supported:
269 tristate "KYE/Genius devices"
272 Support for KYE/Genius devices not fully compliant with HID standard:
274 - EasyPen i405X tablet
275 - MousePen i608X tablet
276 - EasyPen M610X tablet
282 Support for UC-Logic tablets.
288 Support for Waltop tablets.
291 tristate "Gyration remote control"
294 Support for Gyration remote control.
297 tristate "ION iCade arcade controller"
300 Support for the ION iCade arcade controller to work as a joystick.
302 To compile this driver as a module, choose M here: the
303 module will be called hid-icade.
306 tristate "Twinhan IR remote control"
309 Support for Twinhan IR remote control.
311 config HID_KENSINGTON
312 tristate "Kensington Slimblade Trackball" if EXPERT
316 Support for Kensington Slimblade Trackball.
322 Support for LC-Power RC1000MCE RF remote control.
324 config HID_LENOVO_TPKBD
325 tristate "Lenovo ThinkPad USB Keyboard with TrackPoint"
330 Support for the Lenovo ThinkPad USB Keyboard with TrackPoint.
332 Say Y here if you have a Lenovo ThinkPad USB Keyboard with TrackPoint
333 and would like to use device-specific features like changing the
334 sensitivity of the trackpoint, using the microphone mute button or
335 controlling the mute and microphone mute LEDs.
338 tristate "Logitech devices" if EXPERT
342 Support for Logitech devices that are not fully compliant with HID standard.
344 config HID_LOGITECH_DJ
345 tristate "Logitech Unifying receivers full support"
346 depends on HID_LOGITECH
348 Say Y if you want support for Logitech Unifying receivers and devices.
349 Unifying receivers are capable of pairing up to 6 Logitech compliant
350 devices to the same receiver. Without this driver it will be handled by
351 generic USB_HID driver and all incoming events will be multiplexed
352 into a single mouse and a single keyboard device.
355 bool "Logitech force feedback support"
356 depends on HID_LOGITECH
357 select INPUT_FF_MEMLESS
359 Say Y here if you have one of these devices:
360 - Logitech WingMan Cordless RumblePad
361 - Logitech WingMan Cordless RumblePad 2
362 - Logitech WingMan Force 3D
363 - Logitech Formula Force EX
364 - Logitech WingMan Formula Force GP
365 - Logitech MOMO Force wheel
367 and if you want to enable force feedback for them.
368 Note: if you say N here, this device will still be supported, but without
371 config LOGIRUMBLEPAD2_FF
372 bool "Logitech RumblePad/Rumblepad 2 force feedback support"
373 depends on HID_LOGITECH
374 select INPUT_FF_MEMLESS
376 Say Y here if you want to enable force feedback support for Logitech
377 RumblePad and Rumblepad 2 devices.
380 bool "Logitech Flight System G940 force feedback support"
381 depends on HID_LOGITECH
382 select INPUT_FF_MEMLESS
384 Say Y here if you want to enable force feedback support for Logitech
385 Flight System G940 devices.
388 bool "Logitech wheels configuration and force feedback support"
389 depends on HID_LOGITECH
390 select INPUT_FF_MEMLESS
393 Say Y here if you want to enable force feedback and range setting
394 support for following Logitech wheels:
395 - Logitech Driving Force
396 - Logitech Driving Force Pro
397 - Logitech Driving Force GT
400 - Logitech MOMO/MOMO 2
401 - Logitech Formula Force EX
403 config HID_MAGICMOUSE
404 tristate "Apple Magic Mouse/Trackpad multi-touch support"
407 Support for the Apple Magic Mouse/Trackpad multi-touch.
409 Say Y here if you want support for the multi-touch features of the
410 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
413 tristate "Microsoft non-fully HID-compliant devices" if EXPERT
417 Support for Microsoft devices that are not fully compliant with HID standard.
420 tristate "Monterey Genius KB29E keyboard" if EXPERT
424 Support for Monterey Genius KB29E.
426 config HID_MULTITOUCH
427 tristate "HID Multitouch panels"
430 Generic support for HID multitouch panels.
432 Say Y here if you have one of the following devices:
433 - 3M PCT touch screens
434 - ActionStar dual touch panels
436 - Cando dual touch panels
439 - Cypress TrueTouch panels
440 - Elo TouchSystems IntelliTouch Plus panels
441 - GeneralTouch 'Sensing Win7-TwoFinger' panels
443 - Hanvon dual touch panels
444 - Ilitek dual touch panels
445 - IrTouch Infrared USB panels
446 - LG Display panels (Dell ST2220Tc)
447 - Lumio CrystalTouch panels
448 - MosArt dual-touch panels
449 - Panasonic multitouch panels
450 - PenMount dual touch panels
451 - Perixx Peripad 701 touchpad
452 - PixArt optical touch screen
453 - Pixcir dual touch panels
455 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
456 - Stantum multitouch panels
457 - Touch International Panels
459 - XAT optical touch panels
460 - Xiroku optical touch panels
461 - Zytronic touch panels
465 To compile this driver as a module, choose M here: the
466 module will be called hid-multitouch.
469 tristate "N-Trig touch screen"
472 Support for N-Trig touch screen.
475 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
478 There are certain devices which have LogicalMaximum wrong in the keyboard
479 usage page of their report descriptor. The most prevailing ones so far
480 are manufactured by Ortek, thus the name of the driver. Currently
481 supported devices by this driver are
485 - Skycable wireless presenter
487 config HID_PANTHERLORD
488 tristate "Pantherlord/GreenAsia game controller"
491 Say Y here if you have a PantherLord/GreenAsia based game controller
494 config PANTHERLORD_FF
495 bool "Pantherlord force feedback support"
496 depends on HID_PANTHERLORD
497 select INPUT_FF_MEMLESS
499 Say Y here if you have a PantherLord/GreenAsia based game controller
500 or adapter and want to enable force feedback support for it.
503 tristate "Petalynx Maxter remote control"
506 Support for Petalynx Maxter remote control.
509 tristate "PicoLCD (graphic version)"
512 This provides support for Minibox PicoLCD devices, currently
513 only the graphical ones are supported.
515 This includes support for the following device features:
517 - Switching between Firmware and Flash mode
518 - EEProm / Flash access (via debugfs)
519 Features selectively enabled:
520 - Framebuffer for monochrome 256x64 display
523 - General purpose outputs
524 Features that are not (yet) supported:
527 config HID_PICOLCD_FB
528 bool "Framebuffer support" if EXPERT
530 depends on HID_PICOLCD
531 depends on HID_PICOLCD=FB || FB=y
532 select FB_DEFERRED_IO
533 select FB_SYS_FILLRECT
534 select FB_SYS_COPYAREA
535 select FB_SYS_IMAGEBLIT
538 Provide access to PicoLCD's 256x64 monochrome display via a
541 config HID_PICOLCD_BACKLIGHT
542 bool "Backlight control" if EXPERT
544 depends on HID_PICOLCD
545 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
547 Provide access to PicoLCD's backlight control via backlight
550 config HID_PICOLCD_LCD
551 bool "Contrast control" if EXPERT
553 depends on HID_PICOLCD
554 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
556 Provide access to PicoLCD's LCD contrast via lcd class.
558 config HID_PICOLCD_LEDS
559 bool "GPO via leds class" if EXPERT
561 depends on HID_PICOLCD
562 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
564 Provide access to PicoLCD's GPO pins via leds class.
566 config HID_PICOLCD_CIR
567 bool "CIR via RC class" if EXPERT
569 depends on HID_PICOLCD
570 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
572 Provide access to PicoLCD's CIR interface via remote control (LIRC).
575 tristate "Primax non-fully HID-compliant devices"
578 Support for Primax devices that are not fully compliant with the
582 tristate "Roccat device support"
585 Support for Roccat devices.
586 Say Y here if you have a Roccat mouse or keyboard and want
587 support for its special functionalities.
590 tristate "Saitek non-fully HID-compliant devices"
593 Support for Saitek devices that are not fully compliant with the
596 Currently only supports the PS1000 controller.
599 tristate "Samsung InfraRed remote control or keyboards"
602 Support for Samsung InfraRed remote control or keyboards.
605 tristate "Sony PS2/3 accessories"
608 depends on LEDS_CLASS
612 * Sony PS3 6-axis controllers
614 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
615 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
618 tristate "Speedlink VAD Cezanne mouse support"
621 Support for Speedlink Vicious and Divine Cezanne mouse.
623 config HID_STEELSERIES
624 tristate "Steelseries SRW-S1 steering wheel support"
627 Support for Steelseries SRW-S1 steering wheel
630 tristate "Sunplus wireless desktop"
633 Support for Sunplus wireless desktop.
636 tristate "GreenAsia (Product ID 0x12) game controller support"
639 Say Y here if you have a GreenAsia (Product ID 0x12) based game
640 controller or adapter.
643 bool "GreenAsia (Product ID 0x12) force feedback support"
644 depends on HID_GREENASIA
645 select INPUT_FF_MEMLESS
647 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
648 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
649 and want to enable force feedback support for it.
651 config HID_HYPERV_MOUSE
652 tristate "Microsoft Hyper-V mouse driver"
655 Select this option to enable the Hyper-V mouse driver.
657 config HID_SMARTJOYPLUS
658 tristate "SmartJoy PLUS PS2/USB adapter support"
661 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
662 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
664 Note that DDR (Dance Dance Revolution) mode is not supported, nor
665 is pressure sensitive buttons on the pro models.
667 config SMARTJOYPLUS_FF
668 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
669 depends on HID_SMARTJOYPLUS
670 select INPUT_FF_MEMLESS
672 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
673 enable force feedback support for it.
676 tristate "TiVo Slide Bluetooth remote control support"
679 Say Y if you have a TiVo Slide Bluetooth remote control.
682 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
685 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
686 CLLRCMCE remote control.
689 tristate "ThingM blink(1) USB RGB LED"
691 depends on LEDS_CLASS
693 Support for the ThingM blink(1) USB RGB LED. This driver registers a
694 Linux LED class instance, plus additional sysfs attributes to control
695 RGB colors, fade time and playing. The device is exposed through hidraw
696 to access other functions.
698 config HID_THRUSTMASTER
699 tristate "ThrustMaster devices support"
702 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
703 a THRUSTMASTER Ferrari GT Rumble Wheel.
705 config THRUSTMASTER_FF
706 bool "ThrustMaster devices force feedback support"
707 depends on HID_THRUSTMASTER
708 select INPUT_FF_MEMLESS
710 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
711 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
712 Rumble Force or Force Feedback Wheel.
715 tristate "Wacom Bluetooth devices support"
717 depends on LEDS_CLASS
720 Support for Wacom Graphire Bluetooth and Intuos4 WL tablets.
723 tristate "Nintendo Wii / Wii U peripherals"
725 depends on LEDS_CLASS
727 select INPUT_FF_MEMLESS
729 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
730 devices are the Wii Remote and its extension devices, but also devices
731 based on the Wii Remote like the Wii U Pro Controller or the
734 Support for all official Nintendo extensions is available, however, 3rd
735 party extensions might not be supported. Please report these devices to:
736 http://github.com/dvdhrm/xwiimote/issues
738 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
739 the Wii U Gamepad) might be supported in the future. But currently
740 support is limited to Bluetooth based devices.
744 To compile this driver as a module, choose M here: the
745 module will be called hid-wiimote.
748 tristate "Xin-Mo non-fully compliant devices"
751 Support for Xin-Mo devices that are not fully compliant with the HID
752 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
753 if you have a Xin-Mo Dual Arcade controller.
756 tristate "Zeroplus based game controller support"
759 Say Y here if you have a Zeroplus based game controller.
762 bool "Zeroplus based game controller force feedback support"
763 depends on HID_ZEROPLUS
764 select INPUT_FF_MEMLESS
766 Say Y here if you have a Zeroplus based game controller and want
767 to have force feedback support for it.
770 tristate "Zydacron remote control support"
773 Support for Zydacron remote control.
775 config HID_SENSOR_HUB
776 tristate "HID Sensors framework support"
781 Support for HID Sensor framework. This creates a MFD instance
782 for a sensor hub and identifies all the sensors connected to it.
783 Each sensor is registered as a MFD cell, so that sensor specific
784 processing can be done in a separate driver. Each sensor
785 drivers can use the service provided by this driver to register
786 for events and handle data streams. Each sensor driver can format
787 data and present to user mode using input or IIO interface.
793 source "drivers/hid/usbhid/Kconfig"
795 source "drivers/hid/i2c-hid/Kconfig"