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
217 Support for Corsair devices that are not fully compliant with the
225 tristate "Cougar devices"
227 Support for Cougar devices that are not fully compliant with the
231 - Cougar 500k Gaming Keyboard
234 tristate "Macally devices"
236 Support for Macally devices that are not fully compliant with the
240 - Macally ikey keyboard
243 tristate "Prodikeys PC-MIDI Keyboard support"
244 depends on USB_HID && SND
247 Support for Prodikeys PC-MIDI Keyboard device support.
248 Say Y here to enable support for this device.
249 - Prodikeys PC-MIDI keyboard.
250 The Prodikeys PC-MIDI acts as a USB Audio device, with one MIDI
251 input and one MIDI output. These MIDI jacks appear as
252 a sound "card" in the ALSA sound system.
253 Note: if you say N here, this device will still function as a basic
254 multimedia keyboard, but will lack support for the musical keyboard
255 and some additional multimedia keys.
258 tristate "CMedia audio chips"
260 Support for CMedia CM6533 HID audio jack controls
261 and HS100B mute buttons.
264 tristate "Silicon Labs CP2112 HID USB-to-SMBus Bridge support"
265 depends on USB_HID && HIDRAW && I2C && GPIOLIB
266 select GPIOLIB_IRQCHIP
268 Support for Silicon Labs CP2112 HID USB to SMBus Master Bridge.
269 This is a HID device driver which registers as an i2c adapter
270 and gpiochip to expose these functions of the CP2112. The
271 customizable USB descriptor fields are exposed as sysfs attributes.
273 config HID_CREATIVE_SB0540
274 tristate "Creative SB0540 infrared receiver"
277 Support for Creative infrared SB0540-compatible remote controls, such
278 as the RM-1500 and RM-1800 remotes.
280 Say Y here if you want support for Creative SB0540 infrared receiver.
283 tristate "Cypress mouse and barcode readers"
286 Support for cypress mouse and barcode readers.
288 config HID_DRAGONRISE
289 tristate "DragonRise Inc. game controller"
291 Say Y here if you have DragonRise Inc. game controllers.
292 These might be branded as:
294 - Media-tech MT1504 "Rogue"
296 - Defender Game Master
299 bool "DragonRise Inc. force feedback"
300 depends on HID_DRAGONRISE
301 select INPUT_FF_MEMLESS
303 Say Y here if you want to enable force feedback support for DragonRise Inc.
307 tristate "EMS Production Inc. force feedback support"
308 select INPUT_FF_MEMLESS
310 Say Y here if you want to enable force feedback support for devices by
312 Currently the following devices are known to be supported:
313 - Trio Linker Plus II
316 tristate "ELAN USB Touchpad Support"
317 depends on LEDS_CLASS && USB_HID
319 Say Y to enable support for the USB ELAN touchpad
320 Currently the following devices are known to be supported:
321 - HP Pavilion X2 10-p0XX.
324 tristate "ELECOM HID devices"
326 Support for ELECOM devices:
327 - BM084 Bluetooth Mouse
328 - EX-G Trackballs (M-XT3DRBK, M-XT3URBK)
329 - DEFT Trackballs (M-DT1DRBK, M-DT1URBK, M-DT2DRBK, M-DT2URBK)
330 - HUGE Trackballs (M-HT1DRBK, M-HT1URBK)
333 tristate "ELO USB 4000/4500 touchscreen"
336 Support for the ELO USB 4000/4500 touchscreens. Note that this is for
337 different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
340 tristate "EVision Keyboards Support"
343 Support for some EVision keyboards. Note that this is needed only when
344 applying customization using userspace programs.
347 tristate "Ezkey BTC 8193 keyboard"
350 Support for Ezkey BTC 8193 keyboard.
353 tristate "FTDI FT260 USB HID to I2C host support"
354 depends on USB_HID && HIDRAW && I2C
356 Provides I2C host adapter functionality over USB-HID through FT260
357 device. The customizable USB descriptor fields are exposed as sysfs
360 To compile this driver as a module, choose M here: the module
361 will be called hid-ft260.
364 tristate "Gembird Joypad"
366 Support for Gembird JPD-DualForce 2.
369 tristate "Google Fiber TV Box remote control support"
371 Support for Google Fiber TV Box remote controls
374 tristate "Glorious PC Gaming Race mice"
376 Support for Glorious PC Gaming Race mice such as
377 the Glorious Model O, O- and D.
380 tristate "Holtek HID devices"
383 Support for Holtek based devices:
384 - Holtek On Line Grip based game controller
385 - Trust GXT 18 Gaming Keyboard
386 - Sharkoon Drakonia / Perixx MX-2000 gaming mice
387 - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
389 - SHARKOON DarkGlider Gaming mouse
390 - LEETGION Hellion Gaming Mouse
393 bool "Holtek On Line Grip force feedback support"
394 depends on HID_HOLTEK
395 select INPUT_FF_MEMLESS
397 Say Y here if you have a Holtek On Line Grip based game controller
398 and want to have force feedback support for it.
400 config HID_VIVALDI_COMMON
403 ChromeOS Vivaldi HID parsing support library. This is a hidden
404 option so that drivers can use common code to parse the HID
405 descriptors for vivaldi function row keymap.
407 config HID_GOOGLE_HAMMER
408 tristate "Google Hammer Keyboard"
409 select HID_VIVALDI_COMMON
410 select INPUT_VIVALDIFMAP
411 depends on USB_HID && LEDS_CLASS && CROS_EC
413 Say Y here if you have a Google Hammer device.
416 tristate "Vivaldi Keyboard"
417 select HID_VIVALDI_COMMON
418 select INPUT_VIVALDIFMAP
420 Say Y here if you want to enable support for Vivaldi keyboards.
422 Vivaldi keyboards use a vendor-specific (Google) HID usage to report
423 how the keys in the top row are physically ordered.
426 tristate "MSI GT68xR LED support"
427 depends on LEDS_CLASS && USB_HID
429 Say Y here if you want to enable support for the three MSI GT68xR LEDs
431 This driver support following modes:
432 - Normal: LEDs are fully on when enabled
433 - Audio: LEDs brightness depends on sound level
434 - Breathing: LEDs brightness varies at human breathing rate
436 Currently the following devices are know to be supported:
440 tristate "Keytouch HID devices"
442 Support for Keytouch HID devices not fully compliant with
443 the specification. Currently supported:
447 tristate "KYE/Genius devices"
449 Support for KYE/Genius devices not fully compliant with HID standard:
451 - EasyPen i405X tablet
452 - MousePen i608X tablet
453 - EasyPen M610X tablet
459 Support for UC-Logic and Huion tablets.
464 Support for Waltop tablets.
467 tristate "ViewSonic/Signotec"
469 Support for ViewSonic/Signotec PD1011 signature pad.
472 tristate "VRC-2 Car Controller"
475 Support for VRC-2 which is a 2-axis controller often used in
478 To compile this driver as a module, choose M here: the
479 module will be called hid-vrc2.
484 Adds support for side buttons of Xiaomi Mi Dual Mode Wireless
485 Mouse Silent Edition.
488 tristate "Gyration remote control"
490 Support for Gyration remote control.
493 tristate "ION iCade arcade controller"
495 Support for the ION iCade arcade controller to work as a joystick.
497 To compile this driver as a module, choose M here: the
498 module will be called hid-icade.
501 tristate "ITE devices"
504 Support for ITE devices not fully compliant with HID standard.
507 tristate "Jabra USB HID Driver"
509 Support for Jabra USB HID devices.
511 Prevents mapping of vendor defined HID usages to input events. Without
512 this driver HID reports from Jabra devices may incorrectly be seen as
514 Say M here if you may ever plug in a Jabra USB device.
517 tristate "Twinhan IR remote control"
519 Support for Twinhan IR remote control.
521 config HID_KENSINGTON
522 tristate "Kensington Slimblade Trackball"
525 Support for Kensington Slimblade Trackball.
530 Support for LC-Power RC1000MCE RF remote control.
533 tristate "Simple RGB LED support"
534 depends on LEDS_CLASS
536 Support for simple RGB LED devices. Currently supported are:
537 - Riso Kagaku Webmail Notifier
538 - Dream Cheeky Webmail Notifier and Friends Alert
540 - Delcom Visual Signal Indicator Generation 2
543 To compile this driver as a module, choose M here: the
544 module will be called hid-led.
547 tristate "Lenovo / Thinkpad devices"
551 Support for IBM/Lenovo devices that are not fully compliant with HID standard.
553 Say Y if you want support for horizontal scrolling of the IBM/Lenovo
554 Scrollpoint mice or the non-compliant features of the Lenovo Thinkpad
555 standalone keyboards, e.g:
556 - ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
558 - ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
559 - ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
562 tristate "Letsketch WP9620N tablets"
565 Driver for the LetSketch / VSON WP9620N drawing tablet. This
566 drawing tablet is also sold under other brand names such as Case U,
567 presumably this driver will work for all of them. But it has only been
568 tested with a LetSketch WP9620N model.
570 These tablets also work without a special HID driver, but then only
571 part of the active area works and both the pad and stylus buttons are
572 hardwired to special key-combos. E.g. the 2 stylus buttons send right
573 mouse clicks / resp. "e" key presses.
576 tristate "Logitech devices"
578 depends on LEDS_CLASS
581 Support for Logitech devices that are not fully compliant with HID standard.
583 config HID_LOGITECH_DJ
584 tristate "Logitech receivers full support"
587 depends on HID_LOGITECH
588 select HID_LOGITECH_HIDPP
590 Say Y if you want support for Logitech receivers and devices.
591 Logitech receivers are capable of pairing multiple Logitech compliant
592 devices to the same receiver. Without this driver it will be handled by
593 generic USB_HID driver and all incoming events will be multiplexed
594 into a single mouse and a single keyboard device.
596 config HID_LOGITECH_HIDPP
597 tristate "Logitech HID++ devices support"
598 depends on HID_LOGITECH
601 Support for Logitech devices relying on the HID++ Logitech specification
603 Say Y if you want support for Logitech devices relying on the HID++
604 specification. Such devices are the various Logitech Touchpads (T650,
605 T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
609 bool "Logitech force feedback support"
610 depends on HID_LOGITECH
611 select INPUT_FF_MEMLESS
613 Say Y here if you have one of these devices:
614 - Logitech WingMan Cordless RumblePad
615 - Logitech WingMan Cordless RumblePad 2
616 - Logitech WingMan Force 3D
618 and if you want to enable force feedback for them.
619 Note: if you say N here, this device will still be supported, but without
622 config LOGIRUMBLEPAD2_FF
623 bool "Logitech force feedback support (variant 2)"
624 depends on HID_LOGITECH
625 select INPUT_FF_MEMLESS
627 Say Y here if you want to enable force feedback support for:
629 - Logitech Rumblepad 2
630 - Logitech Formula Vibration Feedback Wheel
633 bool "Logitech Flight System G940 force feedback support"
634 depends on HID_LOGITECH
635 select INPUT_FF_MEMLESS
637 Say Y here if you want to enable force feedback support for Logitech
638 Flight System G940 devices.
641 bool "Logitech wheels configuration and force feedback support"
642 depends on HID_LOGITECH
643 select INPUT_FF_MEMLESS
646 Say Y here if you want to enable force feedback and range setting(*)
647 support for following Logitech wheels:
651 - Logitech Driving Force
652 - Logitech Driving Force Pro (*)
653 - Logitech Driving Force GT (*)
654 - Logitech Driving Force EX/RX
655 - Logitech Driving Force Wireless
656 - Logitech Speed Force Wireless
657 - Logitech MOMO Force
658 - Logitech MOMO Racing Force
659 - Logitech Formula Force GP
660 - Logitech Formula Force EX/RX
661 - Logitech Wingman Formula Force GP
663 config HID_MAGICMOUSE
664 tristate "Apple Magic Mouse/Trackpad multi-touch support"
666 Support for the Apple Magic Mouse/Trackpad multi-touch.
668 Say Y here if you want support for the multi-touch features of the
669 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
672 tristate "Maltron L90 keyboard"
674 Adds support for the volume up, volume down, mute, and play/pause buttons
675 of the Maltron L90 keyboard.
678 tristate "Mayflash game controller adapter force feedback"
679 select INPUT_FF_MEMLESS
681 Say Y here if you have HJZ Mayflash PS3 game controller adapters
682 and want to enable force feedback support.
684 config HID_MEGAWORLD_FF
685 tristate "Mega World based game controller force feedback support"
687 select INPUT_FF_MEMLESS
689 Say Y here if you have a Mega World based game controller and want
690 to have force feedback support for it.
693 tristate "Redragon keyboards"
696 Support for Redragon keyboards that need fix-ups to work properly.
699 tristate "Microsoft non-fully HID-compliant devices"
701 select INPUT_FF_MEMLESS
703 Support for Microsoft devices that are not fully compliant with HID standard.
706 tristate "Monterey Genius KB29E keyboard"
709 Support for Monterey Genius KB29E.
711 config HID_MULTITOUCH
712 tristate "HID Multitouch panels"
714 Generic support for HID multitouch panels.
716 Say Y here if you have one of the following devices:
717 - 3M PCT touch screens
718 - ActionStar dual touch panels
720 - Cando dual touch panels
724 - Cypress TrueTouch panels
725 - Elan Microelectronics touch panels
726 - Elo TouchSystems IntelliTouch Plus panels
727 - GeneralTouch 'Sensing Win7-TwoFinger' panels
729 - Hanvon dual touch panels
730 - Ilitek dual touch panels
731 - IrTouch Infrared USB panels
732 - LG Display panels (Dell ST2220Tc)
733 - Lumio CrystalTouch panels
734 - MosArt dual-touch panels
735 - Panasonic multitouch panels
736 - PenMount dual touch panels
737 - Perixx Peripad 701 touchpad
738 - PixArt optical touch screen
739 - Pixcir dual touch panels
741 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
742 - SiS multitouch panels
743 - Stantum multitouch panels
744 - Touch International Panels
746 - Wistron optical touch panels
747 - XAT optical touch panels
748 - Xiroku optical touch panels
749 - Zytronic touch panels
753 To compile this driver as a module, choose M here: the
754 module will be called hid-multitouch.
757 tristate "Nintendo Joy-Con and Pro Controller support"
759 depends on LEDS_CLASS
762 Adds support for the Nintendo Switch Joy-Cons and Pro Controller.
763 All controllers support bluetooth, and the Pro Controller also supports
766 To compile this driver as a module, choose M here: the
767 module will be called hid-nintendo.
770 bool "Nintendo Switch controller force feedback support"
771 depends on HID_NINTENDO
772 select INPUT_FF_MEMLESS
774 Say Y here if you have a Nintendo Switch controller and want to enable
775 force feedback support for it. This works for both joy-cons and the pro
776 controller. For the pro controller, both rumble motors can be controlled
780 tristate "NTI keyboard adapters"
782 Support for the "extra" Sun keyboard keys on keyboards attached
783 through Network Technologies USB-SUN keyboard adapters.
786 tristate "N-Trig touch screen"
789 Support for N-Trig touch screen.
792 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
794 There are certain devices which have LogicalMaximum wrong in the keyboard
795 usage page of their report descriptor. The most prevailing ones so far
796 are manufactured by Ortek, thus the name of the driver. Currently
797 supported devices by this driver are
801 - Skycable wireless presenter
803 config HID_PANTHERLORD
804 tristate "Pantherlord/GreenAsia game controller"
806 Say Y here if you have a PantherLord/GreenAsia based game controller
809 config PANTHERLORD_FF
810 bool "Pantherlord force feedback support"
811 depends on HID_PANTHERLORD
812 select INPUT_FF_MEMLESS
814 Say Y here if you have a PantherLord/GreenAsia based game controller
815 or adapter and want to enable force feedback support for it.
818 tristate "Penmount touch device"
821 This selects a driver for the PenMount 6000 touch controller.
823 The driver works around a problem in the report descript allowing
824 the userspace to touch events instead of mouse events.
826 Say Y here if you have a Penmount based touch controller.
829 tristate "Petalynx Maxter remote control"
831 Support for Petalynx Maxter remote control.
834 tristate "PicoLCD (graphic version)"
836 This provides support for Minibox PicoLCD devices, currently
837 only the graphical ones are supported.
839 This includes support for the following device features:
841 - Switching between Firmware and Flash mode
842 - EEProm / Flash access (via debugfs)
843 Features selectively enabled:
844 - Framebuffer for monochrome 256x64 display
847 - General purpose outputs
848 Features that are not (yet) supported:
851 config HID_PICOLCD_FB
852 bool "Framebuffer support" if EXPERT
854 depends on HID_PICOLCD
855 depends on HID_PICOLCD=FB || FB=y
856 select FB_DEFERRED_IO
857 select FB_SYS_FILLRECT
858 select FB_SYS_COPYAREA
859 select FB_SYS_IMAGEBLIT
862 Provide access to PicoLCD's 256x64 monochrome display via a
865 config HID_PICOLCD_BACKLIGHT
866 bool "Backlight control" if EXPERT
868 depends on HID_PICOLCD
869 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
871 Provide access to PicoLCD's backlight control via backlight
874 config HID_PICOLCD_LCD
875 bool "Contrast control" if EXPERT
877 depends on HID_PICOLCD
878 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
880 Provide access to PicoLCD's LCD contrast via lcd class.
882 config HID_PICOLCD_LEDS
883 bool "GPO via leds class" if EXPERT
885 depends on HID_PICOLCD
886 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
888 Provide access to PicoLCD's GPO pins via leds class.
890 config HID_PICOLCD_CIR
891 bool "CIR via RC class" if EXPERT
893 depends on HID_PICOLCD
894 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
896 Provide access to PicoLCD's CIR interface via remote control (LIRC).
898 config HID_PLANTRONICS
899 tristate "Plantronics USB HID Driver"
901 Provides HID support for Plantronics USB audio devices.
902 Correctly maps vendor unique volume up/down HID usages to
903 KEY_VOLUMEUP and KEY_VOLUMEDOWN events and prevents core mapping
904 of other vendor unique HID usages to random mouse events.
906 Say M here if you may ever plug in a Plantronics USB audio device.
908 config HID_PLAYSTATION
909 tristate "PlayStation HID Driver"
910 depends on LEDS_CLASS_MULTICOLOR
914 Provides support for Sony PS4/PS5 controllers including support for
915 its special functionalities e.g. touchpad, lights and motion
918 config PLAYSTATION_FF
919 bool "PlayStation force feedback support"
920 depends on HID_PLAYSTATION
921 select INPUT_FF_MEMLESS
923 Say Y here if you would like to enable force feedback support for
924 PlayStation game controllers.
927 tristate "PhoenixRC HID Flight Controller"
930 Support for PhoenixRC HID Flight Controller, a 8-axis flight controller.
932 To compile this driver as a module, choose M here: the
933 module will be called hid-pxrc.
936 tristate "Razer non-fully HID-compliant devices"
938 Support for Razer devices that are not fully compliant with the
942 tristate "Primax non-fully HID-compliant devices"
944 Support for Primax devices that are not fully compliant with the
948 tristate "Retrode 2 USB adapter for vintage video games"
952 * Retrode 2 cartridge and controller adapter
955 tristate "Roccat device support"
958 Support for Roccat devices.
959 Say Y here if you have a Roccat mouse or keyboard and want
960 support for its special functionalities.
963 tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
965 Support for Saitek devices that are not fully compliant with the
969 - PS1000 Dual Analog Pad
970 - Saitek R.A.T.7, R.A.T.9, M.M.O.7 Gaming Mice
971 - Mad Catz R.A.T.5, R.A.T.9 Gaming Mice
974 tristate "Samsung InfraRed remote control or keyboards"
977 Support for Samsung InfraRed remote control or keyboards.
980 tristate "Semitek USB keyboards"
982 Support for Semitek USB keyboards that are not fully compliant
983 with the HID standard.
985 There are many variants, including:
986 - GK61, GK64, GK68, GK84, GK96, etc.
987 - SK61, SK64, SK68, SK84, SK96, etc.
991 - X-Bows Nature/Knight
993 config HID_SIGMAMICRO
994 tristate "SiGma Micro-based keyboards"
997 Support for keyboards that use the SiGma Micro (a.k.a SigmaChip) IC.
1004 tristate "Sony PS2/3/4 accessories"
1007 depends on LEDS_CLASS
1013 * Sony PS3 6-axis controllers
1014 * Sony PS4 DualShock 4 controllers
1016 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
1017 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
1018 * Guitar Hero Live PS3, Wii U and PS4 guitar dongles
1019 * Guitar Hero PS3 and PC guitar dongles
1022 bool "Sony PS2/3/4 accessories force feedback support"
1024 select INPUT_FF_MEMLESS
1026 Say Y here if you have a Sony PS2/3/4 accessory and want to enable
1027 force feedback support for it.
1029 config HID_SPEEDLINK
1030 tristate "Speedlink VAD Cezanne mouse support"
1032 Support for Speedlink Vicious and Divine Cezanne mouse.
1035 tristate "Steam Controller/Deck support"
1038 Say Y here if you have a Steam Controller or Deck if you want to use it
1039 without running the Steam Client. It supports both the wired and
1040 the wireless adaptor.
1043 bool "Steam Deck force feedback support"
1044 depends on HID_STEAM
1045 select INPUT_FF_MEMLESS
1047 Say Y here if you want to enable force feedback support for the Steam
1050 config HID_STEELSERIES
1051 tristate "Steelseries SRW-S1 steering wheel support"
1053 Support for Steelseries SRW-S1 steering wheel
1056 tristate "Sunplus wireless desktop"
1058 Support for Sunplus wireless desktop.
1061 tristate "Synaptics RMI4 device support"
1068 Support for Synaptics RMI4 touchpads.
1069 Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
1070 and want support for its special functionalities.
1072 config HID_GREENASIA
1073 tristate "GreenAsia (Product ID 0x12) game controller support"
1075 Say Y here if you have a GreenAsia (Product ID 0x12) based game
1076 controller or adapter.
1079 bool "GreenAsia (Product ID 0x12) force feedback support"
1080 depends on HID_GREENASIA
1081 select INPUT_FF_MEMLESS
1083 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
1084 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
1085 and want to enable force feedback support for it.
1087 config HID_HYPERV_MOUSE
1088 tristate "Microsoft Hyper-V mouse driver"
1091 Select this option to enable the Hyper-V mouse driver.
1093 config HID_SMARTJOYPLUS
1094 tristate "SmartJoy PLUS PS2/USB adapter support"
1096 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
1097 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
1099 Note that DDR (Dance Dance Revolution) mode is not supported, nor
1100 is pressure sensitive buttons on the pro models.
1102 config SMARTJOYPLUS_FF
1103 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
1104 depends on HID_SMARTJOYPLUS
1105 select INPUT_FF_MEMLESS
1107 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
1108 enable force feedback support for it.
1111 tristate "TiVo Slide Bluetooth remote control support"
1113 Say Y if you have a TiVo Slide Bluetooth remote control.
1116 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
1118 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
1119 CLLRCMCE remote control.
1122 tristate "Topre REALFORCE keyboards"
1125 Say Y for N-key rollover support on Topre REALFORCE R2 108 key keyboards.
1128 tristate "ThingM blink(1) USB RGB LED"
1129 depends on LEDS_CLASS
1132 Support for the ThingM blink(1) USB RGB LED. This driver has been
1133 merged into the generic hid led driver. Config symbol HID_THINGM
1134 just selects HID_LED and will be removed soon.
1136 config HID_THRUSTMASTER
1137 tristate "ThrustMaster devices support"
1140 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2,
1141 a THRUSTMASTER Ferrari GT Rumble Wheel or Thrustmaster FFB
1142 Wheel (T150RS, T300RS, T300 Ferrari Alcantara Edition, T500RS).
1144 config THRUSTMASTER_FF
1145 bool "ThrustMaster devices force feedback support"
1146 depends on HID_THRUSTMASTER
1147 select INPUT_FF_MEMLESS
1149 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
1150 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
1151 Rumble Force or Force Feedback Wheel.
1153 config HID_UDRAW_PS3
1154 tristate "THQ PS3 uDraw tablet"
1156 Say Y here if you want to use the THQ uDraw gaming tablet for
1160 tristate "U2F Zero LED and RNG support"
1162 depends on LEDS_CLASS
1163 depends on HW_RANDOM
1165 Support for the LED of the U2F Zero device.
1167 U2F Zero supports custom commands for blinking the LED
1168 and getting data from the internal hardware RNG.
1169 The internal hardware can be used to feed the enthropy pool.
1171 U2F Zero only supports blinking its LED, so this driver doesn't
1172 allow setting the brightness to anything but 1, which will
1173 trigger a single blink and immediately reset back to 0.
1176 tristate "Wacom Intuos/Graphire tablet support (USB)"
1181 select LEDS_TRIGGERS
1183 Say Y here if you want to use the USB or BT version of the Wacom Intuos
1186 To compile this driver as a module, choose M here: the
1187 module will be called wacom.
1190 tristate "Nintendo Wii / Wii U peripherals"
1191 depends on LEDS_CLASS
1193 select INPUT_FF_MEMLESS
1195 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
1196 devices are the Wii Remote and its extension devices, but also devices
1197 based on the Wii Remote like the Wii U Pro Controller or the
1200 Support for all official Nintendo extensions is available, however, 3rd
1201 party extensions might not be supported. Please report these devices to:
1202 http://github.com/dvdhrm/xwiimote/issues
1204 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
1205 the Wii U Gamepad) might be supported in the future. But currently
1206 support is limited to Bluetooth based devices.
1210 To compile this driver as a module, choose M here: the
1211 module will be called hid-wiimote.
1214 tristate "Xin-Mo non-fully compliant devices"
1216 Support for Xin-Mo devices that are not fully compliant with the HID
1217 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
1218 if you have a Xin-Mo Dual Arcade controller.
1221 tristate "Zeroplus based game controller support"
1223 Say Y here if you have a Zeroplus based game controller.
1226 bool "Zeroplus based game controller force feedback support"
1227 depends on HID_ZEROPLUS
1228 select INPUT_FF_MEMLESS
1230 Say Y here if you have a Zeroplus based game controller and want
1231 to have force feedback support for it.
1234 tristate "Zydacron remote control support"
1236 Support for Zydacron remote control.
1238 config HID_SENSOR_HUB
1239 tristate "HID Sensors framework support"
1240 depends on HAS_IOMEM
1244 Support for HID Sensor framework. This creates a MFD instance
1245 for a sensor hub and identifies all the sensors connected to it.
1246 Each sensor is registered as a MFD cell, so that sensor specific
1247 processing can be done in a separate driver. Each sensor
1248 drivers can use the service provided by this driver to register
1249 for events and handle data streams. Each sensor driver can format
1250 data and present to user mode using input or IIO interface.
1252 config HID_SENSOR_CUSTOM_SENSOR
1253 tristate "HID Sensors hub custom sensor support"
1254 depends on HID_SENSOR_HUB
1257 HID Sensor hub specification allows definition of some custom and
1258 generic sensors. Unlike other HID sensors, they can't be exported
1259 via Linux IIO because of custom fields. This is up to the manufacturer
1260 to decide how to interpret these special sensor ids and process in
1261 the user space. Currently some manufacturers are using these ids for
1262 sensor calibration and debugging other sensors. Manufacturers
1263 shouldn't use these special custom sensor ids to export any of the
1265 Select this config option for custom/generic sensor support.
1268 tristate "Alps HID device support"
1270 Support for Alps I2C HID touchpads and StickPointer.
1271 Say Y here if you have a Alps touchpads over i2c-hid or usbhid
1272 and want support for its special functionalities.
1275 tristate "Microchip MCP2221 HID USB-to-I2C/SMbus host support"
1276 depends on USB_HID && I2C
1280 Provides I2C and SMBUS host adapter functionality over USB-HID
1281 through MCP2221 device.
1283 To compile this driver as a module, choose M here: the module
1284 will be called hid-mcp2221.ko.
1286 config HID_KUNIT_TEST
1287 tristate "KUnit tests for HID" if !KUNIT_ALL_TESTS
1289 depends on HID_BATTERY_STRENGTH
1290 depends on HID_UCLOGIC
1291 default KUNIT_ALL_TESTS
1293 This builds unit tests for HID. This option is not useful for
1294 distributions or general kernels, but only for kernel
1295 developers working on HID and associated drivers.
1297 For more information on KUnit and unit tests in general,
1298 please refer to the KUnit documentation in
1299 Documentation/dev-tools/kunit/.
1301 If in doubt, say "N".
1305 source "drivers/hid/bpf/Kconfig"
1309 source "drivers/hid/usbhid/Kconfig"
1311 source "drivers/hid/i2c-hid/Kconfig"
1313 source "drivers/hid/intel-ish-hid/Kconfig"
1315 source "drivers/hid/amd-sfh-hid/Kconfig"
1317 source "drivers/hid/surface-hid/Kconfig"