2 # HID driver configuration
8 tristate "HID bus support"
12 A human interface device (HID) is a type of computer device that
13 interacts directly with and takes input from humans. The term "HID"
14 most commonly used to refer to the USB-HID specification, but other
15 devices (such as, but not strictly limited to, Bluetooth) are
16 designed using HID specification (this involves certain keyboards,
17 mice, tablets, etc). This option adds the HID bus to the kernel,
18 together with generic HID layer code. The HID devices are added and
19 removed from the HID bus by the transport-layer drivers, such as
20 usbhid (USB_HID) and hidp (BT_HIDP).
22 For docs and specs, see http://www.usb.org/developers/hidpage/
28 config HID_BATTERY_STRENGTH
29 bool "Battery level reporting for HID devices"
34 This option adds support of reporting battery strength (for HID devices
35 that support this feature) through power_supply class so that userspace
36 tools, such as upower, can display it.
39 bool "/dev/hidraw raw HID device support"
42 Say Y here if you want to support HID devices (from the USB
43 specification standpoint) that aren't strictly user interface
44 devices, like monitor controls and Uninterruptable Power Supplies.
46 This module supports these devices separately using a separate
47 event interface on /dev/hidraw.
49 There is also a /dev/hiddev configuration option in the USB HID
50 configuration menu. In comparison to hiddev, this device does not process
51 the hid events at all (no parsing, no lookups). This lets applications
52 to work on raw hid events when they want to, and avoid using transport-specific
53 userspace libhid/libusb libraries.
58 tristate "User-space I/O driver support for HID subsystem"
62 Say Y here if you want to provide HID I/O Drivers from user-space.
63 This allows to write I/O drivers in user-space and feed the data from
64 the device into the kernel. The kernel parses the HID reports, loads the
65 corresponding HID Device Driver or provides input devices on top of your
68 This driver cannot be used to parse HID-reports in user-space and write
69 special HID-drivers. You should use hidraw for that.
70 Instead, this driver allows to write the transport-layer driver in
71 user-space like USB-HID and Bluetooth-HID do in kernel-space.
75 To compile this driver as a module, choose M here: the
76 module will be called uhid.
79 tristate "Generic HID driver"
83 Support for generic devices on the HID bus. This includes most
84 keyboards and mice, joysticks, tablets and digitizers.
86 To compile this driver as a module, choose M here: the module
87 will be called hid-generic.
91 menu "Special HID drivers"
95 tristate "A4 tech mice"
99 Support for A4 tech X5 and WOP-35 / Trust 450L mice.
102 tristate "Accutouch touch device"
105 This selects a driver for the Accutouch 2216 touch controller.
107 The driver works around a problem in the reported device capabilities
108 which causes userspace to detect the device as a mouse rather than
111 Say Y here if you have a Accutouch 2216 touch controller.
114 tristate "ACRUX game controller support"
117 Say Y here if you want to enable support for ACRUX game controllers.
120 bool "ACRUX force feedback support"
122 select INPUT_FF_MEMLESS
124 Say Y here if you want to enable force feedback support for ACRUX
128 tristate "Apple {i,Power,Mac}Books"
132 Support for some Apple devices which less or more break
135 Say Y here if you want support for keyboards of Apple iBooks, PowerBooks,
136 MacBooks, MacBook Pros and Apple Aluminum.
139 tristate "Apple infrared receiver"
142 Support for Apple infrared remote control. All the Apple computers from
143 2005 onwards include such a port, except the unibody Macbook (2009),
144 and Mac Pros. This receiver is also used in the Apple TV set-top box
145 prior to the 2010 model.
147 Say Y here if you want support for Apple infrared remote control.
152 depends on LEDS_CLASS
154 Support for Asus notebook built-in keyboard and touchpad via i2c, and
155 the Asus Republic of Gamers laptop keyboard special keys.
167 Support for Aureal Cy se W-01RN Remote Controller and other Aureal derived remotes.
170 tristate "Belkin Flip KVM and Wireless keyboard"
174 Support for Belkin Flip KVM and Wireless keyboard.
177 tristate "Betop Production Inc. force feedback support"
179 select INPUT_FF_MEMLESS
181 Say Y here if you want to enable force feedback support for devices by
182 BETOP Production Ltd.
183 Currently the following devices are known to be supported:
184 - BETOP 2185 PC & BFM MODE
187 tristate "Cherry Cymotion keyboard"
191 Support for Cherry Cymotion keyboard.
194 tristate "Chicony devices"
198 Support for Chicony Tactical pad and special keys on Chicony keyboards.
201 tristate "Corsair devices"
202 depends on USB_HID && LEDS_CLASS
204 Support for Corsair devices that are not fully compliant with the
212 tristate "Prodikeys PC-MIDI Keyboard support"
213 depends on USB_HID && SND
216 Support for Prodikeys PC-MIDI Keyboard device support.
217 Say Y here to enable support for this device.
218 - Prodikeys PC-MIDI keyboard.
219 The Prodikeys PC-MIDI acts as a USB Audio device, with one MIDI
220 input and one MIDI output. These MIDI jacks appear as
221 a sound "card" in the ALSA sound system.
222 Note: if you say N here, this device will still function as a basic
223 multimedia keyboard, but will lack support for the musical keyboard
224 and some additional multimedia keys.
227 tristate "CMedia CM6533 HID audio jack controls"
230 Support for CMedia CM6533 HID audio jack controls.
233 tristate "Silicon Labs CP2112 HID USB-to-SMBus Bridge support"
234 depends on USB_HID && HIDRAW && I2C && GPIOLIB
235 select GPIOLIB_IRQCHIP
237 Support for Silicon Labs CP2112 HID USB to SMBus Master Bridge.
238 This is a HID device driver which registers as an i2c adapter
239 and gpiochip to expose these functions of the CP2112. The
240 customizable USB descriptor fields are exposed as sysfs attributes.
243 tristate "Cypress mouse and barcode readers"
247 Support for cypress mouse and barcode readers.
249 config HID_DRAGONRISE
250 tristate "DragonRise Inc. game controller"
253 Say Y here if you have DragonRise Inc. game controllers.
254 These might be branded as:
256 - Media-tech MT1504 "Rogue"
258 - Defender Game Master
261 bool "DragonRise Inc. force feedback"
262 depends on HID_DRAGONRISE
263 select INPUT_FF_MEMLESS
265 Say Y here if you want to enable force feedback support for DragonRise Inc.
269 tristate "EMS Production Inc. force feedback support"
271 select INPUT_FF_MEMLESS
273 Say Y here if you want to enable force feedback support for devices by
275 Currently the following devices are known to be supported:
276 - Trio Linker Plus II
279 tristate "ELECOM HID devices"
282 Support for ELECOM devices:
283 - BM084 Bluetooth Mouse
284 - DEFT Trackball (Wired and wireless)
285 - HUGE Trackball (Wired and wireless)
288 tristate "ELO USB 4000/4500 touchscreen"
291 Support for the ELO USB 4000/4500 touchscreens. Note that this is for
292 different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
295 tristate "Ezkey BTC 8193 keyboard"
299 Support for Ezkey BTC 8193 keyboard.
302 tristate "Gembird Joypad"
305 Support for Gembird JPD-DualForce 2.
308 tristate "Google Fiber TV Box remote control support"
311 Support for Google Fiber TV Box remote controls
314 tristate "Holtek HID devices"
317 Support for Holtek based devices:
318 - Holtek On Line Grip based game controller
319 - Trust GXT 18 Gaming Keyboard
320 - Sharkoon Drakonia / Perixx MX-2000 gaming mice
321 - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
323 - SHARKOON DarkGlider Gaming mouse
324 - LEETGION Hellion Gaming Mouse
327 bool "Holtek On Line Grip force feedback support"
328 depends on HID_HOLTEK
329 select INPUT_FF_MEMLESS
331 Say Y here if you have a Holtek On Line Grip based game controller
332 and want to have force feedback support for it.
335 tristate "MSI GT68xR LED support"
336 depends on LEDS_CLASS && USB_HID
338 Say Y here if you want to enable support for the three MSI GT68xR LEDs
340 This driver support following modes:
341 - Normal: LEDs are fully on when enabled
342 - Audio: LEDs brightness depends on sound level
343 - Breathing: LEDs brightness varies at human breathing rate
345 Currently the following devices are know to be supported:
349 tristate "Keytouch HID devices"
352 Support for Keytouch HID devices not fully compliant with
353 the specification. Currently supported:
357 tristate "KYE/Genius devices"
360 Support for KYE/Genius devices not fully compliant with HID standard:
362 - EasyPen i405X tablet
363 - MousePen i608X tablet
364 - EasyPen M610X tablet
370 Support for UC-Logic and Huion tablets.
376 Support for Waltop tablets.
379 tristate "Gyration remote control"
382 Support for Gyration remote control.
385 tristate "ION iCade arcade controller"
388 Support for the ION iCade arcade controller to work as a joystick.
390 To compile this driver as a module, choose M here: the
391 module will be called hid-icade.
394 tristate "ITE devices"
398 Support for ITE devices not fully compliant with HID standard.
401 tristate "Twinhan IR remote control"
404 Support for Twinhan IR remote control.
406 config HID_KENSINGTON
407 tristate "Kensington Slimblade Trackball"
411 Support for Kensington Slimblade Trackball.
417 Support for LC-Power RC1000MCE RF remote control.
420 tristate "Simple RGB LED support"
422 depends on LEDS_CLASS
424 Support for simple RGB LED devices. Currently supported are:
425 - Riso Kagaku Webmail Notifier
426 - Dream Cheeky Webmail Notifier and Friends Alert
428 - Delcom Visual Signal Indicator Generation 2
431 To compile this driver as a module, choose M here: the
432 module will be called hid-led.
435 tristate "Lenovo / Thinkpad devices"
440 Support for IBM/Lenovo devices that are not fully compliant with HID standard.
442 Say Y if you want support for horizontal scrolling of the IBM/Lenovo
443 Scrollpoint mice or the non-compliant features of the Lenovo Thinkpad
444 standalone keyboards, e.g:
445 - ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
447 - ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
448 - ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
451 tristate "Logitech devices"
455 Support for Logitech devices that are not fully compliant with HID standard.
457 config HID_LOGITECH_DJ
458 tristate "Logitech Unifying receivers full support"
460 depends on HID_LOGITECH
461 select HID_LOGITECH_HIDPP
463 Say Y if you want support for Logitech Unifying receivers and devices.
464 Unifying receivers are capable of pairing up to 6 Logitech compliant
465 devices to the same receiver. Without this driver it will be handled by
466 generic USB_HID driver and all incoming events will be multiplexed
467 into a single mouse and a single keyboard device.
469 config HID_LOGITECH_HIDPP
470 tristate "Logitech HID++ devices support"
471 depends on HID_LOGITECH
474 Support for Logitech devices relyingon the HID++ Logitech specification
476 Say Y if you want support for Logitech devices relying on the HID++
477 specification. Such devices are the various Logitech Touchpads (T650,
478 T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
482 bool "Logitech force feedback support"
483 depends on HID_LOGITECH
484 select INPUT_FF_MEMLESS
486 Say Y here if you have one of these devices:
487 - Logitech WingMan Cordless RumblePad
488 - Logitech WingMan Cordless RumblePad 2
489 - Logitech WingMan Force 3D
491 and if you want to enable force feedback for them.
492 Note: if you say N here, this device will still be supported, but without
495 config LOGIRUMBLEPAD2_FF
496 bool "Logitech force feedback support (variant 2)"
497 depends on HID_LOGITECH
498 select INPUT_FF_MEMLESS
500 Say Y here if you want to enable force feedback support for:
502 - Logitech Rumblepad 2
503 - Logitech Formula Vibration Feedback Wheel
506 bool "Logitech Flight System G940 force feedback support"
507 depends on HID_LOGITECH
508 select INPUT_FF_MEMLESS
510 Say Y here if you want to enable force feedback support for Logitech
511 Flight System G940 devices.
514 bool "Logitech wheels configuration and force feedback support"
515 depends on HID_LOGITECH
516 select INPUT_FF_MEMLESS
519 Say Y here if you want to enable force feedback and range setting(*)
520 support for following Logitech wheels:
524 - Logitech Driving Force
525 - Logitech Driving Force Pro (*)
526 - Logitech Driving Force GT (*)
527 - Logitech Driving Force EX/RX
528 - Logitech Driving Force Wireless
529 - Logitech Speed Force Wireless
530 - Logitech MOMO Force
531 - Logitech MOMO Racing Force
532 - Logitech Formula Force GP
533 - Logitech Formula Force EX/RX
534 - Logitech Wingman Formula Force GP
536 config HID_MAGICMOUSE
537 tristate "Apple Magic Mouse/Trackpad multi-touch support"
540 Support for the Apple Magic Mouse/Trackpad multi-touch.
542 Say Y here if you want support for the multi-touch features of the
543 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
546 tristate "Mayflash game controller adapter force feedback"
548 select INPUT_FF_MEMLESS
550 Say Y here if you have HJZ Mayflash PS3 game controller adapters
551 and want to enable force feedback support.
554 tristate "Microsoft non-fully HID-compliant devices"
558 Support for Microsoft devices that are not fully compliant with HID standard.
561 tristate "Monterey Genius KB29E keyboard"
565 Support for Monterey Genius KB29E.
567 config HID_MULTITOUCH
568 tristate "HID Multitouch panels"
571 Generic support for HID multitouch panels.
573 Say Y here if you have one of the following devices:
574 - 3M PCT touch screens
575 - ActionStar dual touch panels
577 - Cando dual touch panels
581 - Cypress TrueTouch panels
582 - Elan Microelectronics touch panels
583 - Elo TouchSystems IntelliTouch Plus panels
584 - GeneralTouch 'Sensing Win7-TwoFinger' panels
586 - Hanvon dual touch panels
587 - Ilitek dual touch panels
588 - IrTouch Infrared USB panels
589 - LG Display panels (Dell ST2220Tc)
590 - Lumio CrystalTouch panels
591 - MosArt dual-touch panels
592 - Panasonic multitouch panels
593 - PenMount dual touch panels
594 - Perixx Peripad 701 touchpad
595 - PixArt optical touch screen
596 - Pixcir dual touch panels
598 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
599 - SiS multitouch panels
600 - Stantum multitouch panels
601 - Touch International Panels
603 - Wistron optical touch panels
604 - XAT optical touch panels
605 - Xiroku optical touch panels
606 - Zytronic touch panels
610 To compile this driver as a module, choose M here: the
611 module will be called hid-multitouch.
614 tristate "NTI keyboard adapters"
616 Support for the "extra" Sun keyboard keys on keyboards attached
617 through Network Technologies USB-SUN keyboard adapters.
620 tristate "N-Trig touch screen"
623 Support for N-Trig touch screen.
626 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
629 There are certain devices which have LogicalMaximum wrong in the keyboard
630 usage page of their report descriptor. The most prevailing ones so far
631 are manufactured by Ortek, thus the name of the driver. Currently
632 supported devices by this driver are
636 - Skycable wireless presenter
638 config HID_PANTHERLORD
639 tristate "Pantherlord/GreenAsia game controller"
642 Say Y here if you have a PantherLord/GreenAsia based game controller
645 config PANTHERLORD_FF
646 bool "Pantherlord force feedback support"
647 depends on HID_PANTHERLORD
648 select INPUT_FF_MEMLESS
650 Say Y here if you have a PantherLord/GreenAsia based game controller
651 or adapter and want to enable force feedback support for it.
654 tristate "Penmount touch device"
657 This selects a driver for the PenMount 6000 touch controller.
659 The driver works around a problem in the report descript allowing
660 the userspace to touch events instead of mouse events.
662 Say Y here if you have a Penmount based touch controller.
665 tristate "Petalynx Maxter remote control"
668 Support for Petalynx Maxter remote control.
671 tristate "PicoLCD (graphic version)"
674 This provides support for Minibox PicoLCD devices, currently
675 only the graphical ones are supported.
677 This includes support for the following device features:
679 - Switching between Firmware and Flash mode
680 - EEProm / Flash access (via debugfs)
681 Features selectively enabled:
682 - Framebuffer for monochrome 256x64 display
685 - General purpose outputs
686 Features that are not (yet) supported:
689 config HID_PICOLCD_FB
690 bool "Framebuffer support" if EXPERT
692 depends on HID_PICOLCD
693 depends on HID_PICOLCD=FB || FB=y
694 select FB_DEFERRED_IO
695 select FB_SYS_FILLRECT
696 select FB_SYS_COPYAREA
697 select FB_SYS_IMAGEBLIT
700 Provide access to PicoLCD's 256x64 monochrome display via a
703 config HID_PICOLCD_BACKLIGHT
704 bool "Backlight control" if EXPERT
706 depends on HID_PICOLCD
707 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
709 Provide access to PicoLCD's backlight control via backlight
712 config HID_PICOLCD_LCD
713 bool "Contrast control" if EXPERT
715 depends on HID_PICOLCD
716 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
718 Provide access to PicoLCD's LCD contrast via lcd class.
720 config HID_PICOLCD_LEDS
721 bool "GPO via leds class" if EXPERT
723 depends on HID_PICOLCD
724 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
726 Provide access to PicoLCD's GPO pins via leds class.
728 config HID_PICOLCD_CIR
729 bool "CIR via RC class" if EXPERT
731 depends on HID_PICOLCD
732 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
734 Provide access to PicoLCD's CIR interface via remote control (LIRC).
736 config HID_PLANTRONICS
737 tristate "Plantronics USB HID Driver"
740 Provides HID support for Plantronics USB audio devices.
741 Correctly maps vendor unique volume up/down HID usages to
742 KEY_VOLUMEUP and KEY_VOLUMEDOWN events and prevents core mapping
743 of other vendor unique HID usages to random mouse events.
745 Say M here if you may ever plug in a Plantronics USB audio device.
748 tristate "Primax non-fully HID-compliant devices"
751 Support for Primax devices that are not fully compliant with the
760 * Retrode 2 cartridge and controller adapter
763 tristate "Roccat device support"
766 Support for Roccat devices.
767 Say Y here if you have a Roccat mouse or keyboard and want
768 support for its special functionalities.
771 tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
774 Support for Saitek devices that are not fully compliant with the
778 - PS1000 Dual Analog Pad
779 - Saitek R.A.T.7, R.A.T.9, M.M.O.7 Gaming Mice
780 - Mad Catz R.A.T.5, R.A.T.9 Gaming Mice
783 tristate "Samsung InfraRed remote control or keyboards"
786 Support for Samsung InfraRed remote control or keyboards.
789 tristate "Sony PS2/3/4 accessories"
792 depends on LEDS_CLASS
797 * Sony PS3 6-axis controllers
798 * Sony PS4 DualShock 4 controllers
800 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
801 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
804 bool "Sony PS2/3/4 accessories force feedback support"
806 select INPUT_FF_MEMLESS
808 Say Y here if you have a Sony PS2/3/4 accessory and want to enable
809 force feedback support for it.
812 tristate "Speedlink VAD Cezanne mouse support"
815 Support for Speedlink Vicious and Divine Cezanne mouse.
817 config HID_STEELSERIES
818 tristate "Steelseries SRW-S1 steering wheel support"
821 Support for Steelseries SRW-S1 steering wheel
824 tristate "Sunplus wireless desktop"
827 Support for Sunplus wireless desktop.
830 tristate "Synaptics RMI4 device support"
838 Support for Synaptics RMI4 touchpads.
839 Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
840 and want support for its special functionalities.
843 tristate "GreenAsia (Product ID 0x12) game controller support"
846 Say Y here if you have a GreenAsia (Product ID 0x12) based game
847 controller or adapter.
850 bool "GreenAsia (Product ID 0x12) force feedback support"
851 depends on HID_GREENASIA
852 select INPUT_FF_MEMLESS
854 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
855 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
856 and want to enable force feedback support for it.
858 config HID_HYPERV_MOUSE
859 tristate "Microsoft Hyper-V mouse driver"
862 Select this option to enable the Hyper-V mouse driver.
864 config HID_SMARTJOYPLUS
865 tristate "SmartJoy PLUS PS2/USB adapter support"
868 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
869 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
871 Note that DDR (Dance Dance Revolution) mode is not supported, nor
872 is pressure sensitive buttons on the pro models.
874 config SMARTJOYPLUS_FF
875 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
876 depends on HID_SMARTJOYPLUS
877 select INPUT_FF_MEMLESS
879 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
880 enable force feedback support for it.
883 tristate "TiVo Slide Bluetooth remote control support"
886 Say Y if you have a TiVo Slide Bluetooth remote control.
889 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
892 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
893 CLLRCMCE remote control.
896 tristate "ThingM blink(1) USB RGB LED"
898 depends on LEDS_CLASS
901 Support for the ThingM blink(1) USB RGB LED. This driver has been
902 merged into the generic hid led driver. Config symbol HID_THINGM
903 just selects HID_LED and will be removed soon.
905 config HID_THRUSTMASTER
906 tristate "ThrustMaster devices support"
909 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
910 a THRUSTMASTER Ferrari GT Rumble Wheel.
912 config THRUSTMASTER_FF
913 bool "ThrustMaster devices force feedback support"
914 depends on HID_THRUSTMASTER
915 select INPUT_FF_MEMLESS
917 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
918 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
919 Rumble Force or Force Feedback Wheel.
922 tristate "THQ PS3 uDraw tablet"
925 Say Y here if you want to use the THQ uDraw gaming tablet for
929 tristate "Wacom Intuos/Graphire tablet support (USB)"
936 Say Y here if you want to use the USB or BT version of the Wacom Intuos
939 To compile this driver as a module, choose M here: the
940 module will be called wacom.
943 tristate "Nintendo Wii / Wii U peripherals"
945 depends on LEDS_CLASS
947 select INPUT_FF_MEMLESS
949 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
950 devices are the Wii Remote and its extension devices, but also devices
951 based on the Wii Remote like the Wii U Pro Controller or the
954 Support for all official Nintendo extensions is available, however, 3rd
955 party extensions might not be supported. Please report these devices to:
956 http://github.com/dvdhrm/xwiimote/issues
958 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
959 the Wii U Gamepad) might be supported in the future. But currently
960 support is limited to Bluetooth based devices.
964 To compile this driver as a module, choose M here: the
965 module will be called hid-wiimote.
968 tristate "Xin-Mo non-fully compliant devices"
971 Support for Xin-Mo devices that are not fully compliant with the HID
972 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
973 if you have a Xin-Mo Dual Arcade controller.
976 tristate "Zeroplus based game controller support"
979 Say Y here if you have a Zeroplus based game controller.
982 bool "Zeroplus based game controller force feedback support"
983 depends on HID_ZEROPLUS
984 select INPUT_FF_MEMLESS
986 Say Y here if you have a Zeroplus based game controller and want
987 to have force feedback support for it.
990 tristate "Zydacron remote control support"
993 Support for Zydacron remote control.
995 config HID_SENSOR_HUB
996 tristate "HID Sensors framework support"
997 depends on HID && HAS_IOMEM
1001 Support for HID Sensor framework. This creates a MFD instance
1002 for a sensor hub and identifies all the sensors connected to it.
1003 Each sensor is registered as a MFD cell, so that sensor specific
1004 processing can be done in a separate driver. Each sensor
1005 drivers can use the service provided by this driver to register
1006 for events and handle data streams. Each sensor driver can format
1007 data and present to user mode using input or IIO interface.
1009 config HID_SENSOR_CUSTOM_SENSOR
1010 tristate "HID Sensors hub custom sensor support"
1011 depends on HID_SENSOR_HUB
1014 HID Sensor hub specification allows definition of some custom and
1015 generic sensors. Unlike other HID sensors, they can't be exported
1016 via Linux IIO because of custom fields. This is up to the manufacturer
1017 to decide how to interpret these special sensor ids and process in
1018 the user space. Currently some manufacturers are using these ids for
1019 sensor calibration and debugging other sensors. Manufacturers
1020 should't use these special custom sensor ids to export any of the
1022 Select this config option for custom/generic sensor support.
1025 tristate "Alps HID device support"
1028 Support for Alps I2C HID touchpads and StickPointer.
1029 Say Y here if you have a Alps touchpads over i2c-hid or usbhid
1030 and want support for its special functionalities.
1036 source "drivers/hid/usbhid/Kconfig"
1038 source "drivers/hid/i2c-hid/Kconfig"
1040 source "drivers/hid/intel-ish-hid/Kconfig"