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
375 Say Y if you want support for Logitech Unifying receivers and devices.
376 Unifying receivers are capable of pairing up to 6 Logitech compliant
377 devices to the same receiver. Without this driver it will be handled by
378 generic USB_HID driver and all incoming events will be multiplexed
379 into a single mouse and a single keyboard device.
382 bool "Logitech force feedback support"
383 depends on HID_LOGITECH
384 select INPUT_FF_MEMLESS
386 Say Y here if you have one of these devices:
387 - Logitech WingMan Cordless RumblePad
388 - Logitech WingMan Cordless RumblePad 2
389 - Logitech WingMan Force 3D
390 - Logitech Formula Force EX
391 - Logitech WingMan Formula Force GP
393 and if you want to enable force feedback for them.
394 Note: if you say N here, this device will still be supported, but without
397 config LOGIRUMBLEPAD2_FF
398 bool "Logitech force feedback support (variant 2)"
399 depends on HID_LOGITECH
400 select INPUT_FF_MEMLESS
402 Say Y here if you want to enable force feedback support for:
404 - Logitech Rumblepad 2
405 - Logitech Formula Vibration Feedback Wheel
408 bool "Logitech Flight System G940 force feedback support"
409 depends on HID_LOGITECH
410 select INPUT_FF_MEMLESS
412 Say Y here if you want to enable force feedback support for Logitech
413 Flight System G940 devices.
416 bool "Logitech wheels configuration and force feedback support"
417 depends on HID_LOGITECH
418 select INPUT_FF_MEMLESS
421 Say Y here if you want to enable force feedback and range setting
422 support for following Logitech wheels:
423 - Logitech Driving Force
424 - Logitech Driving Force Pro
425 - Logitech Driving Force GT
428 - Logitech MOMO/MOMO 2
429 - Logitech Formula Force EX
431 config HID_MAGICMOUSE
432 tristate "Apple Magic Mouse/Trackpad multi-touch support"
435 Support for the Apple Magic Mouse/Trackpad multi-touch.
437 Say Y here if you want support for the multi-touch features of the
438 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
441 tristate "Microsoft non-fully HID-compliant devices" if EXPERT
445 Support for Microsoft devices that are not fully compliant with HID standard.
448 tristate "Monterey Genius KB29E keyboard" if EXPERT
452 Support for Monterey Genius KB29E.
454 config HID_MULTITOUCH
455 tristate "HID Multitouch panels"
458 Generic support for HID multitouch panels.
460 Say Y here if you have one of the following devices:
461 - 3M PCT touch screens
462 - ActionStar dual touch panels
464 - Cando dual touch panels
467 - Cypress TrueTouch panels
468 - Elan Microelectronics touch panels
469 - Elo TouchSystems IntelliTouch Plus panels
470 - GeneralTouch 'Sensing Win7-TwoFinger' panels
472 - Hanvon dual touch panels
473 - Ilitek dual touch panels
474 - IrTouch Infrared USB panels
475 - LG Display panels (Dell ST2220Tc)
476 - Lumio CrystalTouch panels
477 - MosArt dual-touch panels
478 - Panasonic multitouch panels
479 - PenMount dual touch panels
480 - Perixx Peripad 701 touchpad
481 - PixArt optical touch screen
482 - Pixcir dual touch panels
484 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
485 - SiS multitouch panels
486 - Stantum multitouch panels
487 - Touch International Panels
489 - Wistron optical touch panels
490 - XAT optical touch panels
491 - Xiroku optical touch panels
492 - Zytronic touch panels
496 To compile this driver as a module, choose M here: the
497 module will be called hid-multitouch.
500 tristate "N-Trig touch screen"
503 Support for N-Trig touch screen.
506 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
509 There are certain devices which have LogicalMaximum wrong in the keyboard
510 usage page of their report descriptor. The most prevailing ones so far
511 are manufactured by Ortek, thus the name of the driver. Currently
512 supported devices by this driver are
516 - Skycable wireless presenter
518 config HID_PANTHERLORD
519 tristate "Pantherlord/GreenAsia game controller"
522 Say Y here if you have a PantherLord/GreenAsia based game controller
525 config PANTHERLORD_FF
526 bool "Pantherlord force feedback support"
527 depends on HID_PANTHERLORD
528 select INPUT_FF_MEMLESS
530 Say Y here if you have a PantherLord/GreenAsia based game controller
531 or adapter and want to enable force feedback support for it.
534 tristate "Petalynx Maxter remote control"
537 Support for Petalynx Maxter remote control.
540 tristate "PicoLCD (graphic version)"
543 This provides support for Minibox PicoLCD devices, currently
544 only the graphical ones are supported.
546 This includes support for the following device features:
548 - Switching between Firmware and Flash mode
549 - EEProm / Flash access (via debugfs)
550 Features selectively enabled:
551 - Framebuffer for monochrome 256x64 display
554 - General purpose outputs
555 Features that are not (yet) supported:
558 config HID_PICOLCD_FB
559 bool "Framebuffer support" if EXPERT
561 depends on HID_PICOLCD
562 depends on HID_PICOLCD=FB || FB=y
563 select FB_DEFERRED_IO
564 select FB_SYS_FILLRECT
565 select FB_SYS_COPYAREA
566 select FB_SYS_IMAGEBLIT
569 Provide access to PicoLCD's 256x64 monochrome display via a
572 config HID_PICOLCD_BACKLIGHT
573 bool "Backlight control" if EXPERT
575 depends on HID_PICOLCD
576 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
578 Provide access to PicoLCD's backlight control via backlight
581 config HID_PICOLCD_LCD
582 bool "Contrast control" if EXPERT
584 depends on HID_PICOLCD
585 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
587 Provide access to PicoLCD's LCD contrast via lcd class.
589 config HID_PICOLCD_LEDS
590 bool "GPO via leds class" if EXPERT
592 depends on HID_PICOLCD
593 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
595 Provide access to PicoLCD's GPO pins via leds class.
597 config HID_PICOLCD_CIR
598 bool "CIR via RC class" if EXPERT
600 depends on HID_PICOLCD
601 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
603 Provide access to PicoLCD's CIR interface via remote control (LIRC).
606 tristate "Primax non-fully HID-compliant devices"
609 Support for Primax devices that are not fully compliant with the
613 tristate "Roccat device support"
616 Support for Roccat devices.
617 Say Y here if you have a Roccat mouse or keyboard and want
618 support for its special functionalities.
621 tristate "Saitek non-fully HID-compliant devices"
624 Support for Saitek devices that are not fully compliant with the
628 - PS1000 Dual Analog Pad
629 - R.A.T.7 Gaming Mouse
630 - M.M.O.7 Gaming Mouse
633 tristate "Samsung InfraRed remote control or keyboards"
636 Support for Samsung InfraRed remote control or keyboards.
639 tristate "Sony PS2/3/4 accessories"
642 depends on LEDS_CLASS
647 * Sony PS3 6-axis controllers
648 * Sony PS4 DualShock 4 controllers
650 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
651 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
654 bool "Sony PS2/3/4 accessories force feedback support"
656 select INPUT_FF_MEMLESS
658 Say Y here if you have a Sony PS2/3/4 accessory and want to enable
659 force feedback support for it.
662 tristate "Speedlink VAD Cezanne mouse support"
665 Support for Speedlink Vicious and Divine Cezanne mouse.
667 config HID_STEELSERIES
668 tristate "Steelseries SRW-S1 steering wheel support"
671 Support for Steelseries SRW-S1 steering wheel
674 tristate "Sunplus wireless desktop"
677 Support for Sunplus wireless desktop.
680 tristate "Synaptics RMI4 device support"
683 Support for Synaptics RMI4 touchpads.
684 Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
685 and want support for its special functionalities.
688 tristate "GreenAsia (Product ID 0x12) game controller support"
691 Say Y here if you have a GreenAsia (Product ID 0x12) based game
692 controller or adapter.
695 bool "GreenAsia (Product ID 0x12) force feedback support"
696 depends on HID_GREENASIA
697 select INPUT_FF_MEMLESS
699 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
700 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
701 and want to enable force feedback support for it.
703 config HID_HYPERV_MOUSE
704 tristate "Microsoft Hyper-V mouse driver"
707 Select this option to enable the Hyper-V mouse driver.
709 config HID_SMARTJOYPLUS
710 tristate "SmartJoy PLUS PS2/USB adapter support"
713 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
714 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
716 Note that DDR (Dance Dance Revolution) mode is not supported, nor
717 is pressure sensitive buttons on the pro models.
719 config SMARTJOYPLUS_FF
720 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
721 depends on HID_SMARTJOYPLUS
722 select INPUT_FF_MEMLESS
724 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
725 enable force feedback support for it.
728 tristate "TiVo Slide Bluetooth remote control support"
731 Say Y if you have a TiVo Slide Bluetooth remote control.
734 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
737 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
738 CLLRCMCE remote control.
741 tristate "ThingM blink(1) USB RGB LED"
743 depends on LEDS_CLASS
745 Support for the ThingM blink(1) USB RGB LED. This driver registers a
746 Linux LED class instance, plus additional sysfs attributes to control
747 RGB colors, fade time and playing. The device is exposed through hidraw
748 to access other functions.
750 config HID_THRUSTMASTER
751 tristate "ThrustMaster devices support"
754 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
755 a THRUSTMASTER Ferrari GT Rumble Wheel.
757 config THRUSTMASTER_FF
758 bool "ThrustMaster devices force feedback support"
759 depends on HID_THRUSTMASTER
760 select INPUT_FF_MEMLESS
762 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
763 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
764 Rumble Force or Force Feedback Wheel.
767 tristate "Wacom Bluetooth devices support"
769 depends on LEDS_CLASS
772 Support for Wacom Graphire Bluetooth and Intuos4 WL tablets.
775 tristate "Nintendo Wii / Wii U peripherals"
777 depends on LEDS_CLASS
779 select INPUT_FF_MEMLESS
781 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
782 devices are the Wii Remote and its extension devices, but also devices
783 based on the Wii Remote like the Wii U Pro Controller or the
786 Support for all official Nintendo extensions is available, however, 3rd
787 party extensions might not be supported. Please report these devices to:
788 http://github.com/dvdhrm/xwiimote/issues
790 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
791 the Wii U Gamepad) might be supported in the future. But currently
792 support is limited to Bluetooth based devices.
796 To compile this driver as a module, choose M here: the
797 module will be called hid-wiimote.
800 tristate "Xin-Mo non-fully compliant devices"
803 Support for Xin-Mo devices that are not fully compliant with the HID
804 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
805 if you have a Xin-Mo Dual Arcade controller.
808 tristate "Zeroplus based game controller support"
811 Say Y here if you have a Zeroplus based game controller.
814 bool "Zeroplus based game controller force feedback support"
815 depends on HID_ZEROPLUS
816 select INPUT_FF_MEMLESS
818 Say Y here if you have a Zeroplus based game controller and want
819 to have force feedback support for it.
822 tristate "Zydacron remote control support"
825 Support for Zydacron remote control.
827 config HID_SENSOR_HUB
828 tristate "HID Sensors framework support"
829 depends on HID && HAS_IOMEM
833 Support for HID Sensor framework. This creates a MFD instance
834 for a sensor hub and identifies all the sensors connected to it.
835 Each sensor is registered as a MFD cell, so that sensor specific
836 processing can be done in a separate driver. Each sensor
837 drivers can use the service provided by this driver to register
838 for events and handle data streams. Each sensor driver can format
839 data and present to user mode using input or IIO interface.
845 source "drivers/hid/usbhid/Kconfig"
847 source "drivers/hid/i2c-hid/Kconfig"