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 "Huion tablets"
268 Support for Huion 580 tablet.
271 tristate "Keytouch HID devices"
274 Support for Keytouch HID devices not fully compliant with
275 the specification. Currently supported:
279 tristate "KYE/Genius devices"
282 Support for KYE/Genius devices not fully compliant with HID standard:
284 - EasyPen i405X tablet
285 - MousePen i608X tablet
286 - EasyPen M610X tablet
292 Support for UC-Logic tablets.
298 Support for Waltop tablets.
301 tristate "Gyration remote control"
304 Support for Gyration remote control.
307 tristate "ION iCade arcade controller"
310 Support for the ION iCade arcade controller to work as a joystick.
312 To compile this driver as a module, choose M here: the
313 module will be called hid-icade.
316 tristate "Twinhan IR remote control"
319 Support for Twinhan IR remote control.
321 config HID_KENSINGTON
322 tristate "Kensington Slimblade Trackball" if EXPERT
326 Support for Kensington Slimblade Trackball.
332 Support for LC-Power RC1000MCE RF remote control.
334 config HID_LENOVO_TPKBD
335 tristate "Lenovo ThinkPad USB Keyboard with TrackPoint"
340 Support for the Lenovo ThinkPad USB Keyboard with TrackPoint.
342 Say Y here if you have a Lenovo ThinkPad USB Keyboard with TrackPoint
343 and would like to use device-specific features like changing the
344 sensitivity of the trackpoint, using the microphone mute button or
345 controlling the mute and microphone mute LEDs.
348 tristate "Logitech devices" if EXPERT
352 Support for Logitech devices that are not fully compliant with HID standard.
354 config HID_LOGITECH_DJ
355 tristate "Logitech Unifying receivers full support"
357 depends on HID_LOGITECH
359 Say Y if you want support for Logitech Unifying receivers and devices.
360 Unifying receivers are capable of pairing up to 6 Logitech compliant
361 devices to the same receiver. Without this driver it will be handled by
362 generic USB_HID driver and all incoming events will be multiplexed
363 into a single mouse and a single keyboard device.
366 bool "Logitech force feedback support"
367 depends on HID_LOGITECH
368 select INPUT_FF_MEMLESS
370 Say Y here if you have one of these devices:
371 - Logitech WingMan Cordless RumblePad
372 - Logitech WingMan Cordless RumblePad 2
373 - Logitech WingMan Force 3D
374 - Logitech Formula Force EX
375 - Logitech WingMan Formula Force GP
377 and if you want to enable force feedback for them.
378 Note: if you say N here, this device will still be supported, but without
381 config LOGIRUMBLEPAD2_FF
382 bool "Logitech force feedback support (variant 2)"
383 depends on HID_LOGITECH
384 select INPUT_FF_MEMLESS
386 Say Y here if you want to enable force feedback support for:
388 - Logitech Rumblepad 2
389 - Logitech Formula Vibration Feedback Wheel
392 bool "Logitech Flight System G940 force feedback support"
393 depends on HID_LOGITECH
394 select INPUT_FF_MEMLESS
396 Say Y here if you want to enable force feedback support for Logitech
397 Flight System G940 devices.
400 bool "Logitech wheels configuration and force feedback support"
401 depends on HID_LOGITECH
402 select INPUT_FF_MEMLESS
405 Say Y here if you want to enable force feedback and range setting
406 support for following Logitech wheels:
407 - Logitech Driving Force
408 - Logitech Driving Force Pro
409 - Logitech Driving Force GT
412 - Logitech MOMO/MOMO 2
413 - Logitech Formula Force EX
415 config HID_MAGICMOUSE
416 tristate "Apple Magic Mouse/Trackpad multi-touch support"
419 Support for the Apple Magic Mouse/Trackpad multi-touch.
421 Say Y here if you want support for the multi-touch features of the
422 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
425 tristate "Microsoft non-fully HID-compliant devices" if EXPERT
429 Support for Microsoft devices that are not fully compliant with HID standard.
432 tristate "Monterey Genius KB29E keyboard" if EXPERT
436 Support for Monterey Genius KB29E.
438 config HID_MULTITOUCH
439 tristate "HID Multitouch panels"
442 Generic support for HID multitouch panels.
444 Say Y here if you have one of the following devices:
445 - 3M PCT touch screens
446 - ActionStar dual touch panels
448 - Cando dual touch panels
451 - Cypress TrueTouch panels
452 - Elan Microelectronics touch panels
453 - Elo TouchSystems IntelliTouch Plus panels
454 - GeneralTouch 'Sensing Win7-TwoFinger' panels
456 - Hanvon dual touch panels
457 - Ilitek dual touch panels
458 - IrTouch Infrared USB panels
459 - LG Display panels (Dell ST2220Tc)
460 - Lumio CrystalTouch panels
461 - MosArt dual-touch panels
462 - Panasonic multitouch panels
463 - PenMount dual touch panels
464 - Perixx Peripad 701 touchpad
465 - PixArt optical touch screen
466 - Pixcir dual touch panels
468 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
469 - SiS multitouch panels
470 - Stantum multitouch panels
471 - Touch International Panels
473 - Wistron optical touch panels
474 - XAT optical touch panels
475 - Xiroku optical touch panels
476 - Zytronic touch panels
480 To compile this driver as a module, choose M here: the
481 module will be called hid-multitouch.
484 tristate "N-Trig touch screen"
487 Support for N-Trig touch screen.
490 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
493 There are certain devices which have LogicalMaximum wrong in the keyboard
494 usage page of their report descriptor. The most prevailing ones so far
495 are manufactured by Ortek, thus the name of the driver. Currently
496 supported devices by this driver are
500 - Skycable wireless presenter
502 config HID_PANTHERLORD
503 tristate "Pantherlord/GreenAsia game controller"
506 Say Y here if you have a PantherLord/GreenAsia based game controller
509 config PANTHERLORD_FF
510 bool "Pantherlord force feedback support"
511 depends on HID_PANTHERLORD
512 select INPUT_FF_MEMLESS
514 Say Y here if you have a PantherLord/GreenAsia based game controller
515 or adapter and want to enable force feedback support for it.
518 tristate "Petalynx Maxter remote control"
521 Support for Petalynx Maxter remote control.
524 tristate "PicoLCD (graphic version)"
527 This provides support for Minibox PicoLCD devices, currently
528 only the graphical ones are supported.
530 This includes support for the following device features:
532 - Switching between Firmware and Flash mode
533 - EEProm / Flash access (via debugfs)
534 Features selectively enabled:
535 - Framebuffer for monochrome 256x64 display
538 - General purpose outputs
539 Features that are not (yet) supported:
542 config HID_PICOLCD_FB
543 bool "Framebuffer support" if EXPERT
545 depends on HID_PICOLCD
546 depends on HID_PICOLCD=FB || FB=y
547 select FB_DEFERRED_IO
548 select FB_SYS_FILLRECT
549 select FB_SYS_COPYAREA
550 select FB_SYS_IMAGEBLIT
553 Provide access to PicoLCD's 256x64 monochrome display via a
556 config HID_PICOLCD_BACKLIGHT
557 bool "Backlight control" if EXPERT
559 depends on HID_PICOLCD
560 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
562 Provide access to PicoLCD's backlight control via backlight
565 config HID_PICOLCD_LCD
566 bool "Contrast control" if EXPERT
568 depends on HID_PICOLCD
569 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
571 Provide access to PicoLCD's LCD contrast via lcd class.
573 config HID_PICOLCD_LEDS
574 bool "GPO via leds class" if EXPERT
576 depends on HID_PICOLCD
577 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
579 Provide access to PicoLCD's GPO pins via leds class.
581 config HID_PICOLCD_CIR
582 bool "CIR via RC class" if EXPERT
584 depends on HID_PICOLCD
585 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
587 Provide access to PicoLCD's CIR interface via remote control (LIRC).
590 tristate "Primax non-fully HID-compliant devices"
593 Support for Primax devices that are not fully compliant with the
597 tristate "Roccat device support"
600 Support for Roccat devices.
601 Say Y here if you have a Roccat mouse or keyboard and want
602 support for its special functionalities.
605 tristate "Saitek non-fully HID-compliant devices"
608 Support for Saitek devices that are not fully compliant with the
612 - PS1000 Dual Analog Pad
613 - R.A.T.7 Gaming Mouse
614 - M.M.O.7 Gaming Mouse
617 tristate "Samsung InfraRed remote control or keyboards"
620 Support for Samsung InfraRed remote control or keyboards.
623 tristate "Sony PS2/3/4 accessories"
626 depends on LEDS_CLASS
631 * Sony PS3 6-axis controllers
632 * Sony PS4 DualShock 4 controllers
634 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
635 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
638 bool "Sony PS2/3/4 accessories force feedback support"
640 select INPUT_FF_MEMLESS
642 Say Y here if you have a Sony PS2/3/4 accessory and want to enable
643 force feedback support for it.
646 tristate "Speedlink VAD Cezanne mouse support"
649 Support for Speedlink Vicious and Divine Cezanne mouse.
651 config HID_STEELSERIES
652 tristate "Steelseries SRW-S1 steering wheel support"
655 Support for Steelseries SRW-S1 steering wheel
658 tristate "Sunplus wireless desktop"
661 Support for Sunplus wireless desktop.
664 tristate "Synaptics RMI4 device support"
667 Support for Synaptics RMI4 touchpads.
668 Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
669 and want support for its special functionalities.
672 tristate "GreenAsia (Product ID 0x12) game controller support"
675 Say Y here if you have a GreenAsia (Product ID 0x12) based game
676 controller or adapter.
679 bool "GreenAsia (Product ID 0x12) force feedback support"
680 depends on HID_GREENASIA
681 select INPUT_FF_MEMLESS
683 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
684 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
685 and want to enable force feedback support for it.
687 config HID_HYPERV_MOUSE
688 tristate "Microsoft Hyper-V mouse driver"
691 Select this option to enable the Hyper-V mouse driver.
693 config HID_SMARTJOYPLUS
694 tristate "SmartJoy PLUS PS2/USB adapter support"
697 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
698 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
700 Note that DDR (Dance Dance Revolution) mode is not supported, nor
701 is pressure sensitive buttons on the pro models.
703 config SMARTJOYPLUS_FF
704 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
705 depends on HID_SMARTJOYPLUS
706 select INPUT_FF_MEMLESS
708 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
709 enable force feedback support for it.
712 tristate "TiVo Slide Bluetooth remote control support"
715 Say Y if you have a TiVo Slide Bluetooth remote control.
718 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
721 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
722 CLLRCMCE remote control.
725 tristate "ThingM blink(1) USB RGB LED"
727 depends on LEDS_CLASS
729 Support for the ThingM blink(1) USB RGB LED. This driver registers a
730 Linux LED class instance, plus additional sysfs attributes to control
731 RGB colors, fade time and playing. The device is exposed through hidraw
732 to access other functions.
734 config HID_THRUSTMASTER
735 tristate "ThrustMaster devices support"
738 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
739 a THRUSTMASTER Ferrari GT Rumble Wheel.
741 config THRUSTMASTER_FF
742 bool "ThrustMaster devices force feedback support"
743 depends on HID_THRUSTMASTER
744 select INPUT_FF_MEMLESS
746 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
747 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
748 Rumble Force or Force Feedback Wheel.
751 tristate "Wacom Bluetooth devices support"
753 depends on LEDS_CLASS
756 Support for Wacom Graphire Bluetooth and Intuos4 WL tablets.
759 tristate "Wacom Intuos/Graphire tablet support (USB)"
765 Say Y here if you want to use the USB version of the Wacom Intuos
768 To compile this driver as a module, choose M here: the
769 module will be called wacom.
772 tristate "Nintendo Wii / Wii U peripherals"
774 depends on LEDS_CLASS
776 select INPUT_FF_MEMLESS
778 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
779 devices are the Wii Remote and its extension devices, but also devices
780 based on the Wii Remote like the Wii U Pro Controller or the
783 Support for all official Nintendo extensions is available, however, 3rd
784 party extensions might not be supported. Please report these devices to:
785 http://github.com/dvdhrm/xwiimote/issues
787 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
788 the Wii U Gamepad) might be supported in the future. But currently
789 support is limited to Bluetooth based devices.
793 To compile this driver as a module, choose M here: the
794 module will be called hid-wiimote.
797 tristate "Xin-Mo non-fully compliant devices"
800 Support for Xin-Mo devices that are not fully compliant with the HID
801 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
802 if you have a Xin-Mo Dual Arcade controller.
805 tristate "Zeroplus based game controller support"
808 Say Y here if you have a Zeroplus based game controller.
811 bool "Zeroplus based game controller force feedback support"
812 depends on HID_ZEROPLUS
813 select INPUT_FF_MEMLESS
815 Say Y here if you have a Zeroplus based game controller and want
816 to have force feedback support for it.
819 tristate "Zydacron remote control support"
822 Support for Zydacron remote control.
824 config HID_SENSOR_HUB
825 tristate "HID Sensors framework support"
826 depends on HID && HAS_IOMEM
830 Support for HID Sensor framework. This creates a MFD instance
831 for a sensor hub and identifies all the sensors connected to it.
832 Each sensor is registered as a MFD cell, so that sensor specific
833 processing can be done in a separate driver. Each sensor
834 drivers can use the service provided by this driver to register
835 for events and handle data streams. Each sensor driver can format
836 data and present to user mode using input or IIO interface.
842 source "drivers/hid/usbhid/Kconfig"
844 source "drivers/hid/i2c-hid/Kconfig"