1 # SPDX-License-Identifier: GPL-2.0-only
3 # HID driver configuration
10 This option adds core support for human interface device (HID).
11 You will also need drivers from the following menu to make use of it.
16 tristate "HID bus core support"
20 A human interface device (HID) is a type of computer device that
21 interacts directly with and takes input from humans. The term "HID"
22 most commonly used to refer to the USB-HID specification, but other
23 devices (such as, but not strictly limited to, Bluetooth) are
24 designed using HID specification (this involves certain keyboards,
25 mice, tablets, etc). This option adds the HID bus to the kernel,
26 together with generic HID layer code. The HID devices are added and
27 removed from the HID bus by the transport-layer drivers, such as
28 usbhid (USB_HID) and hidp (BT_HIDP).
30 For docs and specs, see https://www.usb.org/developers/hidpage/
36 config HID_BATTERY_STRENGTH
37 bool "Battery level reporting for HID devices"
41 This option adds support of reporting battery strength (for HID devices
42 that support this feature) through power_supply class so that userspace
43 tools, such as upower, can display it.
46 bool "/dev/hidraw raw HID device support"
48 Say Y here if you want to support HID devices (from the USB
49 specification standpoint) that aren't strictly user interface
50 devices, like monitor controls and Uninterruptible Power Supplies.
52 This module supports these devices separately using a separate
53 event interface on /dev/hidraw.
55 There is also a /dev/hiddev configuration option in the USB HID
56 configuration menu. In comparison to hiddev, this device does not process
57 the hid events at all (no parsing, no lookups). This lets applications
58 to work on raw hid events when they want to, and avoid using transport-specific
59 userspace libhid/libusb libraries.
64 tristate "User-space I/O driver support for HID subsystem"
67 Say Y here if you want to provide HID I/O Drivers from user-space.
68 This allows to write I/O drivers in user-space and feed the data from
69 the device into the kernel. The kernel parses the HID reports, loads the
70 corresponding HID Device Driver or provides input devices on top of your
73 This driver cannot be used to parse HID-reports in user-space and write
74 special HID-drivers. You should use hidraw for that.
75 Instead, this driver allows to write the transport-layer driver in
76 user-space like USB-HID and Bluetooth-HID do in kernel-space.
80 To compile this driver as a module, choose M here: the
81 module will be called uhid.
84 tristate "Generic HID driver"
87 Support for generic devices on the HID bus. This includes most
88 keyboards and mice, joysticks, tablets and digitizers.
90 To compile this driver as a module, choose M here: the module
91 will be called hid-generic.
95 menu "Special HID drivers"
98 tristate "A4TECH mice"
101 Support for some A4TECH mice with two scroll wheels.
104 tristate "Accutouch touch device"
107 This selects a driver for the Accutouch 2216 touch controller.
109 The driver works around a problem in the reported device capabilities
110 which causes userspace to detect the device as a mouse rather than
113 Say Y here if you have a Accutouch 2216 touch controller.
116 tristate "ACRUX game controller support"
118 Say Y here if you want to enable support for ACRUX game controllers.
121 bool "ACRUX force feedback support"
123 select INPUT_FF_MEMLESS
125 Say Y here if you want to enable force feedback support for ACRUX
129 tristate "Apple {i,Power,Mac}Books"
130 depends on LEDS_CLASS
134 Support for some Apple devices which less or more break
137 Say Y here if you want support for keyboards of Apple iBooks, PowerBooks,
138 MacBooks, MacBook Pros and Apple Aluminum.
141 tristate "Apple infrared receiver"
144 Support for Apple infrared remote control. All the Apple computers from
145 2005 onwards include such a port, except the unibody Macbook (2009),
146 and Mac Pros. This receiver is also used in the Apple TV set-top box
147 prior to the 2010 model.
149 Say Y here if you want support for Apple infrared remote control.
154 depends on LEDS_CLASS
155 depends on ASUS_WMI || ASUS_WMI=n
158 Support for Asus notebook built-in keyboard and touchpad via i2c, and
159 the Asus Republic of Gamers laptop keyboard special keys.
170 Support for Aureal Cy se W-01RN Remote Controller and other Aureal derived remotes.
173 tristate "Belkin Flip KVM and Wireless keyboard"
176 Support for Belkin Flip KVM and Wireless keyboard.
179 tristate "Betop Production Inc. force feedback support"
181 select INPUT_FF_MEMLESS
183 Say Y here if you want to enable force feedback support for devices by
184 BETOP Production Ltd.
185 Currently the following devices are known to be supported:
186 - BETOP 2185 PC & BFM MODE
189 tristate "BigBen Interactive Kids' gamepad support"
192 depends on LEDS_CLASS
193 select INPUT_FF_MEMLESS
195 Support for the "Kid-friendly Wired Controller" PS3OFMINIPAD
196 gamepad made by BigBen Interactive, originally sold as a PS3
197 accessory. This driver fixes input mapping and adds support for
198 force feedback effects and LEDs on the device.
201 tristate "Cherry Cymotion keyboard"
204 Support for Cherry Cymotion keyboard.
207 tristate "Chicony devices"
211 Support for Chicony Tactical pad and special keys on Chicony keyboards.
214 tristate "Corsair devices"
215 depends on USB_HID && LEDS_CLASS
218 Support for Corsair devices that are not fully compliant with the
220 Support for Corsair Void headsets.
225 - Corsair Void headsets
228 tristate "Cougar devices"
230 Support for Cougar devices that are not fully compliant with the
234 - Cougar 500k Gaming Keyboard
237 tristate "Macally devices"
239 Support for Macally devices that are not fully compliant with the
243 - Macally ikey keyboard
246 tristate "Prodikeys PC-MIDI Keyboard support"
247 depends on USB_HID && SND
250 Support for Prodikeys PC-MIDI Keyboard device support.
251 Say Y here to enable support for this device.
252 - Prodikeys PC-MIDI keyboard.
253 The Prodikeys PC-MIDI acts as a USB Audio device, with one MIDI
254 input and one MIDI output. These MIDI jacks appear as
255 a sound "card" in the ALSA sound system.
256 Note: if you say N here, this device will still function as a basic
257 multimedia keyboard, but will lack support for the musical keyboard
258 and some additional multimedia keys.
261 tristate "CMedia audio chips"
263 Support for CMedia CM6533 HID audio jack controls
264 and HS100B mute buttons.
267 tristate "Silicon Labs CP2112 HID USB-to-SMBus Bridge support"
268 depends on USB_HID && HIDRAW && I2C && GPIOLIB
269 select GPIOLIB_IRQCHIP
271 Support for Silicon Labs CP2112 HID USB to SMBus Master Bridge.
272 This is a HID device driver which registers as an i2c adapter
273 and gpiochip to expose these functions of the CP2112. The
274 customizable USB descriptor fields are exposed as sysfs attributes.
276 config HID_CREATIVE_SB0540
277 tristate "Creative SB0540 infrared receiver"
280 Support for Creative infrared SB0540-compatible remote controls, such
281 as the RM-1500 and RM-1800 remotes.
283 Say Y here if you want support for Creative SB0540 infrared receiver.
286 tristate "Cypress mouse and barcode readers"
289 Support for cypress mouse and barcode readers.
291 config HID_DRAGONRISE
292 tristate "DragonRise Inc. game controller"
294 Say Y here if you have DragonRise Inc. game controllers.
295 These might be branded as:
297 - Media-tech MT1504 "Rogue"
299 - Defender Game Master
302 bool "DragonRise Inc. force feedback"
303 depends on HID_DRAGONRISE
304 select INPUT_FF_MEMLESS
306 Say Y here if you want to enable force feedback support for DragonRise Inc.
310 tristate "EMS Production Inc. force feedback support"
311 select INPUT_FF_MEMLESS
313 Say Y here if you want to enable force feedback support for devices by
315 Currently the following devices are known to be supported:
316 - Trio Linker Plus II
319 tristate "ELAN USB Touchpad Support"
320 depends on LEDS_CLASS && USB_HID
322 Say Y to enable support for the USB ELAN touchpad
323 Currently the following devices are known to be supported:
324 - HP Pavilion X2 10-p0XX.
327 tristate "ELECOM HID devices"
329 Support for ELECOM devices:
330 - BM084 Bluetooth Mouse
331 - EX-G Trackballs (M-XT3DRBK, M-XT3URBK)
332 - DEFT Trackballs (M-DT1DRBK, M-DT1URBK, M-DT2DRBK, M-DT2URBK)
333 - HUGE Trackballs (M-HT1DRBK, M-HT1URBK)
336 tristate "ELO USB 4000/4500 touchscreen"
339 Support for the ELO USB 4000/4500 touchscreens. Note that this is for
340 different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
343 tristate "EVision Keyboards Support"
346 Support for some EVision keyboards. Note that this is needed only when
347 applying customization using userspace programs.
350 tristate "Ezkey BTC 8193 keyboard"
353 Support for Ezkey BTC 8193 keyboard.
356 tristate "FTDI FT260 USB HID to I2C host support"
357 depends on USB_HID && HIDRAW && I2C
359 Provides I2C host adapter functionality over USB-HID through FT260
360 device. The customizable USB descriptor fields are exposed as sysfs
363 To compile this driver as a module, choose M here: the module
364 will be called hid-ft260.
367 tristate "Gembird Joypad"
369 Support for Gembird JPD-DualForce 2.
372 tristate "Google Fiber TV Box remote control support"
374 Support for Google Fiber TV Box remote controls
377 tristate "Glorious PC Gaming Race mice"
379 Support for Glorious PC Gaming Race mice such as
380 the Glorious Model O, O- and D.
383 tristate "Holtek HID devices"
386 Support for Holtek based devices:
387 - Holtek On Line Grip based game controller
388 - Trust GXT 18 Gaming Keyboard
389 - Sharkoon Drakonia / Perixx MX-2000 gaming mice
390 - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
392 - SHARKOON DarkGlider Gaming mouse
393 - LEETGION Hellion Gaming Mouse
396 bool "Holtek On Line Grip force feedback support"
397 depends on HID_HOLTEK
398 select INPUT_FF_MEMLESS
400 Say Y here if you have a Holtek On Line Grip based game controller
401 and want to have force feedback support for it.
403 config HID_VIVALDI_COMMON
406 ChromeOS Vivaldi HID parsing support library. This is a hidden
407 option so that drivers can use common code to parse the HID
408 descriptors for vivaldi function row keymap.
410 config HID_GOODIX_SPI
411 tristate "Goodix GT7986U SPI HID touchscreen"
412 depends on SPI_MASTER
414 Support for Goodix GT7986U SPI HID touchscreen device.
416 config HID_GOOGLE_HAMMER
417 tristate "Google Hammer Keyboard"
418 select HID_VIVALDI_COMMON
419 select INPUT_VIVALDIFMAP
420 depends on USB_HID && LEDS_CLASS && CROS_EC
422 Say Y here if you have a Google Hammer device.
424 config HID_GOOGLE_STADIA_FF
425 tristate "Google Stadia force feedback"
426 select INPUT_FF_MEMLESS
428 Say Y here if you want to enable force feedback support for the Google
432 tristate "Vivaldi Keyboard"
433 select HID_VIVALDI_COMMON
434 select INPUT_VIVALDIFMAP
436 Say Y here if you want to enable support for Vivaldi keyboards.
438 Vivaldi keyboards use a vendor-specific (Google) HID usage to report
439 how the keys in the top row are physically ordered.
442 tristate "MSI GT68xR LED support"
443 depends on LEDS_CLASS && USB_HID
445 Say Y here if you want to enable support for the three MSI GT68xR LEDs
447 This driver support following modes:
448 - Normal: LEDs are fully on when enabled
449 - Audio: LEDs brightness depends on sound level
450 - Breathing: LEDs brightness varies at human breathing rate
452 Currently the following devices are know to be supported:
456 tristate "Keytouch HID devices"
458 Support for Keytouch HID devices not fully compliant with
459 the specification. Currently supported:
463 tristate "KYE/Genius devices"
465 Support for KYE/Genius devices not fully compliant with HID standard:
467 - EasyPen i405X tablet
468 - MousePen i608X tablet
469 - EasyPen M610X tablet
472 tristate "Kysona devices"
475 Support for Kysona mice.
477 Say Y here if you have a Kysona M600 mouse
478 and want to be able to read its battery capacity.
484 Support for UC-Logic and Huion tablets.
489 Support for Waltop tablets.
492 tristate "ViewSonic/Signotec"
494 Support for ViewSonic/Signotec PD1011 signature pad.
497 tristate "VRC-2 Car Controller"
500 Support for VRC-2 which is a 2-axis controller often used in
503 To compile this driver as a module, choose M here: the
504 module will be called hid-vrc2.
509 Adds support for side buttons of Xiaomi Mi Dual Mode Wireless
510 Mouse Silent Edition.
513 tristate "Gyration remote control"
515 Support for Gyration remote control.
518 tristate "ION iCade arcade controller"
520 Support for the ION iCade arcade controller to work as a joystick.
522 To compile this driver as a module, choose M here: the
523 module will be called hid-icade.
526 tristate "ITE devices"
529 Support for ITE devices not fully compliant with HID standard.
532 tristate "Jabra USB HID Driver"
534 Support for Jabra USB HID devices.
536 Prevents mapping of vendor defined HID usages to input events. Without
537 this driver HID reports from Jabra devices may incorrectly be seen as
539 Say M here if you may ever plug in a Jabra USB device.
542 tristate "Twinhan IR remote control"
544 Support for Twinhan IR remote control.
546 config HID_KENSINGTON
547 tristate "Kensington Slimblade Trackball"
550 Support for Kensington Slimblade Trackball.
555 Support for LC-Power RC1000MCE RF remote control.
558 tristate "Simple RGB LED support"
559 depends on LEDS_CLASS
561 Support for simple RGB LED devices. Currently supported are:
562 - Riso Kagaku Webmail Notifier
563 - Dream Cheeky Webmail Notifier and Friends Alert
565 - Delcom Visual Signal Indicator Generation 2
568 To compile this driver as a module, choose M here: the
569 module will be called hid-led.
572 tristate "Lenovo / Thinkpad devices"
574 select ACPI_PLATFORM_PROFILE
578 Support for IBM/Lenovo devices that are not fully compliant with HID standard.
580 Say Y if you want support for horizontal scrolling of the IBM/Lenovo
581 Scrollpoint mice or the non-compliant features of the Lenovo Thinkpad
582 standalone keyboards, e.g:
583 - ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
585 - ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
586 - ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
589 tristate "Letsketch WP9620N tablets"
592 Driver for the LetSketch / VSON WP9620N drawing tablet. This
593 drawing tablet is also sold under other brand names such as Case U,
594 presumably this driver will work for all of them. But it has only been
595 tested with a LetSketch WP9620N model.
597 These tablets also work without a special HID driver, but then only
598 part of the active area works and both the pad and stylus buttons are
599 hardwired to special key-combos. E.g. the 2 stylus buttons send right
600 mouse clicks / resp. "e" key presses.
603 tristate "Logitech devices"
605 depends on LEDS_CLASS
608 Support for Logitech devices that are not fully compliant with HID standard.
610 config HID_LOGITECH_DJ
611 tristate "Logitech receivers full support"
614 depends on HID_LOGITECH
615 select HID_LOGITECH_HIDPP
617 Say Y if you want support for Logitech receivers and devices.
618 Logitech receivers are capable of pairing multiple Logitech compliant
619 devices to the same receiver. Without this driver it will be handled by
620 generic USB_HID driver and all incoming events will be multiplexed
621 into a single mouse and a single keyboard device.
623 config HID_LOGITECH_HIDPP
624 tristate "Logitech HID++ devices support"
625 depends on HID_LOGITECH
628 Support for Logitech devices relying on the HID++ Logitech specification
630 Say Y if you want support for Logitech devices relying on the HID++
631 specification. Such devices are the various Logitech Touchpads (T650,
632 T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
636 bool "Logitech force feedback support"
637 depends on HID_LOGITECH
638 select INPUT_FF_MEMLESS
640 Say Y here if you have one of these devices:
641 - Logitech WingMan Cordless RumblePad
642 - Logitech WingMan Cordless RumblePad 2
643 - Logitech WingMan Force 3D
645 and if you want to enable force feedback for them.
646 Note: if you say N here, this device will still be supported, but without
649 config LOGIRUMBLEPAD2_FF
650 bool "Logitech force feedback support (variant 2)"
651 depends on HID_LOGITECH
652 select INPUT_FF_MEMLESS
654 Say Y here if you want to enable force feedback support for:
656 - Logitech Rumblepad 2
657 - Logitech Formula Vibration Feedback Wheel
660 bool "Logitech Flight System G940 force feedback support"
661 depends on HID_LOGITECH
662 select INPUT_FF_MEMLESS
664 Say Y here if you want to enable force feedback support for Logitech
665 Flight System G940 devices.
668 bool "Logitech wheels configuration and force feedback support"
669 depends on HID_LOGITECH
670 select INPUT_FF_MEMLESS
673 Say Y here if you want to enable force feedback and range setting(*)
674 support for following Logitech wheels:
678 - Logitech Driving Force
679 - Logitech Driving Force Pro (*)
680 - Logitech Driving Force GT (*)
681 - Logitech Driving Force EX/RX
682 - Logitech Driving Force Wireless
683 - Logitech Speed Force Wireless
684 - Logitech MOMO Force
685 - Logitech MOMO Racing Force
686 - Logitech Formula Force GP
687 - Logitech Formula Force EX/RX
688 - Logitech Wingman Formula Force GP
690 config HID_MAGICMOUSE
691 tristate "Apple Magic Mouse/Trackpad multi-touch support"
693 Support for the Apple Magic Mouse/Trackpad multi-touch.
695 Say Y here if you want support for the multi-touch features of the
696 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
699 tristate "Maltron L90 keyboard"
701 Adds support for the volume up, volume down, mute, and play/pause buttons
702 of the Maltron L90 keyboard.
705 tristate "Mayflash game controller adapter force feedback"
706 select INPUT_FF_MEMLESS
708 Say Y here if you have HJZ Mayflash PS3 game controller adapters
709 and want to enable force feedback support.
711 config HID_MEGAWORLD_FF
712 tristate "Mega World based game controller force feedback support"
714 select INPUT_FF_MEMLESS
716 Say Y here if you have a Mega World based game controller and want
717 to have force feedback support for it.
720 tristate "Redragon keyboards"
723 Support for Redragon keyboards that need fix-ups to work properly.
726 tristate "Microsoft non-fully HID-compliant devices"
728 select INPUT_FF_MEMLESS
730 Support for Microsoft devices that are not fully compliant with HID standard.
733 tristate "Monterey Genius KB29E keyboard"
736 Support for Monterey Genius KB29E.
738 config HID_MULTITOUCH
739 tristate "HID Multitouch panels"
741 Generic support for HID multitouch panels.
743 Say Y here if you have one of the following devices:
744 - 3M PCT touch screens
745 - ActionStar dual touch panels
747 - Cando dual touch panels
751 - Cypress TrueTouch panels
752 - Elan Microelectronics touch panels
753 - Elo TouchSystems IntelliTouch Plus panels
754 - GeneralTouch 'Sensing Win7-TwoFinger' panels
756 - Hanvon dual touch panels
757 - Ilitek dual touch panels
758 - IrTouch Infrared USB panels
759 - LG Display panels (Dell ST2220Tc)
760 - Lumio CrystalTouch panels
761 - MosArt dual-touch panels
762 - Panasonic multitouch panels
763 - PenMount dual touch panels
764 - Perixx Peripad 701 touchpad
765 - PixArt optical touch screen
766 - Pixcir dual touch panels
768 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
769 - SiS multitouch panels
770 - Stantum multitouch panels
771 - Touch International Panels
773 - Wistron optical touch panels
774 - XAT optical touch panels
775 - Xiroku optical touch panels
776 - Zytronic touch panels
780 To compile this driver as a module, choose M here: the
781 module will be called hid-multitouch.
784 tristate "Nintendo Joy-Con, NSO, and Pro Controller support"
786 depends on LEDS_CLASS
789 Adds support for the Nintendo Switch Joy-Cons, NSO, Pro Controller.
790 All controllers support bluetooth, and the Pro Controller also supports
791 its USB mode. This also includes support for the Nintendo Switch Online
792 Controllers which include the NES, Genesis, SNES, and N64 controllers.
794 To compile this driver as a module, choose M here: the
795 module will be called hid-nintendo.
798 bool "Nintendo Switch controller force feedback support"
799 depends on HID_NINTENDO
800 select INPUT_FF_MEMLESS
802 Say Y here if you have a Nintendo Switch controller and want to enable
803 force feedback support for it. This works for both joy-cons, the pro
804 controller, and the NSO N64 controller. For the pro controller, both
805 rumble motors can be controlled individually.
808 tristate "NTI keyboard adapters"
810 Support for the "extra" Sun keyboard keys on keyboards attached
811 through Network Technologies USB-SUN keyboard adapters.
814 tristate "N-Trig touch screen"
817 Support for N-Trig touch screen.
819 config HID_NVIDIA_SHIELD
820 tristate "NVIDIA SHIELD devices"
823 depends on LEDS_CLASS
826 Support for NVIDIA SHIELD accessories.
829 - Thunderstrike (NVIDIA SHIELD Controller 2017)
831 config NVIDIA_SHIELD_FF
832 bool "NVIDIA SHIELD force feedback support"
833 depends on HID_NVIDIA_SHIELD
834 select INPUT_FF_MEMLESS
836 Say Y here if you would like to enable force feedback support for
837 NVIDIA SHIELD accessories with haptics capabilities.
840 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
842 There are certain devices which have LogicalMaximum wrong in the keyboard
843 usage page of their report descriptor. The most prevailing ones so far
844 are manufactured by Ortek, thus the name of the driver. Currently
845 supported devices by this driver are
849 - Skycable wireless presenter
851 config HID_PANTHERLORD
852 tristate "Pantherlord/GreenAsia game controller"
854 Say Y here if you have a PantherLord/GreenAsia based game controller
857 config PANTHERLORD_FF
858 bool "Pantherlord force feedback support"
859 depends on HID_PANTHERLORD
860 select INPUT_FF_MEMLESS
862 Say Y here if you have a PantherLord/GreenAsia based game controller
863 or adapter and want to enable force feedback support for it.
866 tristate "Penmount touch device"
869 This selects a driver for the PenMount 6000 touch controller.
871 The driver works around a problem in the report descript allowing
872 the userspace to touch events instead of mouse events.
874 Say Y here if you have a Penmount based touch controller.
877 tristate "Petalynx Maxter remote control"
879 Support for Petalynx Maxter remote control.
882 tristate "PicoLCD (graphic version)"
884 This provides support for Minibox PicoLCD devices, currently
885 only the graphical ones are supported.
887 This includes support for the following device features:
889 - Switching between Firmware and Flash mode
890 - EEProm / Flash access (via debugfs)
891 Features selectively enabled:
892 - Framebuffer for monochrome 256x64 display
895 - General purpose outputs
896 Features that are not (yet) supported:
899 config HID_PICOLCD_FB
900 bool "Framebuffer support" if EXPERT
902 depends on HID_PICOLCD
903 depends on HID_PICOLCD=FB || FB=y
904 select FB_SYSMEM_HELPERS_DEFERRED
906 Provide access to PicoLCD's 256x64 monochrome display via a
909 config HID_PICOLCD_BACKLIGHT
910 bool "Backlight control" if EXPERT
912 depends on HID_PICOLCD
913 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
915 Provide access to PicoLCD's backlight control via backlight
918 config HID_PICOLCD_LCD
919 bool "Contrast control" if EXPERT
921 depends on HID_PICOLCD
922 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
924 Provide access to PicoLCD's LCD contrast via lcd class.
926 config HID_PICOLCD_LEDS
927 bool "GPO via leds class" if EXPERT
929 depends on HID_PICOLCD
930 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
932 Provide access to PicoLCD's GPO pins via leds class.
934 config HID_PICOLCD_CIR
935 bool "CIR via RC class" if EXPERT
937 depends on HID_PICOLCD
938 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
940 Provide access to PicoLCD's CIR interface via remote control (LIRC).
942 config HID_PLANTRONICS
943 tristate "Plantronics USB HID Driver"
945 Provides HID support for Plantronics USB audio devices.
946 Correctly maps vendor unique volume up/down HID usages to
947 KEY_VOLUMEUP and KEY_VOLUMEDOWN events and prevents core mapping
948 of other vendor unique HID usages to random mouse events.
950 Say M here if you may ever plug in a Plantronics USB audio device.
952 config HID_PLAYSTATION
953 tristate "PlayStation HID Driver"
954 depends on LEDS_CLASS_MULTICOLOR
958 Provides support for Sony PS4/PS5 controllers including support for
959 its special functionalities e.g. touchpad, lights and motion
962 config PLAYSTATION_FF
963 bool "PlayStation force feedback support"
964 depends on HID_PLAYSTATION
965 select INPUT_FF_MEMLESS
967 Say Y here if you would like to enable force feedback support for
968 PlayStation game controllers.
971 tristate "PhoenixRC HID Flight Controller"
974 Support for PhoenixRC HID Flight Controller, a 8-axis flight controller.
976 To compile this driver as a module, choose M here: the
977 module will be called hid-pxrc.
980 tristate "Razer non-fully HID-compliant devices"
982 Support for Razer devices that are not fully compliant with the
986 tristate "Primax non-fully HID-compliant devices"
988 Support for Primax devices that are not fully compliant with the
992 tristate "Retrode 2 USB adapter for vintage video games"
996 * Retrode 2 cartridge and controller adapter
999 tristate "Roccat device support"
1002 Support for Roccat devices.
1003 Say Y here if you have a Roccat mouse or keyboard and want
1004 support for its special functionalities.
1007 tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
1009 Support for Saitek devices that are not fully compliant with the
1013 - PS1000 Dual Analog Pad
1014 - Saitek R.A.T.7, R.A.T.9, M.M.O.7 Gaming Mice
1015 - Mad Catz R.A.T.5, R.A.T.9 Gaming Mice
1018 tristate "Samsung InfraRed remote control or keyboards"
1021 Support for Samsung InfraRed remote control or keyboards.
1024 tristate "Semitek USB keyboards"
1026 Support for Semitek USB keyboards that are not fully compliant
1027 with the HID standard.
1029 There are many variants, including:
1030 - GK61, GK64, GK68, GK84, GK96, etc.
1031 - SK61, SK64, SK68, SK84, SK96, etc.
1035 - X-Bows Nature/Knight
1037 config HID_SIGMAMICRO
1038 tristate "SiGma Micro-based keyboards"
1041 Support for keyboards that use the SiGma Micro (a.k.a SigmaChip) IC.
1048 tristate "Sony PS2/3/4 accessories"
1051 depends on LEDS_CLASS
1057 * Sony PS3 6-axis controllers
1058 * Sony PS4 DualShock 4 controllers
1060 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
1061 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
1062 * Guitar Hero Live PS3, Wii U and PS4 guitar dongles
1063 * Guitar Hero PS3 and PC guitar dongles
1066 bool "Sony PS2/3/4 accessories force feedback support"
1068 select INPUT_FF_MEMLESS
1070 Say Y here if you have a Sony PS2/3/4 accessory and want to enable
1071 force feedback support for it.
1073 config HID_SPEEDLINK
1074 tristate "Speedlink VAD Cezanne mouse support"
1076 Support for Speedlink Vicious and Divine Cezanne mouse.
1079 tristate "Steam Controller/Deck support"
1082 Say Y here if you have a Steam Controller or Deck if you want to use it
1083 without running the Steam Client. It supports both the wired and
1084 the wireless adaptor.
1087 bool "Steam Deck force feedback support"
1088 depends on HID_STEAM
1089 select INPUT_FF_MEMLESS
1091 Say Y here if you want to enable force feedback support for the Steam
1094 config HID_STEELSERIES
1095 tristate "Steelseries devices support"
1098 Support for Steelseries SRW-S1 steering wheel, and the Steelseries
1099 Arctis 1 Wireless for XBox headset.
1102 tristate "Sunplus wireless desktop"
1104 Support for Sunplus wireless desktop.
1107 tristate "Synaptics RMI4 device support"
1115 Support for Synaptics RMI4 touchpads.
1116 Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
1117 and want support for its special functionalities.
1119 config HID_GREENASIA
1120 tristate "GreenAsia (Product ID 0x12) game controller support"
1122 Say Y here if you have a GreenAsia (Product ID 0x12) based game
1123 controller or adapter.
1126 bool "GreenAsia (Product ID 0x12) force feedback support"
1127 depends on HID_GREENASIA
1128 select INPUT_FF_MEMLESS
1130 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
1131 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
1132 and want to enable force feedback support for it.
1134 config HID_HYPERV_MOUSE
1135 tristate "Microsoft Hyper-V mouse driver"
1138 Select this option to enable the Hyper-V mouse driver.
1140 config HID_SMARTJOYPLUS
1141 tristate "SmartJoy PLUS PS2/USB adapter support"
1143 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
1144 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
1146 Note that DDR (Dance Dance Revolution) mode is not supported, nor
1147 is pressure sensitive buttons on the pro models.
1149 config SMARTJOYPLUS_FF
1150 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
1151 depends on HID_SMARTJOYPLUS
1152 select INPUT_FF_MEMLESS
1154 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
1155 enable force feedback support for it.
1158 tristate "TiVo Slide Bluetooth remote control support"
1160 Say Y if you have a TiVo Slide Bluetooth remote control.
1163 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
1165 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
1166 CLLRCMCE remote control.
1169 tristate "Topre REALFORCE keyboards"
1172 Say Y for N-key rollover support on Topre REALFORCE R2 108/87 key and
1173 Topre REALFORCE R3S 87 key keyboards.
1176 tristate "ThingM blink(1) USB RGB LED"
1177 depends on LEDS_CLASS
1180 Support for the ThingM blink(1) USB RGB LED. This driver has been
1181 merged into the generic hid led driver. Config symbol HID_THINGM
1182 just selects HID_LED and will be removed soon.
1184 config HID_THRUSTMASTER
1185 tristate "ThrustMaster devices support"
1188 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2,
1189 a THRUSTMASTER Ferrari GT Rumble Wheel or Thrustmaster FFB
1190 Wheel (T150RS, T300RS, T300 Ferrari Alcantara Edition, T500RS).
1192 config THRUSTMASTER_FF
1193 bool "ThrustMaster devices force feedback support"
1194 depends on HID_THRUSTMASTER
1195 select INPUT_FF_MEMLESS
1197 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
1198 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
1199 Rumble Force or Force Feedback Wheel.
1201 config HID_UDRAW_PS3
1202 tristate "THQ PS3 uDraw tablet"
1204 Say Y here if you want to use the THQ uDraw gaming tablet for
1208 tristate "U2F Zero LED and RNG support"
1210 depends on LEDS_CLASS
1211 depends on HW_RANDOM
1213 Support for the LED of the U2F Zero device.
1215 U2F Zero supports custom commands for blinking the LED
1216 and getting data from the internal hardware RNG.
1217 The internal hardware can be used to feed the enthropy pool.
1219 U2F Zero only supports blinking its LED, so this driver doesn't
1220 allow setting the brightness to anything but 1, which will
1221 trigger a single blink and immediately reset back to 0.
1224 tristate "Wacom Intuos/Graphire tablet support (USB)"
1229 select LEDS_TRIGGERS
1231 Say Y here if you want to use the USB or BT version of the Wacom Intuos
1234 To compile this driver as a module, choose M here: the
1235 module will be called wacom.
1238 tristate "Nintendo Wii / Wii U peripherals"
1239 depends on LEDS_CLASS
1241 select INPUT_FF_MEMLESS
1243 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
1244 devices are the Wii Remote and its extension devices, but also devices
1245 based on the Wii Remote like the Wii U Pro Controller or the
1248 Support for all official Nintendo extensions is available, however, 3rd
1249 party extensions might not be supported. Please report these devices to:
1250 http://github.com/dvdhrm/xwiimote/issues
1252 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
1253 the Wii U Gamepad) might be supported in the future. But currently
1254 support is limited to Bluetooth based devices.
1258 To compile this driver as a module, choose M here: the
1259 module will be called hid-wiimote.
1262 tristate "WinWing Orion2 throttle support"
1265 depends on LEDS_CLASS
1267 Support for WinWing Orion2 throttle base with the following grips:
1272 This driver enables all buttons and switches on the throttle base.
1274 To compile this driver as a module, choose M here: the
1275 module will be called hid-winwing.
1278 tristate "Xin-Mo non-fully compliant devices"
1280 Support for Xin-Mo devices that are not fully compliant with the HID
1281 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
1282 if you have a Xin-Mo Dual Arcade controller.
1285 tristate "Zeroplus based game controller support"
1287 Say Y here if you have a Zeroplus based game controller.
1290 bool "Zeroplus based game controller force feedback support"
1291 depends on HID_ZEROPLUS
1292 select INPUT_FF_MEMLESS
1294 Say Y here if you have a Zeroplus based game controller and want
1295 to have force feedback support for it.
1298 tristate "Zydacron remote control support"
1300 Support for Zydacron remote control.
1302 config HID_SENSOR_HUB
1303 tristate "HID Sensors framework support"
1304 depends on HAS_IOMEM
1308 Support for HID Sensor framework. This creates a MFD instance
1309 for a sensor hub and identifies all the sensors connected to it.
1310 Each sensor is registered as a MFD cell, so that sensor specific
1311 processing can be done in a separate driver. Each sensor
1312 drivers can use the service provided by this driver to register
1313 for events and handle data streams. Each sensor driver can format
1314 data and present to user mode using input or IIO interface.
1316 config HID_SENSOR_CUSTOM_SENSOR
1317 tristate "HID Sensors hub custom sensor support"
1318 depends on HID_SENSOR_HUB
1321 HID Sensor hub specification allows definition of some custom and
1322 generic sensors. Unlike other HID sensors, they can't be exported
1323 via Linux IIO because of custom fields. This is up to the manufacturer
1324 to decide how to interpret these special sensor ids and process in
1325 the user space. Currently some manufacturers are using these ids for
1326 sensor calibration and debugging other sensors. Manufacturers
1327 shouldn't use these special custom sensor ids to export any of the
1329 Select this config option for custom/generic sensor support.
1332 tristate "Alps HID device support"
1334 Support for Alps I2C HID touchpads and StickPointer.
1335 Say Y here if you have a Alps touchpads over i2c-hid or usbhid
1336 and want support for its special functionalities.
1339 tristate "Microchip MCP2200 HID USB-to-GPIO bridge"
1340 depends on USB_HID && GPIOLIB
1342 Provides GPIO functionality over USB-HID through MCP2200 device.
1344 To compile this driver as a module, choose M here: the module
1345 will be called hid-mcp2200.ko.
1348 tristate "Microchip MCP2221 HID USB-to-I2C/SMbus host support"
1349 depends on USB_HID && I2C
1353 Provides I2C and SMBUS host adapter functionality over USB-HID
1354 through MCP2221 device.
1356 To compile this driver as a module, choose M here: the module
1357 will be called hid-mcp2221.ko.
1359 config HID_KUNIT_TEST
1360 tristate "KUnit tests for HID" if !KUNIT_ALL_TESTS
1362 depends on HID_BATTERY_STRENGTH
1363 depends on HID_UCLOGIC
1364 default KUNIT_ALL_TESTS
1366 This builds unit tests for HID. This option is not useful for
1367 distributions or general kernels, but only for kernel
1368 developers working on HID and associated drivers.
1370 For more information on KUnit and unit tests in general,
1371 please refer to the KUnit documentation in
1372 Documentation/dev-tools/kunit/.
1374 If in doubt, say "N".
1378 source "drivers/hid/bpf/Kconfig"
1380 source "drivers/hid/i2c-hid/Kconfig"
1382 source "drivers/hid/intel-ish-hid/Kconfig"
1384 source "drivers/hid/amd-sfh-hid/Kconfig"
1386 source "drivers/hid/surface-hid/Kconfig"
1388 source "drivers/hid/intel-thc-hid/Kconfig"
1392 # USB support may be used with HID disabled
1394 source "drivers/hid/usbhid/Kconfig"