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 "Silicon Labs CP2112 HID USB-to-SMBus Bridge support"
201 depends on USB_HID && I2C && GPIOLIB
203 Support for Silicon Labs CP2112 HID USB to SMBus Master Bridge.
204 This is a HID device driver which registers as an i2c adapter
205 and gpiochip to expose these functions of the CP2112. The
206 customizable USB descriptor fields are exposed as sysfs attributes.
209 tristate "Cypress mouse and barcode readers"
213 Support for cypress mouse and barcode readers.
215 config HID_DRAGONRISE
216 tristate "DragonRise Inc. game controller"
219 Say Y here if you have DragonRise Inc. game controllers.
220 These might be branded as:
222 - Media-tech MT1504 "Rogue"
224 - Defender Game Master
227 bool "DragonRise Inc. force feedback"
228 depends on HID_DRAGONRISE
229 select INPUT_FF_MEMLESS
231 Say Y here if you want to enable force feedback support for DragonRise Inc.
235 tristate "EMS Production Inc. force feedback support"
237 select INPUT_FF_MEMLESS
239 Say Y here if you want to enable force feedback support for devices by
241 Currently the following devices are known to be supported:
242 - Trio Linker Plus II
245 tristate "ELECOM BM084 bluetooth mouse"
248 Support for the ELECOM BM084 (bluetooth mouse).
251 tristate "ELO USB 4000/4500 touchscreen"
254 Support for the ELO USB 4000/4500 touchscreens. Note that this is for
255 different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
258 tristate "Ezkey BTC 8193 keyboard"
262 Support for Ezkey BTC 8193 keyboard.
265 tristate "Gembird Joypad"
268 Support for Gembird JPD-DualForce 2.
271 tristate "Holtek HID devices"
274 Support for Holtek based devices:
275 - Holtek On Line Grip based game controller
276 - Trust GXT 18 Gaming Keyboard
277 - Sharkoon Drakonia / Perixx MX-2000 gaming mice
278 - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
280 - SHARKOON DarkGlider Gaming mouse
281 - LEETGION Hellion Gaming Mouse
284 bool "Holtek On Line Grip force feedback support"
285 depends on HID_HOLTEK
286 select INPUT_FF_MEMLESS
288 Say Y here if you have a Holtek On Line Grip based game controller
289 and want to have force feedback support for it.
292 tristate "MSI GT68xR LED support"
293 depends on LEDS_CLASS && USB_HID
295 Say Y here if you want to enable support for the three MSI GT68xR LEDs
297 This driver support following modes:
298 - Normal: LEDs are fully on when enabled
299 - Audio: LEDs brightness depends on sound level
300 - Breathing: LEDs brightness varies at human breathing rate
302 Currently the following devices are know to be supported:
306 tristate "Keytouch HID devices"
309 Support for Keytouch HID devices not fully compliant with
310 the specification. Currently supported:
314 tristate "KYE/Genius devices"
317 Support for KYE/Genius devices not fully compliant with HID standard:
319 - EasyPen i405X tablet
320 - MousePen i608X tablet
321 - EasyPen M610X tablet
327 Support for UC-Logic and Huion tablets.
333 Support for Waltop tablets.
336 tristate "Gyration remote control"
339 Support for Gyration remote control.
342 tristate "ION iCade arcade controller"
345 Support for the ION iCade arcade controller to work as a joystick.
347 To compile this driver as a module, choose M here: the
348 module will be called hid-icade.
351 tristate "Twinhan IR remote control"
354 Support for Twinhan IR remote control.
356 config HID_KENSINGTON
357 tristate "Kensington Slimblade Trackball"
361 Support for Kensington Slimblade Trackball.
367 Support for LC-Power RC1000MCE RF remote control.
370 tristate "Lenovo / Thinkpad devices"
375 Support for Lenovo devices that are not fully compliant with HID standard.
377 Say Y if you want support for the non-compliant features of the Lenovo
378 Thinkpad standalone keyboards, e.g:
379 - ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
381 - ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
382 - ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
385 tristate "Logitech devices"
389 Support for Logitech devices that are not fully compliant with HID standard.
391 config HID_LOGITECH_DJ
392 tristate "Logitech Unifying receivers full support"
394 depends on HID_LOGITECH
395 select HID_LOGITECH_HIDPP
397 Say Y if you want support for Logitech Unifying receivers and devices.
398 Unifying receivers are capable of pairing up to 6 Logitech compliant
399 devices to the same receiver. Without this driver it will be handled by
400 generic USB_HID driver and all incoming events will be multiplexed
401 into a single mouse and a single keyboard device.
403 config HID_LOGITECH_HIDPP
404 tristate "Logitech HID++ devices support"
405 depends on HID_LOGITECH
407 Support for Logitech devices relyingon the HID++ Logitech specification
409 Say Y if you want support for Logitech devices relying on the HID++
410 specification. Such devices are the various Logitech Touchpads (T650,
411 T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
415 bool "Logitech force feedback support"
416 depends on HID_LOGITECH
417 select INPUT_FF_MEMLESS
419 Say Y here if you have one of these devices:
420 - Logitech WingMan Cordless RumblePad
421 - Logitech WingMan Cordless RumblePad 2
422 - Logitech WingMan Force 3D
423 - Logitech Formula Force EX
424 - Logitech WingMan Formula Force GP
426 and if you want to enable force feedback for them.
427 Note: if you say N here, this device will still be supported, but without
430 config LOGIRUMBLEPAD2_FF
431 bool "Logitech force feedback support (variant 2)"
432 depends on HID_LOGITECH
433 select INPUT_FF_MEMLESS
435 Say Y here if you want to enable force feedback support for:
437 - Logitech Rumblepad 2
438 - Logitech Formula Vibration Feedback Wheel
441 bool "Logitech Flight System G940 force feedback support"
442 depends on HID_LOGITECH
443 select INPUT_FF_MEMLESS
445 Say Y here if you want to enable force feedback support for Logitech
446 Flight System G940 devices.
449 bool "Logitech wheels configuration and force feedback support"
450 depends on HID_LOGITECH
451 select INPUT_FF_MEMLESS
454 Say Y here if you want to enable force feedback and range setting
455 support for following Logitech wheels:
456 - Logitech Driving Force
457 - Logitech Driving Force Pro
458 - Logitech Driving Force GT
461 - Logitech MOMO/MOMO 2
462 - Logitech Formula Force EX
464 config HID_MAGICMOUSE
465 tristate "Apple Magic Mouse/Trackpad multi-touch support"
468 Support for the Apple Magic Mouse/Trackpad multi-touch.
470 Say Y here if you want support for the multi-touch features of the
471 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
474 tristate "Microsoft non-fully HID-compliant devices"
478 Support for Microsoft devices that are not fully compliant with HID standard.
481 tristate "Monterey Genius KB29E keyboard"
485 Support for Monterey Genius KB29E.
487 config HID_MULTITOUCH
488 tristate "HID Multitouch panels"
491 Generic support for HID multitouch panels.
493 Say Y here if you have one of the following devices:
494 - 3M PCT touch screens
495 - ActionStar dual touch panels
497 - Cando dual touch panels
501 - Cypress TrueTouch panels
502 - Elan Microelectronics touch panels
503 - Elo TouchSystems IntelliTouch Plus panels
504 - GeneralTouch 'Sensing Win7-TwoFinger' panels
506 - Hanvon dual touch panels
507 - Ilitek dual touch panels
508 - IrTouch Infrared USB panels
509 - LG Display panels (Dell ST2220Tc)
510 - Lumio CrystalTouch panels
511 - MosArt dual-touch panels
512 - Panasonic multitouch panels
513 - PenMount dual touch panels
514 - Perixx Peripad 701 touchpad
515 - PixArt optical touch screen
516 - Pixcir dual touch panels
518 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
519 - SiS multitouch panels
520 - Stantum multitouch panels
521 - Touch International Panels
523 - Wistron optical touch panels
524 - XAT optical touch panels
525 - Xiroku optical touch panels
526 - Zytronic touch panels
530 To compile this driver as a module, choose M here: the
531 module will be called hid-multitouch.
534 tristate "N-Trig touch screen"
537 Support for N-Trig touch screen.
540 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
543 There are certain devices which have LogicalMaximum wrong in the keyboard
544 usage page of their report descriptor. The most prevailing ones so far
545 are manufactured by Ortek, thus the name of the driver. Currently
546 supported devices by this driver are
550 - Skycable wireless presenter
552 config HID_PANTHERLORD
553 tristate "Pantherlord/GreenAsia game controller"
556 Say Y here if you have a PantherLord/GreenAsia based game controller
559 config PANTHERLORD_FF
560 bool "Pantherlord force feedback support"
561 depends on HID_PANTHERLORD
562 select INPUT_FF_MEMLESS
564 Say Y here if you have a PantherLord/GreenAsia based game controller
565 or adapter and want to enable force feedback support for it.
568 tristate "Penmount touch device"
571 This selects a driver for the PenMount 6000 touch controller.
573 The driver works around a problem in the report descript allowing
574 the userspace to touch events instead of mouse events.
576 Say Y here if you have a Penmount based touch controller.
579 tristate "Petalynx Maxter remote control"
582 Support for Petalynx Maxter remote control.
585 tristate "PicoLCD (graphic version)"
588 This provides support for Minibox PicoLCD devices, currently
589 only the graphical ones are supported.
591 This includes support for the following device features:
593 - Switching between Firmware and Flash mode
594 - EEProm / Flash access (via debugfs)
595 Features selectively enabled:
596 - Framebuffer for monochrome 256x64 display
599 - General purpose outputs
600 Features that are not (yet) supported:
603 config HID_PICOLCD_FB
604 bool "Framebuffer support" if EXPERT
606 depends on HID_PICOLCD
607 depends on HID_PICOLCD=FB || FB=y
608 select FB_DEFERRED_IO
609 select FB_SYS_FILLRECT
610 select FB_SYS_COPYAREA
611 select FB_SYS_IMAGEBLIT
614 Provide access to PicoLCD's 256x64 monochrome display via a
617 config HID_PICOLCD_BACKLIGHT
618 bool "Backlight control" if EXPERT
620 depends on HID_PICOLCD
621 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
623 Provide access to PicoLCD's backlight control via backlight
626 config HID_PICOLCD_LCD
627 bool "Contrast control" if EXPERT
629 depends on HID_PICOLCD
630 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
632 Provide access to PicoLCD's LCD contrast via lcd class.
634 config HID_PICOLCD_LEDS
635 bool "GPO via leds class" if EXPERT
637 depends on HID_PICOLCD
638 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
640 Provide access to PicoLCD's GPO pins via leds class.
642 config HID_PICOLCD_CIR
643 bool "CIR via RC class" if EXPERT
645 depends on HID_PICOLCD
646 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
648 Provide access to PicoLCD's CIR interface via remote control (LIRC).
650 config HID_PLANTRONICS
651 tristate "Plantronics USB HID Driver"
654 Provides HID support for Plantronics USB audio devices.
655 Correctly maps vendor unique volume up/down HID usages to
656 KEY_VOLUMEUP and KEY_VOLUMEDOWN events and prevents core mapping
657 of other vendor unique HID usages to random mouse events.
659 Say M here if you may ever plug in a Plantronics USB audio device.
662 tristate "Primax non-fully HID-compliant devices"
665 Support for Primax devices that are not fully compliant with the
669 tristate "Roccat device support"
672 Support for Roccat devices.
673 Say Y here if you have a Roccat mouse or keyboard and want
674 support for its special functionalities.
677 tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
680 Support for Saitek devices that are not fully compliant with the
684 - PS1000 Dual Analog Pad
685 - Saitek R.A.T.7, R.A.T.9, M.M.O.7 Gaming Mice
686 - Mad Catz R.A.T.5, R.A.T.9 Gaming Mice
689 tristate "Samsung InfraRed remote control or keyboards"
692 Support for Samsung InfraRed remote control or keyboards.
695 tristate "Sony PS2/3/4 accessories"
698 depends on LEDS_CLASS
703 * Sony PS3 6-axis controllers
704 * Sony PS4 DualShock 4 controllers
706 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
707 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
710 bool "Sony PS2/3/4 accessories force feedback support"
712 select INPUT_FF_MEMLESS
714 Say Y here if you have a Sony PS2/3/4 accessory and want to enable
715 force feedback support for it.
718 tristate "Speedlink VAD Cezanne mouse support"
721 Support for Speedlink Vicious and Divine Cezanne mouse.
723 config HID_STEELSERIES
724 tristate "Steelseries SRW-S1 steering wheel support"
727 Support for Steelseries SRW-S1 steering wheel
730 tristate "Sunplus wireless desktop"
733 Support for Sunplus wireless desktop.
736 tristate "Synaptics RMI4 device support"
739 Support for Synaptics RMI4 touchpads.
740 Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
741 and want support for its special functionalities.
744 tristate "GreenAsia (Product ID 0x12) game controller support"
747 Say Y here if you have a GreenAsia (Product ID 0x12) based game
748 controller or adapter.
751 bool "GreenAsia (Product ID 0x12) force feedback support"
752 depends on HID_GREENASIA
753 select INPUT_FF_MEMLESS
755 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
756 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
757 and want to enable force feedback support for it.
759 config HID_HYPERV_MOUSE
760 tristate "Microsoft Hyper-V mouse driver"
763 Select this option to enable the Hyper-V mouse driver.
765 config HID_SMARTJOYPLUS
766 tristate "SmartJoy PLUS PS2/USB adapter support"
769 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
770 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
772 Note that DDR (Dance Dance Revolution) mode is not supported, nor
773 is pressure sensitive buttons on the pro models.
775 config SMARTJOYPLUS_FF
776 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
777 depends on HID_SMARTJOYPLUS
778 select INPUT_FF_MEMLESS
780 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
781 enable force feedback support for it.
784 tristate "TiVo Slide Bluetooth remote control support"
787 Say Y if you have a TiVo Slide Bluetooth remote control.
790 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
793 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
794 CLLRCMCE remote control.
797 tristate "ThingM blink(1) USB RGB LED"
799 depends on LEDS_CLASS
801 Support for the ThingM blink(1) USB RGB LED. This driver registers a
802 Linux LED class instance, plus additional sysfs attributes to control
803 RGB colors, fade time and playing. The device is exposed through hidraw
804 to access other functions.
806 config HID_THRUSTMASTER
807 tristate "ThrustMaster devices support"
810 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
811 a THRUSTMASTER Ferrari GT Rumble Wheel.
813 config THRUSTMASTER_FF
814 bool "ThrustMaster devices force feedback support"
815 depends on HID_THRUSTMASTER
816 select INPUT_FF_MEMLESS
818 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
819 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
820 Rumble Force or Force Feedback Wheel.
823 tristate "Wacom Intuos/Graphire tablet support (USB)"
829 Say Y here if you want to use the USB or BT version of the Wacom Intuos
832 To compile this driver as a module, choose M here: the
833 module will be called wacom.
836 tristate "Nintendo Wii / Wii U peripherals"
838 depends on LEDS_CLASS
840 select INPUT_FF_MEMLESS
842 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
843 devices are the Wii Remote and its extension devices, but also devices
844 based on the Wii Remote like the Wii U Pro Controller or the
847 Support for all official Nintendo extensions is available, however, 3rd
848 party extensions might not be supported. Please report these devices to:
849 http://github.com/dvdhrm/xwiimote/issues
851 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
852 the Wii U Gamepad) might be supported in the future. But currently
853 support is limited to Bluetooth based devices.
857 To compile this driver as a module, choose M here: the
858 module will be called hid-wiimote.
861 tristate "Xin-Mo non-fully compliant devices"
864 Support for Xin-Mo devices that are not fully compliant with the HID
865 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
866 if you have a Xin-Mo Dual Arcade controller.
869 tristate "Zeroplus based game controller support"
872 Say Y here if you have a Zeroplus based game controller.
875 bool "Zeroplus based game controller force feedback support"
876 depends on HID_ZEROPLUS
877 select INPUT_FF_MEMLESS
879 Say Y here if you have a Zeroplus based game controller and want
880 to have force feedback support for it.
883 tristate "Zydacron remote control support"
886 Support for Zydacron remote control.
888 config HID_SENSOR_HUB
889 tristate "HID Sensors framework support"
890 depends on HID && HAS_IOMEM
894 Support for HID Sensor framework. This creates a MFD instance
895 for a sensor hub and identifies all the sensors connected to it.
896 Each sensor is registered as a MFD cell, so that sensor specific
897 processing can be done in a separate driver. Each sensor
898 drivers can use the service provided by this driver to register
899 for events and handle data streams. Each sensor driver can format
900 data and present to user mode using input or IIO interface.
902 config HID_SENSOR_CUSTOM_SENSOR
903 tristate "HID Sensors hub custom sensor support"
904 depends on HID_SENSOR_HUB
907 HID Sensor hub specification allows definition of some custom and
908 generic sensors. Unlike other HID sensors, they can't be exported
909 via Linux IIO because of custom fields. This is up to the manufacturer
910 to decide how to interpret these special sensor ids and process in
911 the user space. Currently some manufacturers are using these ids for
912 sensor calibration and debugging other sensors. Manufacturers
913 should't use these special custom sensor ids to export any of the
915 Select this config option for custom/generic sensor support.
921 source "drivers/hid/usbhid/Kconfig"
923 source "drivers/hid/i2c-hid/Kconfig"