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 "Prodikeys PC-MIDI Keyboard support"
176 depends on HID && SND
179 Support for Prodikeys PC-MIDI Keyboard device support.
180 Say Y here to enable support for this device.
181 - Prodikeys PC-MIDI keyboard.
182 The Prodikeys PC-MIDI acts as a USB Audio device, with one MIDI
183 input and one MIDI output. These MIDI jacks appear as
184 a sound "card" in the ALSA sound system.
185 Note: if you say N here, this device will still function as a basic
186 multimedia keyboard, but will lack support for the musical keyboard
187 and some additional multimedia keys.
190 tristate "Silicon Labs CP2112 HID USB-to-SMBus Bridge support"
191 depends on USB_HID && I2C && GPIOLIB
193 Support for Silicon Labs CP2112 HID USB to SMBus Master Bridge.
194 This is a HID device driver which registers as an i2c adapter
195 and gpiochip to expose these functions of the CP2112. The
196 customizable USB descriptor fields are exposed as sysfs attributes.
199 tristate "Cypress mouse and barcode readers"
203 Support for cypress mouse and barcode readers.
205 config HID_DRAGONRISE
206 tristate "DragonRise Inc. game controller"
209 Say Y here if you have DragonRise Inc. game controllers.
210 These might be branded as:
212 - Media-tech MT1504 "Rogue"
214 - Defender Game Master
217 bool "DragonRise Inc. force feedback"
218 depends on HID_DRAGONRISE
219 select INPUT_FF_MEMLESS
221 Say Y here if you want to enable force feedback support for DragonRise Inc.
225 tristate "EMS Production Inc. force feedback support"
227 select INPUT_FF_MEMLESS
229 Say Y here if you want to enable force feedback support for devices by
231 Currently the following devices are known to be supported:
232 - Trio Linker Plus II
235 tristate "ELECOM BM084 bluetooth mouse"
238 Support for the ELECOM BM084 (bluetooth mouse).
241 tristate "ELO USB 4000/4500 touchscreen"
244 Support for the ELO USB 4000/4500 touchscreens. Note that this is for
245 different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
248 tristate "Ezkey BTC 8193 keyboard"
252 Support for Ezkey BTC 8193 keyboard.
255 tristate "Gembird Joypad"
258 Support for Gembird JPD-DualForce 2.
261 tristate "Google Fiber TV Box remote control support"
264 Support for Google Fiber TV Box remote controls
267 tristate "Holtek HID devices"
270 Support for Holtek based devices:
271 - Holtek On Line Grip based game controller
272 - Trust GXT 18 Gaming Keyboard
273 - Sharkoon Drakonia / Perixx MX-2000 gaming mice
274 - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
276 - SHARKOON DarkGlider Gaming mouse
277 - LEETGION Hellion Gaming Mouse
280 bool "Holtek On Line Grip force feedback support"
281 depends on HID_HOLTEK
282 select INPUT_FF_MEMLESS
284 Say Y here if you have a Holtek On Line Grip based game controller
285 and want to have force feedback support for it.
288 tristate "MSI GT68xR LED support"
289 depends on LEDS_CLASS && USB_HID
291 Say Y here if you want to enable support for the three MSI GT68xR LEDs
293 This driver support following modes:
294 - Normal: LEDs are fully on when enabled
295 - Audio: LEDs brightness depends on sound level
296 - Breathing: LEDs brightness varies at human breathing rate
298 Currently the following devices are know to be supported:
302 tristate "Keytouch HID devices"
305 Support for Keytouch HID devices not fully compliant with
306 the specification. Currently supported:
310 tristate "KYE/Genius devices"
313 Support for KYE/Genius devices not fully compliant with HID standard:
315 - EasyPen i405X tablet
316 - MousePen i608X tablet
317 - EasyPen M610X tablet
323 Support for UC-Logic and Huion tablets.
329 Support for Waltop tablets.
332 tristate "Gyration remote control"
335 Support for Gyration remote control.
338 tristate "ION iCade arcade controller"
341 Support for the ION iCade arcade controller to work as a joystick.
343 To compile this driver as a module, choose M here: the
344 module will be called hid-icade.
347 tristate "Twinhan IR remote control"
350 Support for Twinhan IR remote control.
352 config HID_KENSINGTON
353 tristate "Kensington Slimblade Trackball"
357 Support for Kensington Slimblade Trackball.
363 Support for LC-Power RC1000MCE RF remote control.
366 tristate "Lenovo / Thinkpad devices"
371 Support for Lenovo devices that are not fully compliant with HID standard.
373 Say Y if you want support for the non-compliant features of the Lenovo
374 Thinkpad standalone keyboards, e.g:
375 - ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
377 - ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
378 - ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
381 tristate "Logitech devices"
385 Support for Logitech devices that are not fully compliant with HID standard.
387 config HID_LOGITECH_DJ
388 tristate "Logitech Unifying receivers full support"
390 depends on HID_LOGITECH
391 select HID_LOGITECH_HIDPP
393 Say Y if you want support for Logitech Unifying receivers and devices.
394 Unifying receivers are capable of pairing up to 6 Logitech compliant
395 devices to the same receiver. Without this driver it will be handled by
396 generic USB_HID driver and all incoming events will be multiplexed
397 into a single mouse and a single keyboard device.
399 config HID_LOGITECH_HIDPP
400 tristate "Logitech HID++ devices support"
401 depends on HID_LOGITECH
403 Support for Logitech devices relyingon the HID++ Logitech specification
405 Say Y if you want support for Logitech devices relying on the HID++
406 specification. Such devices are the various Logitech Touchpads (T650,
407 T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
411 bool "Logitech force feedback support"
412 depends on HID_LOGITECH
413 select INPUT_FF_MEMLESS
415 Say Y here if you have one of these devices:
416 - Logitech WingMan Cordless RumblePad
417 - Logitech WingMan Cordless RumblePad 2
418 - Logitech WingMan Force 3D
419 - Logitech Formula Force EX
420 - Logitech WingMan Formula Force GP
422 and if you want to enable force feedback for them.
423 Note: if you say N here, this device will still be supported, but without
426 config LOGIRUMBLEPAD2_FF
427 bool "Logitech force feedback support (variant 2)"
428 depends on HID_LOGITECH
429 select INPUT_FF_MEMLESS
431 Say Y here if you want to enable force feedback support for:
433 - Logitech Rumblepad 2
434 - Logitech Formula Vibration Feedback Wheel
437 bool "Logitech Flight System G940 force feedback support"
438 depends on HID_LOGITECH
439 select INPUT_FF_MEMLESS
441 Say Y here if you want to enable force feedback support for Logitech
442 Flight System G940 devices.
445 bool "Logitech wheels configuration and force feedback support"
446 depends on HID_LOGITECH
447 select INPUT_FF_MEMLESS
450 Say Y here if you want to enable force feedback and range setting
451 support for following Logitech wheels:
452 - Logitech Driving Force
453 - Logitech Driving Force Pro
454 - Logitech Driving Force GT
457 - Logitech MOMO/MOMO 2
458 - Logitech Formula Force EX
460 config HID_MAGICMOUSE
461 tristate "Apple Magic Mouse/Trackpad multi-touch support"
464 Support for the Apple Magic Mouse/Trackpad multi-touch.
466 Say Y here if you want support for the multi-touch features of the
467 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
470 tristate "Microsoft non-fully HID-compliant devices"
474 Support for Microsoft devices that are not fully compliant with HID standard.
477 tristate "Monterey Genius KB29E keyboard"
481 Support for Monterey Genius KB29E.
483 config HID_MULTITOUCH
484 tristate "HID Multitouch panels"
487 Generic support for HID multitouch panels.
489 Say Y here if you have one of the following devices:
490 - 3M PCT touch screens
491 - ActionStar dual touch panels
493 - Cando dual touch panels
497 - Cypress TrueTouch panels
498 - Elan Microelectronics touch panels
499 - Elo TouchSystems IntelliTouch Plus panels
500 - GeneralTouch 'Sensing Win7-TwoFinger' panels
502 - Hanvon dual touch panels
503 - Ilitek dual touch panels
504 - IrTouch Infrared USB panels
505 - LG Display panels (Dell ST2220Tc)
506 - Lumio CrystalTouch panels
507 - MosArt dual-touch panels
508 - Panasonic multitouch panels
509 - PenMount dual touch panels
510 - Perixx Peripad 701 touchpad
511 - PixArt optical touch screen
512 - Pixcir dual touch panels
514 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
515 - SiS multitouch panels
516 - Stantum multitouch panels
517 - Touch International Panels
519 - Wistron optical touch panels
520 - XAT optical touch panels
521 - Xiroku optical touch panels
522 - Zytronic touch panels
526 To compile this driver as a module, choose M here: the
527 module will be called hid-multitouch.
530 tristate "N-Trig touch screen"
533 Support for N-Trig touch screen.
536 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
539 There are certain devices which have LogicalMaximum wrong in the keyboard
540 usage page of their report descriptor. The most prevailing ones so far
541 are manufactured by Ortek, thus the name of the driver. Currently
542 supported devices by this driver are
546 - Skycable wireless presenter
548 config HID_PANTHERLORD
549 tristate "Pantherlord/GreenAsia game controller"
552 Say Y here if you have a PantherLord/GreenAsia based game controller
555 config PANTHERLORD_FF
556 bool "Pantherlord force feedback support"
557 depends on HID_PANTHERLORD
558 select INPUT_FF_MEMLESS
560 Say Y here if you have a PantherLord/GreenAsia based game controller
561 or adapter and want to enable force feedback support for it.
564 tristate "Penmount touch device"
567 This selects a driver for the PenMount 6000 touch controller.
569 The driver works around a problem in the report descript allowing
570 the userspace to touch events instead of mouse events.
572 Say Y here if you have a Penmount based touch controller.
575 tristate "Petalynx Maxter remote control"
578 Support for Petalynx Maxter remote control.
581 tristate "PicoLCD (graphic version)"
584 This provides support for Minibox PicoLCD devices, currently
585 only the graphical ones are supported.
587 This includes support for the following device features:
589 - Switching between Firmware and Flash mode
590 - EEProm / Flash access (via debugfs)
591 Features selectively enabled:
592 - Framebuffer for monochrome 256x64 display
595 - General purpose outputs
596 Features that are not (yet) supported:
599 config HID_PICOLCD_FB
600 bool "Framebuffer support" if EXPERT
602 depends on HID_PICOLCD
603 depends on HID_PICOLCD=FB || FB=y
604 select FB_DEFERRED_IO
605 select FB_SYS_FILLRECT
606 select FB_SYS_COPYAREA
607 select FB_SYS_IMAGEBLIT
610 Provide access to PicoLCD's 256x64 monochrome display via a
613 config HID_PICOLCD_BACKLIGHT
614 bool "Backlight control" if EXPERT
616 depends on HID_PICOLCD
617 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
619 Provide access to PicoLCD's backlight control via backlight
622 config HID_PICOLCD_LCD
623 bool "Contrast control" if EXPERT
625 depends on HID_PICOLCD
626 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
628 Provide access to PicoLCD's LCD contrast via lcd class.
630 config HID_PICOLCD_LEDS
631 bool "GPO via leds class" if EXPERT
633 depends on HID_PICOLCD
634 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
636 Provide access to PicoLCD's GPO pins via leds class.
638 config HID_PICOLCD_CIR
639 bool "CIR via RC class" if EXPERT
641 depends on HID_PICOLCD
642 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
644 Provide access to PicoLCD's CIR interface via remote control (LIRC).
646 config HID_PLANTRONICS
647 tristate "Plantronics USB HID Driver"
650 Provides HID support for Plantronics USB audio devices.
651 Correctly maps vendor unique volume up/down HID usages to
652 KEY_VOLUMEUP and KEY_VOLUMEDOWN events and prevents core mapping
653 of other vendor unique HID usages to random mouse events.
655 Say M here if you may ever plug in a Plantronics USB audio device.
658 tristate "Primax non-fully HID-compliant devices"
661 Support for Primax devices that are not fully compliant with the
665 tristate "Roccat device support"
668 Support for Roccat devices.
669 Say Y here if you have a Roccat mouse or keyboard and want
670 support for its special functionalities.
673 tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
676 Support for Saitek devices that are not fully compliant with the
680 - PS1000 Dual Analog Pad
681 - R.A.T.9 Gaming Mouse
682 - R.A.T.7 Gaming Mouse
683 - M.M.O.7 Gaming Mouse
686 tristate "Samsung InfraRed remote control or keyboards"
689 Support for Samsung InfraRed remote control or keyboards.
692 tristate "Sony PS2/3/4 accessories"
695 depends on LEDS_CLASS
700 * Sony PS3 6-axis controllers
701 * Sony PS4 DualShock 4 controllers
703 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
704 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
707 bool "Sony PS2/3/4 accessories force feedback support"
709 select INPUT_FF_MEMLESS
711 Say Y here if you have a Sony PS2/3/4 accessory and want to enable
712 force feedback support for it.
715 tristate "Speedlink VAD Cezanne mouse support"
718 Support for Speedlink Vicious and Divine Cezanne mouse.
720 config HID_STEELSERIES
721 tristate "Steelseries SRW-S1 steering wheel support"
724 Support for Steelseries SRW-S1 steering wheel
727 tristate "Sunplus wireless desktop"
730 Support for Sunplus wireless desktop.
733 tristate "Synaptics RMI4 device support"
736 Support for Synaptics RMI4 touchpads.
737 Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
738 and want support for its special functionalities.
741 tristate "GreenAsia (Product ID 0x12) game controller support"
744 Say Y here if you have a GreenAsia (Product ID 0x12) based game
745 controller or adapter.
748 bool "GreenAsia (Product ID 0x12) force feedback support"
749 depends on HID_GREENASIA
750 select INPUT_FF_MEMLESS
752 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
753 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
754 and want to enable force feedback support for it.
756 config HID_HYPERV_MOUSE
757 tristate "Microsoft Hyper-V mouse driver"
760 Select this option to enable the Hyper-V mouse driver.
762 config HID_SMARTJOYPLUS
763 tristate "SmartJoy PLUS PS2/USB adapter support"
766 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
767 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
769 Note that DDR (Dance Dance Revolution) mode is not supported, nor
770 is pressure sensitive buttons on the pro models.
772 config SMARTJOYPLUS_FF
773 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
774 depends on HID_SMARTJOYPLUS
775 select INPUT_FF_MEMLESS
777 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
778 enable force feedback support for it.
781 tristate "TiVo Slide Bluetooth remote control support"
784 Say Y if you have a TiVo Slide Bluetooth remote control.
787 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
790 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
791 CLLRCMCE remote control.
794 tristate "ThingM blink(1) USB RGB LED"
796 depends on LEDS_CLASS
798 Support for the ThingM blink(1) USB RGB LED. This driver registers a
799 Linux LED class instance, plus additional sysfs attributes to control
800 RGB colors, fade time and playing. The device is exposed through hidraw
801 to access other functions.
803 config HID_THRUSTMASTER
804 tristate "ThrustMaster devices support"
807 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
808 a THRUSTMASTER Ferrari GT Rumble Wheel.
810 config THRUSTMASTER_FF
811 bool "ThrustMaster devices force feedback support"
812 depends on HID_THRUSTMASTER
813 select INPUT_FF_MEMLESS
815 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
816 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
817 Rumble Force or Force Feedback Wheel.
820 tristate "Wacom Intuos/Graphire tablet support (USB)"
826 Say Y here if you want to use the USB or BT version of the Wacom Intuos
829 To compile this driver as a module, choose M here: the
830 module will be called wacom.
833 tristate "Nintendo Wii / Wii U peripherals"
835 depends on LEDS_CLASS
837 select INPUT_FF_MEMLESS
839 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
840 devices are the Wii Remote and its extension devices, but also devices
841 based on the Wii Remote like the Wii U Pro Controller or the
844 Support for all official Nintendo extensions is available, however, 3rd
845 party extensions might not be supported. Please report these devices to:
846 http://github.com/dvdhrm/xwiimote/issues
848 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
849 the Wii U Gamepad) might be supported in the future. But currently
850 support is limited to Bluetooth based devices.
854 To compile this driver as a module, choose M here: the
855 module will be called hid-wiimote.
858 tristate "Xin-Mo non-fully compliant devices"
861 Support for Xin-Mo devices that are not fully compliant with the HID
862 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
863 if you have a Xin-Mo Dual Arcade controller.
866 tristate "Zeroplus based game controller support"
869 Say Y here if you have a Zeroplus based game controller.
872 bool "Zeroplus based game controller force feedback support"
873 depends on HID_ZEROPLUS
874 select INPUT_FF_MEMLESS
876 Say Y here if you have a Zeroplus based game controller and want
877 to have force feedback support for it.
880 tristate "Zydacron remote control support"
883 Support for Zydacron remote control.
885 config HID_SENSOR_HUB
886 tristate "HID Sensors framework support"
887 depends on HID && HAS_IOMEM
891 Support for HID Sensor framework. This creates a MFD instance
892 for a sensor hub and identifies all the sensors connected to it.
893 Each sensor is registered as a MFD cell, so that sensor specific
894 processing can be done in a separate driver. Each sensor
895 drivers can use the service provided by this driver to register
896 for events and handle data streams. Each sensor driver can format
897 data and present to user mode using input or IIO interface.
899 config HID_SENSOR_CUSTOM_SENSOR
900 tristate "HID Sensors hub custom sensor support"
901 depends on HID_SENSOR_HUB
904 HID Sensor hub specification allows definition of some custom and
905 generic sensors. Unlike other HID sensors, they can't be exported
906 via Linux IIO because of custom fields. This is up to the manufacturer
907 to decide how to interpret these special sensor ids and process in
908 the user space. Currently some manufacturers are using these ids for
909 sensor calibration and debugging other sensors. Manufacturers
910 should't use these special custom sensor ids to export any of the
912 Select this config option for custom/generic sensor support.
918 source "drivers/hid/usbhid/Kconfig"
920 source "drivers/hid/i2c-hid/Kconfig"