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"
34 This option adds support of reporting battery strength (for HID devices
35 that support this feature) through power_supply class so that userspace
36 tools, such as upower, can display it.
39 bool "/dev/hidraw raw HID device support"
42 Say Y here if you want to support HID devices (from the USB
43 specification standpoint) that aren't strictly user interface
44 devices, like monitor controls and Uninterruptable Power Supplies.
46 This module supports these devices separately using a separate
47 event interface on /dev/hidraw.
49 There is also a /dev/hiddev configuration option in the USB HID
50 configuration menu. In comparison to hiddev, this device does not process
51 the hid events at all (no parsing, no lookups). This lets applications
52 to work on raw hid events when they want to, and avoid using transport-specific
53 userspace libhid/libusb libraries.
58 tristate "User-space I/O driver support for HID subsystem"
62 Say Y here if you want to provide HID I/O Drivers from user-space.
63 This allows to write I/O drivers in user-space and feed the data from
64 the device into the kernel. The kernel parses the HID reports, loads the
65 corresponding HID Device Driver or provides input devices on top of your
68 This driver cannot be used to parse HID-reports in user-space and write
69 special HID-drivers. You should use hidraw for that.
70 Instead, this driver allows to write the transport-layer driver in
71 user-space like USB-HID and Bluetooth-HID do in kernel-space.
75 To compile this driver as a module, choose M here: the
76 module will be called uhid.
79 tristate "Generic HID driver"
83 Support for generic devices on the HID bus. This includes most
84 keyboards and mice, joysticks, tablets and digitizers.
86 To compile this driver as a module, choose M here: the module
87 will be called hid-generic.
91 menu "Special HID drivers"
95 tristate "A4 tech mice"
99 Support for A4 tech X5 and WOP-35 / Trust 450L mice.
102 tristate "ACRUX game controller support"
105 Say Y here if you want to enable support for ACRUX game controllers.
108 bool "ACRUX force feedback support"
110 select INPUT_FF_MEMLESS
112 Say Y here if you want to enable force feedback support for ACRUX
116 tristate "Apple {i,Power,Mac}Books"
120 Support for some Apple devices which less or more break
123 Say Y here if you want support for keyboards of Apple iBooks, PowerBooks,
124 MacBooks, MacBook Pros and Apple Aluminum.
127 tristate "Apple infrared receiver"
130 Support for Apple infrared remote control. All the Apple computers from
131 2005 onwards include such a port, except the unibody Macbook (2009),
132 and Mac Pros. This receiver is also used in the Apple TV set-top box
133 prior to the 2010 model.
135 Say Y here if you want support for Apple infrared remote control.
141 Support for Aureal Cy se W-01RN Remote Controller and other Aureal derived remotes.
144 tristate "Belkin Flip KVM and Wireless keyboard"
148 Support for Belkin Flip KVM and Wireless keyboard.
151 tristate "Betop Production Inc. force feedback support"
153 select INPUT_FF_MEMLESS
155 Say Y here if you want to enable force feedback support for devices by
156 BETOP Production Ltd.
157 Currently the following devices are known to be supported:
158 - BETOP 2185 PC & BFM MODE
161 tristate "Cherry Cymotion keyboard"
165 Support for Cherry Cymotion keyboard.
168 tristate "Chicony Tactical pad"
172 Support for Chicony Tactical pad.
175 tristate "Corsair devices"
176 depends on HID && USB && LEDS_CLASS
178 Support for Corsair devices that are not fully compliant with the
185 tristate "Prodikeys PC-MIDI Keyboard support"
186 depends on HID && SND
189 Support for Prodikeys PC-MIDI Keyboard device support.
190 Say Y here to enable support for this device.
191 - Prodikeys PC-MIDI keyboard.
192 The Prodikeys PC-MIDI acts as a USB Audio device, with one MIDI
193 input and one MIDI output. These MIDI jacks appear as
194 a sound "card" in the ALSA sound system.
195 Note: if you say N here, this device will still function as a basic
196 multimedia keyboard, but will lack support for the musical keyboard
197 and some additional multimedia keys.
200 tristate "CMedia CM6533 HID audio jack controls"
203 Support for CMedia CM6533 HID audio jack controls.
206 tristate "Silicon Labs CP2112 HID USB-to-SMBus Bridge support"
207 depends on USB_HID && I2C && GPIOLIB
209 Support for Silicon Labs CP2112 HID USB to SMBus Master Bridge.
210 This is a HID device driver which registers as an i2c adapter
211 and gpiochip to expose these functions of the CP2112. The
212 customizable USB descriptor fields are exposed as sysfs attributes.
215 tristate "Cypress mouse and barcode readers"
219 Support for cypress mouse and barcode readers.
221 config HID_DRAGONRISE
222 tristate "DragonRise Inc. game controller"
225 Say Y here if you have DragonRise Inc. game controllers.
226 These might be branded as:
228 - Media-tech MT1504 "Rogue"
230 - Defender Game Master
233 bool "DragonRise Inc. force feedback"
234 depends on HID_DRAGONRISE
235 select INPUT_FF_MEMLESS
237 Say Y here if you want to enable force feedback support for DragonRise Inc.
241 tristate "EMS Production Inc. force feedback support"
243 select INPUT_FF_MEMLESS
245 Say Y here if you want to enable force feedback support for devices by
247 Currently the following devices are known to be supported:
248 - Trio Linker Plus II
251 tristate "ELECOM BM084 bluetooth mouse"
254 Support for the ELECOM BM084 (bluetooth mouse).
257 tristate "ELO USB 4000/4500 touchscreen"
260 Support for the ELO USB 4000/4500 touchscreens. Note that this is for
261 different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
264 tristate "Ezkey BTC 8193 keyboard"
268 Support for Ezkey BTC 8193 keyboard.
271 tristate "Gembird Joypad"
274 Support for Gembird JPD-DualForce 2.
277 tristate "Google Fiber TV Box remote control support"
280 Support for Google Fiber TV Box remote controls
283 tristate "Holtek HID devices"
286 Support for Holtek based devices:
287 - Holtek On Line Grip based game controller
288 - Trust GXT 18 Gaming Keyboard
289 - Sharkoon Drakonia / Perixx MX-2000 gaming mice
290 - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
292 - SHARKOON DarkGlider Gaming mouse
293 - LEETGION Hellion Gaming Mouse
296 bool "Holtek On Line Grip force feedback support"
297 depends on HID_HOLTEK
298 select INPUT_FF_MEMLESS
300 Say Y here if you have a Holtek On Line Grip based game controller
301 and want to have force feedback support for it.
304 tristate "MSI GT68xR LED support"
305 depends on LEDS_CLASS && USB_HID
307 Say Y here if you want to enable support for the three MSI GT68xR LEDs
309 This driver support following modes:
310 - Normal: LEDs are fully on when enabled
311 - Audio: LEDs brightness depends on sound level
312 - Breathing: LEDs brightness varies at human breathing rate
314 Currently the following devices are know to be supported:
318 tristate "Keytouch HID devices"
321 Support for Keytouch HID devices not fully compliant with
322 the specification. Currently supported:
326 tristate "KYE/Genius devices"
329 Support for KYE/Genius devices not fully compliant with HID standard:
331 - EasyPen i405X tablet
332 - MousePen i608X tablet
333 - EasyPen M610X tablet
339 Support for UC-Logic and Huion tablets.
345 Support for Waltop tablets.
348 tristate "Gyration remote control"
351 Support for Gyration remote control.
354 tristate "ION iCade arcade controller"
357 Support for the ION iCade arcade controller to work as a joystick.
359 To compile this driver as a module, choose M here: the
360 module will be called hid-icade.
363 tristate "Twinhan IR remote control"
366 Support for Twinhan IR remote control.
368 config HID_KENSINGTON
369 tristate "Kensington Slimblade Trackball"
373 Support for Kensington Slimblade Trackball.
379 Support for LC-Power RC1000MCE RF remote control.
382 tristate "Lenovo / Thinkpad devices"
387 Support for Lenovo devices that are not fully compliant with HID standard.
389 Say Y if you want support for the non-compliant features of the Lenovo
390 Thinkpad standalone keyboards, e.g:
391 - ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
393 - ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
394 - ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
397 tristate "Logitech devices"
401 Support for Logitech devices that are not fully compliant with HID standard.
403 config HID_LOGITECH_DJ
404 tristate "Logitech Unifying receivers full support"
406 depends on HID_LOGITECH
407 select HID_LOGITECH_HIDPP
409 Say Y if you want support for Logitech Unifying receivers and devices.
410 Unifying receivers are capable of pairing up to 6 Logitech compliant
411 devices to the same receiver. Without this driver it will be handled by
412 generic USB_HID driver and all incoming events will be multiplexed
413 into a single mouse and a single keyboard device.
415 config HID_LOGITECH_HIDPP
416 tristate "Logitech HID++ devices support"
417 depends on HID_LOGITECH
419 Support for Logitech devices relyingon the HID++ Logitech specification
421 Say Y if you want support for Logitech devices relying on the HID++
422 specification. Such devices are the various Logitech Touchpads (T650,
423 T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
427 bool "Logitech force feedback support"
428 depends on HID_LOGITECH
429 select INPUT_FF_MEMLESS
431 Say Y here if you have one of these devices:
432 - Logitech WingMan Cordless RumblePad
433 - Logitech WingMan Cordless RumblePad 2
434 - Logitech WingMan Force 3D
435 - Logitech Formula Force EX
436 - Logitech WingMan Formula Force GP
438 and if you want to enable force feedback for them.
439 Note: if you say N here, this device will still be supported, but without
442 config LOGIRUMBLEPAD2_FF
443 bool "Logitech force feedback support (variant 2)"
444 depends on HID_LOGITECH
445 select INPUT_FF_MEMLESS
447 Say Y here if you want to enable force feedback support for:
449 - Logitech Rumblepad 2
450 - Logitech Formula Vibration Feedback Wheel
453 bool "Logitech Flight System G940 force feedback support"
454 depends on HID_LOGITECH
455 select INPUT_FF_MEMLESS
457 Say Y here if you want to enable force feedback support for Logitech
458 Flight System G940 devices.
461 bool "Logitech wheels configuration and force feedback support"
462 depends on HID_LOGITECH
463 select INPUT_FF_MEMLESS
466 Say Y here if you want to enable force feedback and range setting
467 support for following Logitech wheels:
468 - Logitech Driving Force
469 - Logitech Driving Force Pro
470 - Logitech Driving Force GT
473 - Logitech MOMO/MOMO 2
474 - Logitech Formula Force EX
476 config HID_MAGICMOUSE
477 tristate "Apple Magic Mouse/Trackpad multi-touch support"
480 Support for the Apple Magic Mouse/Trackpad multi-touch.
482 Say Y here if you want support for the multi-touch features of the
483 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
486 tristate "Microsoft non-fully HID-compliant devices"
490 Support for Microsoft devices that are not fully compliant with HID standard.
493 tristate "Monterey Genius KB29E keyboard"
497 Support for Monterey Genius KB29E.
499 config HID_MULTITOUCH
500 tristate "HID Multitouch panels"
503 Generic support for HID multitouch panels.
505 Say Y here if you have one of the following devices:
506 - 3M PCT touch screens
507 - ActionStar dual touch panels
509 - Cando dual touch panels
513 - Cypress TrueTouch panels
514 - Elan Microelectronics touch panels
515 - Elo TouchSystems IntelliTouch Plus panels
516 - GeneralTouch 'Sensing Win7-TwoFinger' panels
518 - Hanvon dual touch panels
519 - Ilitek dual touch panels
520 - IrTouch Infrared USB panels
521 - LG Display panels (Dell ST2220Tc)
522 - Lumio CrystalTouch panels
523 - MosArt dual-touch panels
524 - Panasonic multitouch panels
525 - PenMount dual touch panels
526 - Perixx Peripad 701 touchpad
527 - PixArt optical touch screen
528 - Pixcir dual touch panels
530 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
531 - SiS multitouch panels
532 - Stantum multitouch panels
533 - Touch International Panels
535 - Wistron optical touch panels
536 - XAT optical touch panels
537 - Xiroku optical touch panels
538 - Zytronic touch panels
542 To compile this driver as a module, choose M here: the
543 module will be called hid-multitouch.
546 tristate "N-Trig touch screen"
549 Support for N-Trig touch screen.
552 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
555 There are certain devices which have LogicalMaximum wrong in the keyboard
556 usage page of their report descriptor. The most prevailing ones so far
557 are manufactured by Ortek, thus the name of the driver. Currently
558 supported devices by this driver are
562 - Skycable wireless presenter
564 config HID_PANTHERLORD
565 tristate "Pantherlord/GreenAsia game controller"
568 Say Y here if you have a PantherLord/GreenAsia based game controller
571 config PANTHERLORD_FF
572 bool "Pantherlord force feedback support"
573 depends on HID_PANTHERLORD
574 select INPUT_FF_MEMLESS
576 Say Y here if you have a PantherLord/GreenAsia based game controller
577 or adapter and want to enable force feedback support for it.
580 tristate "Penmount touch device"
583 This selects a driver for the PenMount 6000 touch controller.
585 The driver works around a problem in the report descript allowing
586 the userspace to touch events instead of mouse events.
588 Say Y here if you have a Penmount based touch controller.
591 tristate "Petalynx Maxter remote control"
594 Support for Petalynx Maxter remote control.
597 tristate "PicoLCD (graphic version)"
600 This provides support for Minibox PicoLCD devices, currently
601 only the graphical ones are supported.
603 This includes support for the following device features:
605 - Switching between Firmware and Flash mode
606 - EEProm / Flash access (via debugfs)
607 Features selectively enabled:
608 - Framebuffer for monochrome 256x64 display
611 - General purpose outputs
612 Features that are not (yet) supported:
615 config HID_PICOLCD_FB
616 bool "Framebuffer support" if EXPERT
618 depends on HID_PICOLCD
619 depends on HID_PICOLCD=FB || FB=y
620 select FB_DEFERRED_IO
621 select FB_SYS_FILLRECT
622 select FB_SYS_COPYAREA
623 select FB_SYS_IMAGEBLIT
626 Provide access to PicoLCD's 256x64 monochrome display via a
629 config HID_PICOLCD_BACKLIGHT
630 bool "Backlight control" if EXPERT
632 depends on HID_PICOLCD
633 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
635 Provide access to PicoLCD's backlight control via backlight
638 config HID_PICOLCD_LCD
639 bool "Contrast control" if EXPERT
641 depends on HID_PICOLCD
642 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
644 Provide access to PicoLCD's LCD contrast via lcd class.
646 config HID_PICOLCD_LEDS
647 bool "GPO via leds class" if EXPERT
649 depends on HID_PICOLCD
650 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
652 Provide access to PicoLCD's GPO pins via leds class.
654 config HID_PICOLCD_CIR
655 bool "CIR via RC class" if EXPERT
657 depends on HID_PICOLCD
658 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
660 Provide access to PicoLCD's CIR interface via remote control (LIRC).
662 config HID_PLANTRONICS
663 tristate "Plantronics USB HID Driver"
666 Provides HID support for Plantronics USB audio devices.
667 Correctly maps vendor unique volume up/down HID usages to
668 KEY_VOLUMEUP and KEY_VOLUMEDOWN events and prevents core mapping
669 of other vendor unique HID usages to random mouse events.
671 Say M here if you may ever plug in a Plantronics USB audio device.
674 tristate "Primax non-fully HID-compliant devices"
677 Support for Primax devices that are not fully compliant with the
681 tristate "Roccat device support"
684 Support for Roccat devices.
685 Say Y here if you have a Roccat mouse or keyboard and want
686 support for its special functionalities.
689 tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
692 Support for Saitek devices that are not fully compliant with the
696 - PS1000 Dual Analog Pad
697 - Saitek R.A.T.7, R.A.T.9, M.M.O.7 Gaming Mice
698 - Mad Catz R.A.T.5, R.A.T.9 Gaming Mice
701 tristate "Samsung InfraRed remote control or keyboards"
704 Support for Samsung InfraRed remote control or keyboards.
707 tristate "Sony PS2/3/4 accessories"
710 depends on LEDS_CLASS
715 * Sony PS3 6-axis controllers
716 * Sony PS4 DualShock 4 controllers
718 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
719 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
722 bool "Sony PS2/3/4 accessories force feedback support"
724 select INPUT_FF_MEMLESS
726 Say Y here if you have a Sony PS2/3/4 accessory and want to enable
727 force feedback support for it.
730 tristate "Speedlink VAD Cezanne mouse support"
733 Support for Speedlink Vicious and Divine Cezanne mouse.
735 config HID_STEELSERIES
736 tristate "Steelseries SRW-S1 steering wheel support"
739 Support for Steelseries SRW-S1 steering wheel
742 tristate "Sunplus wireless desktop"
745 Support for Sunplus wireless desktop.
748 tristate "Synaptics RMI4 device support"
751 Support for Synaptics RMI4 touchpads.
752 Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
753 and want support for its special functionalities.
756 tristate "GreenAsia (Product ID 0x12) game controller support"
759 Say Y here if you have a GreenAsia (Product ID 0x12) based game
760 controller or adapter.
763 bool "GreenAsia (Product ID 0x12) force feedback support"
764 depends on HID_GREENASIA
765 select INPUT_FF_MEMLESS
767 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
768 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
769 and want to enable force feedback support for it.
771 config HID_HYPERV_MOUSE
772 tristate "Microsoft Hyper-V mouse driver"
775 Select this option to enable the Hyper-V mouse driver.
777 config HID_SMARTJOYPLUS
778 tristate "SmartJoy PLUS PS2/USB adapter support"
781 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
782 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
784 Note that DDR (Dance Dance Revolution) mode is not supported, nor
785 is pressure sensitive buttons on the pro models.
787 config SMARTJOYPLUS_FF
788 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
789 depends on HID_SMARTJOYPLUS
790 select INPUT_FF_MEMLESS
792 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
793 enable force feedback support for it.
796 tristate "TiVo Slide Bluetooth remote control support"
799 Say Y if you have a TiVo Slide Bluetooth remote control.
802 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
805 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
806 CLLRCMCE remote control.
809 tristate "ThingM blink(1) USB RGB LED"
811 depends on LEDS_CLASS
813 Support for the ThingM blink(1) USB RGB LED. This driver registers a
814 Linux LED class instance, plus additional sysfs attributes to control
815 RGB colors, fade time and playing. The device is exposed through hidraw
816 to access other functions.
818 config HID_THRUSTMASTER
819 tristate "ThrustMaster devices support"
822 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
823 a THRUSTMASTER Ferrari GT Rumble Wheel.
825 config THRUSTMASTER_FF
826 bool "ThrustMaster devices force feedback support"
827 depends on HID_THRUSTMASTER
828 select INPUT_FF_MEMLESS
830 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
831 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
832 Rumble Force or Force Feedback Wheel.
835 tristate "Wacom Intuos/Graphire tablet support (USB)"
841 Say Y here if you want to use the USB or BT version of the Wacom Intuos
844 To compile this driver as a module, choose M here: the
845 module will be called wacom.
848 tristate "Nintendo Wii / Wii U peripherals"
850 depends on LEDS_CLASS
852 select INPUT_FF_MEMLESS
854 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
855 devices are the Wii Remote and its extension devices, but also devices
856 based on the Wii Remote like the Wii U Pro Controller or the
859 Support for all official Nintendo extensions is available, however, 3rd
860 party extensions might not be supported. Please report these devices to:
861 http://github.com/dvdhrm/xwiimote/issues
863 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
864 the Wii U Gamepad) might be supported in the future. But currently
865 support is limited to Bluetooth based devices.
869 To compile this driver as a module, choose M here: the
870 module will be called hid-wiimote.
873 tristate "Xin-Mo non-fully compliant devices"
876 Support for Xin-Mo devices that are not fully compliant with the HID
877 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
878 if you have a Xin-Mo Dual Arcade controller.
881 tristate "Zeroplus based game controller support"
884 Say Y here if you have a Zeroplus based game controller.
887 bool "Zeroplus based game controller force feedback support"
888 depends on HID_ZEROPLUS
889 select INPUT_FF_MEMLESS
891 Say Y here if you have a Zeroplus based game controller and want
892 to have force feedback support for it.
895 tristate "Zydacron remote control support"
898 Support for Zydacron remote control.
900 config HID_SENSOR_HUB
901 tristate "HID Sensors framework support"
902 depends on HID && HAS_IOMEM
906 Support for HID Sensor framework. This creates a MFD instance
907 for a sensor hub and identifies all the sensors connected to it.
908 Each sensor is registered as a MFD cell, so that sensor specific
909 processing can be done in a separate driver. Each sensor
910 drivers can use the service provided by this driver to register
911 for events and handle data streams. Each sensor driver can format
912 data and present to user mode using input or IIO interface.
914 config HID_SENSOR_CUSTOM_SENSOR
915 tristate "HID Sensors hub custom sensor support"
916 depends on HID_SENSOR_HUB
919 HID Sensor hub specification allows definition of some custom and
920 generic sensors. Unlike other HID sensors, they can't be exported
921 via Linux IIO because of custom fields. This is up to the manufacturer
922 to decide how to interpret these special sensor ids and process in
923 the user space. Currently some manufacturers are using these ids for
924 sensor calibration and debugging other sensors. Manufacturers
925 should't use these special custom sensor ids to export any of the
927 Select this config option for custom/generic sensor support.
933 source "drivers/hid/usbhid/Kconfig"
935 source "drivers/hid/i2c-hid/Kconfig"