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 "Holtek HID devices"
258 Support for Holtek based devices:
259 - Holtek On Line Grip based game controller
260 - Trust GXT 18 Gaming Keyboard
261 - Sharkoon Drakonia / Perixx MX-2000 gaming mice
262 - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
264 - SHARKOON DarkGlider Gaming mouse
265 - LEETGION Hellion Gaming Mouse
268 bool "Holtek On Line Grip force feedback support"
269 depends on HID_HOLTEK
270 select INPUT_FF_MEMLESS
272 Say Y here if you have a Holtek On Line Grip based game controller
273 and want to have force feedback support for it.
276 tristate "MSI GT68xR LED support"
277 depends on LEDS_CLASS && USB_HID
279 Say Y here if you want to enable support for the three MSI GT68xR LEDs
281 This driver support following modes:
282 - Normal: LEDs are fully on when enabled
283 - Audio: LEDs brightness depends on sound level
284 - Breathing: LEDs brightness varies at human breathing rate
286 Currently the following devices are know to be supported:
290 tristate "Keytouch HID devices"
293 Support for Keytouch HID devices not fully compliant with
294 the specification. Currently supported:
298 tristate "KYE/Genius devices"
301 Support for KYE/Genius devices not fully compliant with HID standard:
303 - EasyPen i405X tablet
304 - MousePen i608X tablet
305 - EasyPen M610X tablet
311 Support for UC-Logic and Huion tablets.
317 Support for Waltop tablets.
320 tristate "Gyration remote control"
323 Support for Gyration remote control.
326 tristate "ION iCade arcade controller"
329 Support for the ION iCade arcade controller to work as a joystick.
331 To compile this driver as a module, choose M here: the
332 module will be called hid-icade.
335 tristate "Twinhan IR remote control"
338 Support for Twinhan IR remote control.
340 config HID_KENSINGTON
341 tristate "Kensington Slimblade Trackball"
345 Support for Kensington Slimblade Trackball.
351 Support for LC-Power RC1000MCE RF remote control.
354 tristate "Lenovo / Thinkpad devices"
359 Support for Lenovo devices that are not fully compliant with HID standard.
361 Say Y if you want support for the non-compliant features of the Lenovo
362 Thinkpad standalone keyboards, e.g:
363 - ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
365 - ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
366 - ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
369 tristate "Logitech devices"
373 Support for Logitech devices that are not fully compliant with HID standard.
375 config HID_LOGITECH_DJ
376 tristate "Logitech Unifying receivers full support"
378 depends on HID_LOGITECH
379 select HID_LOGITECH_HIDPP
381 Say Y if you want support for Logitech Unifying receivers and devices.
382 Unifying receivers are capable of pairing up to 6 Logitech compliant
383 devices to the same receiver. Without this driver it will be handled by
384 generic USB_HID driver and all incoming events will be multiplexed
385 into a single mouse and a single keyboard device.
387 config HID_LOGITECH_HIDPP
388 tristate "Logitech HID++ devices support"
389 depends on HID_LOGITECH
391 Support for Logitech devices relyingon the HID++ Logitech specification
393 Say Y if you want support for Logitech devices relying on the HID++
394 specification. Such devices are the various Logitech Touchpads (T650,
395 T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
399 bool "Logitech force feedback support"
400 depends on HID_LOGITECH
401 select INPUT_FF_MEMLESS
403 Say Y here if you have one of these devices:
404 - Logitech WingMan Cordless RumblePad
405 - Logitech WingMan Cordless RumblePad 2
406 - Logitech WingMan Force 3D
407 - Logitech Formula Force EX
408 - Logitech WingMan Formula Force GP
410 and if you want to enable force feedback for them.
411 Note: if you say N here, this device will still be supported, but without
414 config LOGIRUMBLEPAD2_FF
415 bool "Logitech force feedback support (variant 2)"
416 depends on HID_LOGITECH
417 select INPUT_FF_MEMLESS
419 Say Y here if you want to enable force feedback support for:
421 - Logitech Rumblepad 2
422 - Logitech Formula Vibration Feedback Wheel
425 bool "Logitech Flight System G940 force feedback support"
426 depends on HID_LOGITECH
427 select INPUT_FF_MEMLESS
429 Say Y here if you want to enable force feedback support for Logitech
430 Flight System G940 devices.
433 bool "Logitech wheels configuration and force feedback support"
434 depends on HID_LOGITECH
435 select INPUT_FF_MEMLESS
438 Say Y here if you want to enable force feedback and range setting
439 support for following Logitech wheels:
440 - Logitech Driving Force
441 - Logitech Driving Force Pro
442 - Logitech Driving Force GT
445 - Logitech MOMO/MOMO 2
446 - Logitech Formula Force EX
448 config HID_MAGICMOUSE
449 tristate "Apple Magic Mouse/Trackpad multi-touch support"
452 Support for the Apple Magic Mouse/Trackpad multi-touch.
454 Say Y here if you want support for the multi-touch features of the
455 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
458 tristate "Microsoft non-fully HID-compliant devices"
462 Support for Microsoft devices that are not fully compliant with HID standard.
465 tristate "Monterey Genius KB29E keyboard"
469 Support for Monterey Genius KB29E.
471 config HID_MULTITOUCH
472 tristate "HID Multitouch panels"
475 Generic support for HID multitouch panels.
477 Say Y here if you have one of the following devices:
478 - 3M PCT touch screens
479 - ActionStar dual touch panels
481 - Cando dual touch panels
484 - Cypress TrueTouch panels
485 - Elan Microelectronics touch panels
486 - Elo TouchSystems IntelliTouch Plus panels
487 - GeneralTouch 'Sensing Win7-TwoFinger' panels
489 - Hanvon dual touch panels
490 - Ilitek dual touch panels
491 - IrTouch Infrared USB panels
492 - LG Display panels (Dell ST2220Tc)
493 - Lumio CrystalTouch panels
494 - MosArt dual-touch panels
495 - Panasonic multitouch panels
496 - PenMount dual touch panels
497 - Perixx Peripad 701 touchpad
498 - PixArt optical touch screen
499 - Pixcir dual touch panels
501 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
502 - SiS multitouch panels
503 - Stantum multitouch panels
504 - Touch International Panels
506 - Wistron optical touch panels
507 - XAT optical touch panels
508 - Xiroku optical touch panels
509 - Zytronic touch panels
513 To compile this driver as a module, choose M here: the
514 module will be called hid-multitouch.
517 tristate "N-Trig touch screen"
520 Support for N-Trig touch screen.
523 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
526 There are certain devices which have LogicalMaximum wrong in the keyboard
527 usage page of their report descriptor. The most prevailing ones so far
528 are manufactured by Ortek, thus the name of the driver. Currently
529 supported devices by this driver are
533 - Skycable wireless presenter
535 config HID_PANTHERLORD
536 tristate "Pantherlord/GreenAsia game controller"
539 Say Y here if you have a PantherLord/GreenAsia based game controller
542 config PANTHERLORD_FF
543 bool "Pantherlord force feedback support"
544 depends on HID_PANTHERLORD
545 select INPUT_FF_MEMLESS
547 Say Y here if you have a PantherLord/GreenAsia based game controller
548 or adapter and want to enable force feedback support for it.
551 tristate "Penmount touch device"
554 This selects a driver for the PenMount 6000 touch controller.
556 The driver works around a problem in the report descript allowing
557 the userspace to touch events instead of mouse events.
559 Say Y here if you have a Penmount based touch controller.
562 tristate "Petalynx Maxter remote control"
565 Support for Petalynx Maxter remote control.
568 tristate "PicoLCD (graphic version)"
571 This provides support for Minibox PicoLCD devices, currently
572 only the graphical ones are supported.
574 This includes support for the following device features:
576 - Switching between Firmware and Flash mode
577 - EEProm / Flash access (via debugfs)
578 Features selectively enabled:
579 - Framebuffer for monochrome 256x64 display
582 - General purpose outputs
583 Features that are not (yet) supported:
586 config HID_PICOLCD_FB
587 bool "Framebuffer support" if EXPERT
589 depends on HID_PICOLCD
590 depends on HID_PICOLCD=FB || FB=y
591 select FB_DEFERRED_IO
592 select FB_SYS_FILLRECT
593 select FB_SYS_COPYAREA
594 select FB_SYS_IMAGEBLIT
597 Provide access to PicoLCD's 256x64 monochrome display via a
600 config HID_PICOLCD_BACKLIGHT
601 bool "Backlight control" if EXPERT
603 depends on HID_PICOLCD
604 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
606 Provide access to PicoLCD's backlight control via backlight
609 config HID_PICOLCD_LCD
610 bool "Contrast control" if EXPERT
612 depends on HID_PICOLCD
613 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
615 Provide access to PicoLCD's LCD contrast via lcd class.
617 config HID_PICOLCD_LEDS
618 bool "GPO via leds class" if EXPERT
620 depends on HID_PICOLCD
621 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
623 Provide access to PicoLCD's GPO pins via leds class.
625 config HID_PICOLCD_CIR
626 bool "CIR via RC class" if EXPERT
628 depends on HID_PICOLCD
629 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
631 Provide access to PicoLCD's CIR interface via remote control (LIRC).
633 config HID_PLANTRONICS
634 tristate "Plantronics USB HID Driver"
637 Provides HID support for Plantronics telephony devices.
640 tristate "Primax non-fully HID-compliant devices"
643 Support for Primax devices that are not fully compliant with the
647 tristate "Roccat device support"
650 Support for Roccat devices.
651 Say Y here if you have a Roccat mouse or keyboard and want
652 support for its special functionalities.
655 tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
658 Support for Saitek devices that are not fully compliant with the
662 - PS1000 Dual Analog Pad
663 - R.A.T.9 Gaming Mouse
664 - R.A.T.7 Gaming Mouse
665 - M.M.O.7 Gaming Mouse
668 tristate "Samsung InfraRed remote control or keyboards"
671 Support for Samsung InfraRed remote control or keyboards.
674 tristate "Sony PS2/3/4 accessories"
677 depends on LEDS_CLASS
682 * Sony PS3 6-axis controllers
683 * Sony PS4 DualShock 4 controllers
685 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
686 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
689 bool "Sony PS2/3/4 accessories force feedback support"
691 select INPUT_FF_MEMLESS
693 Say Y here if you have a Sony PS2/3/4 accessory and want to enable
694 force feedback support for it.
697 tristate "Speedlink VAD Cezanne mouse support"
700 Support for Speedlink Vicious and Divine Cezanne mouse.
702 config HID_STEELSERIES
703 tristate "Steelseries SRW-S1 steering wheel support"
706 Support for Steelseries SRW-S1 steering wheel
709 tristate "Sunplus wireless desktop"
712 Support for Sunplus wireless desktop.
715 tristate "Synaptics RMI4 device support"
718 Support for Synaptics RMI4 touchpads.
719 Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
720 and want support for its special functionalities.
723 tristate "GreenAsia (Product ID 0x12) game controller support"
726 Say Y here if you have a GreenAsia (Product ID 0x12) based game
727 controller or adapter.
730 bool "GreenAsia (Product ID 0x12) force feedback support"
731 depends on HID_GREENASIA
732 select INPUT_FF_MEMLESS
734 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
735 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
736 and want to enable force feedback support for it.
738 config HID_HYPERV_MOUSE
739 tristate "Microsoft Hyper-V mouse driver"
742 Select this option to enable the Hyper-V mouse driver.
744 config HID_SMARTJOYPLUS
745 tristate "SmartJoy PLUS PS2/USB adapter support"
748 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
749 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
751 Note that DDR (Dance Dance Revolution) mode is not supported, nor
752 is pressure sensitive buttons on the pro models.
754 config SMARTJOYPLUS_FF
755 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
756 depends on HID_SMARTJOYPLUS
757 select INPUT_FF_MEMLESS
759 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
760 enable force feedback support for it.
763 tristate "TiVo Slide Bluetooth remote control support"
766 Say Y if you have a TiVo Slide Bluetooth remote control.
769 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
772 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
773 CLLRCMCE remote control.
776 tristate "ThingM blink(1) USB RGB LED"
778 depends on LEDS_CLASS
780 Support for the ThingM blink(1) USB RGB LED. This driver registers a
781 Linux LED class instance, plus additional sysfs attributes to control
782 RGB colors, fade time and playing. The device is exposed through hidraw
783 to access other functions.
785 config HID_THRUSTMASTER
786 tristate "ThrustMaster devices support"
789 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
790 a THRUSTMASTER Ferrari GT Rumble Wheel.
792 config THRUSTMASTER_FF
793 bool "ThrustMaster devices force feedback support"
794 depends on HID_THRUSTMASTER
795 select INPUT_FF_MEMLESS
797 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
798 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
799 Rumble Force or Force Feedback Wheel.
802 tristate "Wacom Intuos/Graphire tablet support (USB)"
808 Say Y here if you want to use the USB or BT version of the Wacom Intuos
811 To compile this driver as a module, choose M here: the
812 module will be called wacom.
815 tristate "Nintendo Wii / Wii U peripherals"
817 depends on LEDS_CLASS
819 select INPUT_FF_MEMLESS
821 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
822 devices are the Wii Remote and its extension devices, but also devices
823 based on the Wii Remote like the Wii U Pro Controller or the
826 Support for all official Nintendo extensions is available, however, 3rd
827 party extensions might not be supported. Please report these devices to:
828 http://github.com/dvdhrm/xwiimote/issues
830 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
831 the Wii U Gamepad) might be supported in the future. But currently
832 support is limited to Bluetooth based devices.
836 To compile this driver as a module, choose M here: the
837 module will be called hid-wiimote.
840 tristate "Xin-Mo non-fully compliant devices"
843 Support for Xin-Mo devices that are not fully compliant with the HID
844 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
845 if you have a Xin-Mo Dual Arcade controller.
848 tristate "Zeroplus based game controller support"
851 Say Y here if you have a Zeroplus based game controller.
854 bool "Zeroplus based game controller force feedback support"
855 depends on HID_ZEROPLUS
856 select INPUT_FF_MEMLESS
858 Say Y here if you have a Zeroplus based game controller and want
859 to have force feedback support for it.
862 tristate "Zydacron remote control support"
865 Support for Zydacron remote control.
867 config HID_SENSOR_HUB
868 tristate "HID Sensors framework support"
869 depends on HID && HAS_IOMEM
873 Support for HID Sensor framework. This creates a MFD instance
874 for a sensor hub and identifies all the sensors connected to it.
875 Each sensor is registered as a MFD cell, so that sensor specific
876 processing can be done in a separate driver. Each sensor
877 drivers can use the service provided by this driver to register
878 for events and handle data streams. Each sensor driver can format
879 data and present to user mode using input or IIO interface.
881 config HID_SENSOR_CUSTOM_SENSOR
882 tristate "HID Sensors hub custom sensor support"
883 depends on HID_SENSOR_HUB
886 HID Sensor hub specification allows definition of some custom and
887 generic sensors. Unlike other HID sensors, they can't be exported
888 via Linux IIO because of custom fields. This is up to the manufacturer
889 to decide how to interpret these special sensor ids and process in
890 the user space. Currently some manufacturers are using these ids for
891 sensor calibration and debugging other sensors. Manufacturers
892 should't use these special custom sensor ids to export any of the
894 Select this config option for custom/generic sensor support.
900 source "drivers/hid/usbhid/Kconfig"
902 source "drivers/hid/i2c-hid/Kconfig"