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 "Silicon Labs CP2112 HID USB-to-SMBus Bridge support"
180 depends on USB_HID && I2C && GPIOLIB
182 Support for Silicon Labs CP2112 HID USB to SMBus Master Bridge.
183 This is a HID device driver which registers as an i2c adapter
184 and gpiochip to expose these functions of the CP2112. The
185 customizable USB descriptor fields are exposed as sysfs attributes.
188 tristate "Cypress mouse and barcode readers" if EXPERT
192 Support for cypress mouse and barcode readers.
194 config HID_DRAGONRISE
195 tristate "DragonRise Inc. game controller"
198 Say Y here if you have DragonRise Inc. game controllers.
199 These might be branded as:
201 - Media-tech MT1504 "Rogue"
203 - Defender Game Master
206 bool "DragonRise Inc. force feedback"
207 depends on HID_DRAGONRISE
208 select INPUT_FF_MEMLESS
210 Say Y here if you want to enable force feedback support for DragonRise Inc.
214 tristate "EMS Production Inc. force feedback support"
216 select INPUT_FF_MEMLESS
218 Say Y here if you want to enable force feedback support for devices by
220 Currently the following devices are known to be supported:
221 - Trio Linker Plus II
224 tristate "ELECOM BM084 bluetooth mouse"
227 Support for the ELECOM BM084 (bluetooth mouse).
230 tristate "ELO USB 4000/4500 touchscreen"
233 Support for the ELO USB 4000/4500 touchscreens. Note that this is for
234 different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
237 tristate "Ezkey BTC 8193 keyboard" if EXPERT
241 Support for Ezkey BTC 8193 keyboard.
244 tristate "Holtek HID devices"
247 Support for Holtek based devices:
248 - Holtek On Line Grip based game controller
249 - Trust GXT 18 Gaming Keyboard
250 - Sharkoon Drakonia / Perixx MX-2000 gaming mice
251 - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
253 - SHARKOON DarkGlider Gaming mouse
254 - LEETGION Hellion Gaming Mouse
257 bool "Holtek On Line Grip force feedback support"
258 depends on HID_HOLTEK
259 select INPUT_FF_MEMLESS
261 Say Y here if you have a Holtek On Line Grip based game controller
262 and want to have force feedback support for it.
265 tristate "MSI GT68xR LED support"
266 depends on LEDS_CLASS && USB_HID
268 Say Y here if you want to enable support for the three MSI GT68xR LEDs
270 This driver support following modes:
271 - Normal: LEDs are fully on when enabled
272 - Audio: LEDs brightness depends on sound level
273 - Breathing: LEDs brightness varies at human breathing rate
275 Currently the following devices are know to be supported:
279 tristate "Huion tablets"
282 Support for Huion 580 tablet.
285 tristate "Keytouch HID devices"
288 Support for Keytouch HID devices not fully compliant with
289 the specification. Currently supported:
293 tristate "KYE/Genius devices"
296 Support for KYE/Genius devices not fully compliant with HID standard:
298 - EasyPen i405X tablet
299 - MousePen i608X tablet
300 - EasyPen M610X tablet
306 Support for UC-Logic tablets.
312 Support for Waltop tablets.
315 tristate "Gyration remote control"
318 Support for Gyration remote control.
321 tristate "ION iCade arcade controller"
324 Support for the ION iCade arcade controller to work as a joystick.
326 To compile this driver as a module, choose M here: the
327 module will be called hid-icade.
330 tristate "Twinhan IR remote control"
333 Support for Twinhan IR remote control.
335 config HID_KENSINGTON
336 tristate "Kensington Slimblade Trackball" if EXPERT
340 Support for Kensington Slimblade Trackball.
346 Support for LC-Power RC1000MCE RF remote control.
349 tristate "Lenovo / Thinkpad devices"
354 Support for Lenovo devices that are not fully compliant with HID standard.
356 Say Y if you want support for the non-compliant features of the Lenovo
357 Thinkpad standalone keyboards, e.g:
358 - ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
360 - ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
361 - ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
364 tristate "Logitech devices" if EXPERT
368 Support for Logitech devices that are not fully compliant with HID standard.
370 config HID_LOGITECH_DJ
371 tristate "Logitech Unifying receivers full support"
373 depends on HID_LOGITECH
374 select HID_LOGITECH_HIDPP
376 Say Y if you want support for Logitech Unifying receivers and devices.
377 Unifying receivers are capable of pairing up to 6 Logitech compliant
378 devices to the same receiver. Without this driver it will be handled by
379 generic USB_HID driver and all incoming events will be multiplexed
380 into a single mouse and a single keyboard device.
382 config HID_LOGITECH_HIDPP
383 tristate "Logitech HID++ devices support"
384 depends on HID_LOGITECH
386 Support for Logitech devices relyingon the HID++ Logitech specification
388 Say Y if you want support for Logitech devices relying on the HID++
389 specification. Such devices are the various Logitech Touchpads (T650,
390 T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
394 bool "Logitech force feedback support"
395 depends on HID_LOGITECH
396 select INPUT_FF_MEMLESS
398 Say Y here if you have one of these devices:
399 - Logitech WingMan Cordless RumblePad
400 - Logitech WingMan Cordless RumblePad 2
401 - Logitech WingMan Force 3D
402 - Logitech Formula Force EX
403 - Logitech WingMan Formula Force GP
405 and if you want to enable force feedback for them.
406 Note: if you say N here, this device will still be supported, but without
409 config LOGIRUMBLEPAD2_FF
410 bool "Logitech force feedback support (variant 2)"
411 depends on HID_LOGITECH
412 select INPUT_FF_MEMLESS
414 Say Y here if you want to enable force feedback support for:
416 - Logitech Rumblepad 2
417 - Logitech Formula Vibration Feedback Wheel
420 bool "Logitech Flight System G940 force feedback support"
421 depends on HID_LOGITECH
422 select INPUT_FF_MEMLESS
424 Say Y here if you want to enable force feedback support for Logitech
425 Flight System G940 devices.
428 bool "Logitech wheels configuration and force feedback support"
429 depends on HID_LOGITECH
430 select INPUT_FF_MEMLESS
433 Say Y here if you want to enable force feedback and range setting
434 support for following Logitech wheels:
435 - Logitech Driving Force
436 - Logitech Driving Force Pro
437 - Logitech Driving Force GT
440 - Logitech MOMO/MOMO 2
441 - Logitech Formula Force EX
443 config HID_MAGICMOUSE
444 tristate "Apple Magic Mouse/Trackpad multi-touch support"
447 Support for the Apple Magic Mouse/Trackpad multi-touch.
449 Say Y here if you want support for the multi-touch features of the
450 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
453 tristate "Microsoft non-fully HID-compliant devices" if EXPERT
457 Support for Microsoft devices that are not fully compliant with HID standard.
460 tristate "Monterey Genius KB29E keyboard" if EXPERT
464 Support for Monterey Genius KB29E.
466 config HID_MULTITOUCH
467 tristate "HID Multitouch panels"
470 Generic support for HID multitouch panels.
472 Say Y here if you have one of the following devices:
473 - 3M PCT touch screens
474 - ActionStar dual touch panels
476 - Cando dual touch panels
479 - Cypress TrueTouch panels
480 - Elan Microelectronics touch panels
481 - Elo TouchSystems IntelliTouch Plus panels
482 - GeneralTouch 'Sensing Win7-TwoFinger' panels
484 - Hanvon dual touch panels
485 - Ilitek dual touch panels
486 - IrTouch Infrared USB panels
487 - LG Display panels (Dell ST2220Tc)
488 - Lumio CrystalTouch panels
489 - MosArt dual-touch panels
490 - Panasonic multitouch panels
491 - PenMount dual touch panels
492 - Perixx Peripad 701 touchpad
493 - PixArt optical touch screen
494 - Pixcir dual touch panels
496 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
497 - SiS multitouch panels
498 - Stantum multitouch panels
499 - Touch International Panels
501 - Wistron optical touch panels
502 - XAT optical touch panels
503 - Xiroku optical touch panels
504 - Zytronic touch panels
508 To compile this driver as a module, choose M here: the
509 module will be called hid-multitouch.
512 tristate "N-Trig touch screen"
515 Support for N-Trig touch screen.
518 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
521 There are certain devices which have LogicalMaximum wrong in the keyboard
522 usage page of their report descriptor. The most prevailing ones so far
523 are manufactured by Ortek, thus the name of the driver. Currently
524 supported devices by this driver are
528 - Skycable wireless presenter
530 config HID_PANTHERLORD
531 tristate "Pantherlord/GreenAsia game controller"
534 Say Y here if you have a PantherLord/GreenAsia based game controller
537 config PANTHERLORD_FF
538 bool "Pantherlord force feedback support"
539 depends on HID_PANTHERLORD
540 select INPUT_FF_MEMLESS
542 Say Y here if you have a PantherLord/GreenAsia based game controller
543 or adapter and want to enable force feedback support for it.
546 tristate "Penmount touch device"
549 This selects a driver for the PenMount 6000 touch controller.
551 The driver works around a problem in the report descript allowing
552 the userspace to touch events instead of mouse events.
554 Say Y here if you have a Penmount based touch controller.
557 tristate "Petalynx Maxter remote control"
560 Support for Petalynx Maxter remote control.
563 tristate "PicoLCD (graphic version)"
566 This provides support for Minibox PicoLCD devices, currently
567 only the graphical ones are supported.
569 This includes support for the following device features:
571 - Switching between Firmware and Flash mode
572 - EEProm / Flash access (via debugfs)
573 Features selectively enabled:
574 - Framebuffer for monochrome 256x64 display
577 - General purpose outputs
578 Features that are not (yet) supported:
581 config HID_PICOLCD_FB
582 bool "Framebuffer support" if EXPERT
584 depends on HID_PICOLCD
585 depends on HID_PICOLCD=FB || FB=y
586 select FB_DEFERRED_IO
587 select FB_SYS_FILLRECT
588 select FB_SYS_COPYAREA
589 select FB_SYS_IMAGEBLIT
592 Provide access to PicoLCD's 256x64 monochrome display via a
595 config HID_PICOLCD_BACKLIGHT
596 bool "Backlight control" if EXPERT
598 depends on HID_PICOLCD
599 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
601 Provide access to PicoLCD's backlight control via backlight
604 config HID_PICOLCD_LCD
605 bool "Contrast control" if EXPERT
607 depends on HID_PICOLCD
608 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
610 Provide access to PicoLCD's LCD contrast via lcd class.
612 config HID_PICOLCD_LEDS
613 bool "GPO via leds class" if EXPERT
615 depends on HID_PICOLCD
616 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
618 Provide access to PicoLCD's GPO pins via leds class.
620 config HID_PICOLCD_CIR
621 bool "CIR via RC class" if EXPERT
623 depends on HID_PICOLCD
624 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
626 Provide access to PicoLCD's CIR interface via remote control (LIRC).
629 tristate "Primax non-fully HID-compliant devices"
632 Support for Primax devices that are not fully compliant with the
636 tristate "Roccat device support"
639 Support for Roccat devices.
640 Say Y here if you have a Roccat mouse or keyboard and want
641 support for its special functionalities.
644 tristate "Saitek non-fully HID-compliant devices"
647 Support for Saitek devices that are not fully compliant with the
651 - PS1000 Dual Analog Pad
652 - R.A.T.7 Gaming Mouse
653 - M.M.O.7 Gaming Mouse
656 tristate "Samsung InfraRed remote control or keyboards"
659 Support for Samsung InfraRed remote control or keyboards.
662 tristate "Sony PS2/3/4 accessories"
665 depends on LEDS_CLASS
670 * Sony PS3 6-axis controllers
671 * Sony PS4 DualShock 4 controllers
673 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
674 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
677 bool "Sony PS2/3/4 accessories force feedback support"
679 select INPUT_FF_MEMLESS
681 Say Y here if you have a Sony PS2/3/4 accessory and want to enable
682 force feedback support for it.
685 tristate "Speedlink VAD Cezanne mouse support"
688 Support for Speedlink Vicious and Divine Cezanne mouse.
690 config HID_STEELSERIES
691 tristate "Steelseries SRW-S1 steering wheel support"
694 Support for Steelseries SRW-S1 steering wheel
697 tristate "Sunplus wireless desktop"
700 Support for Sunplus wireless desktop.
703 tristate "Synaptics RMI4 device support"
706 Support for Synaptics RMI4 touchpads.
707 Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
708 and want support for its special functionalities.
711 tristate "GreenAsia (Product ID 0x12) game controller support"
714 Say Y here if you have a GreenAsia (Product ID 0x12) based game
715 controller or adapter.
718 bool "GreenAsia (Product ID 0x12) force feedback support"
719 depends on HID_GREENASIA
720 select INPUT_FF_MEMLESS
722 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
723 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
724 and want to enable force feedback support for it.
726 config HID_HYPERV_MOUSE
727 tristate "Microsoft Hyper-V mouse driver"
730 Select this option to enable the Hyper-V mouse driver.
732 config HID_SMARTJOYPLUS
733 tristate "SmartJoy PLUS PS2/USB adapter support"
736 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
737 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
739 Note that DDR (Dance Dance Revolution) mode is not supported, nor
740 is pressure sensitive buttons on the pro models.
742 config SMARTJOYPLUS_FF
743 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
744 depends on HID_SMARTJOYPLUS
745 select INPUT_FF_MEMLESS
747 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
748 enable force feedback support for it.
751 tristate "TiVo Slide Bluetooth remote control support"
754 Say Y if you have a TiVo Slide Bluetooth remote control.
757 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
760 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
761 CLLRCMCE remote control.
764 tristate "ThingM blink(1) USB RGB LED"
766 depends on LEDS_CLASS
768 Support for the ThingM blink(1) USB RGB LED. This driver registers a
769 Linux LED class instance, plus additional sysfs attributes to control
770 RGB colors, fade time and playing. The device is exposed through hidraw
771 to access other functions.
773 config HID_THRUSTMASTER
774 tristate "ThrustMaster devices support"
777 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
778 a THRUSTMASTER Ferrari GT Rumble Wheel.
780 config THRUSTMASTER_FF
781 bool "ThrustMaster devices force feedback support"
782 depends on HID_THRUSTMASTER
783 select INPUT_FF_MEMLESS
785 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
786 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
787 Rumble Force or Force Feedback Wheel.
790 tristate "Wacom Intuos/Graphire tablet support (USB)"
796 Say Y here if you want to use the USB or BT version of the Wacom Intuos
799 To compile this driver as a module, choose M here: the
800 module will be called wacom.
803 tristate "Nintendo Wii / Wii U peripherals"
805 depends on LEDS_CLASS
807 select INPUT_FF_MEMLESS
809 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
810 devices are the Wii Remote and its extension devices, but also devices
811 based on the Wii Remote like the Wii U Pro Controller or the
814 Support for all official Nintendo extensions is available, however, 3rd
815 party extensions might not be supported. Please report these devices to:
816 http://github.com/dvdhrm/xwiimote/issues
818 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
819 the Wii U Gamepad) might be supported in the future. But currently
820 support is limited to Bluetooth based devices.
824 To compile this driver as a module, choose M here: the
825 module will be called hid-wiimote.
828 tristate "Xin-Mo non-fully compliant devices"
831 Support for Xin-Mo devices that are not fully compliant with the HID
832 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
833 if you have a Xin-Mo Dual Arcade controller.
836 tristate "Zeroplus based game controller support"
839 Say Y here if you have a Zeroplus based game controller.
842 bool "Zeroplus based game controller force feedback support"
843 depends on HID_ZEROPLUS
844 select INPUT_FF_MEMLESS
846 Say Y here if you have a Zeroplus based game controller and want
847 to have force feedback support for it.
850 tristate "Zydacron remote control support"
853 Support for Zydacron remote control.
855 config HID_SENSOR_HUB
856 tristate "HID Sensors framework support"
857 depends on HID && HAS_IOMEM
861 Support for HID Sensor framework. This creates a MFD instance
862 for a sensor hub and identifies all the sensors connected to it.
863 Each sensor is registered as a MFD cell, so that sensor specific
864 processing can be done in a separate driver. Each sensor
865 drivers can use the service provided by this driver to register
866 for events and handle data streams. Each sensor driver can format
867 data and present to user mode using input or IIO interface.
873 source "drivers/hid/usbhid/Kconfig"
875 source "drivers/hid/i2c-hid/Kconfig"