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.
151 depends on LEDS_CLASS
152 depends on ASUS_WMI || ASUS_WMI=n
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 "BigBen Interactive Kids' gamepad support"
190 depends on LEDS_CLASS
191 select INPUT_FF_MEMLESS
193 Support for the "Kid-friendly Wired Controller" PS3OFMINIPAD
194 gamepad made by BigBen Interactive, originally sold as a PS3
195 accessory. This driver fixes input mapping and adds support for
196 force feedback effects and LEDs on the device.
199 tristate "Cherry Cymotion keyboard"
203 Support for Cherry Cymotion keyboard.
206 tristate "Chicony devices"
210 Support for Chicony Tactical pad and special keys on Chicony keyboards.
213 tristate "Corsair devices"
214 depends on HID && USB && LEDS_CLASS
216 Support for Corsair devices that are not fully compliant with the
224 tristate "Cougar devices"
227 Support for Cougar devices that are not fully compliant with the
231 - Cougar 500k Gaming Keyboard
234 tristate "Prodikeys PC-MIDI Keyboard support"
235 depends on HID && SND
238 Support for Prodikeys PC-MIDI Keyboard device support.
239 Say Y here to enable support for this device.
240 - Prodikeys PC-MIDI keyboard.
241 The Prodikeys PC-MIDI acts as a USB Audio device, with one MIDI
242 input and one MIDI output. These MIDI jacks appear as
243 a sound "card" in the ALSA sound system.
244 Note: if you say N here, this device will still function as a basic
245 multimedia keyboard, but will lack support for the musical keyboard
246 and some additional multimedia keys.
249 tristate "CMedia CM6533 HID audio jack controls"
252 Support for CMedia CM6533 HID audio jack controls.
255 tristate "Silicon Labs CP2112 HID USB-to-SMBus Bridge support"
256 depends on USB_HID && HIDRAW && I2C && GPIOLIB
257 select GPIOLIB_IRQCHIP
259 Support for Silicon Labs CP2112 HID USB to SMBus Master Bridge.
260 This is a HID device driver which registers as an i2c adapter
261 and gpiochip to expose these functions of the CP2112. The
262 customizable USB descriptor fields are exposed as sysfs attributes.
265 tristate "Cypress mouse and barcode readers"
269 Support for cypress mouse and barcode readers.
271 config HID_DRAGONRISE
272 tristate "DragonRise Inc. game controller"
275 Say Y here if you have DragonRise Inc. game controllers.
276 These might be branded as:
278 - Media-tech MT1504 "Rogue"
280 - Defender Game Master
283 bool "DragonRise Inc. force feedback"
284 depends on HID_DRAGONRISE
285 select INPUT_FF_MEMLESS
287 Say Y here if you want to enable force feedback support for DragonRise Inc.
291 tristate "EMS Production Inc. force feedback support"
293 select INPUT_FF_MEMLESS
295 Say Y here if you want to enable force feedback support for devices by
297 Currently the following devices are known to be supported:
298 - Trio Linker Plus II
301 tristate "ELAN USB Touchpad Support"
302 depends on LEDS_CLASS && USB_HID
304 Say Y to enable support for the USB ELAN touchpad
305 Currently the following devices are known to be supported:
306 - HP Pavilion X2 10-p0XX.
309 tristate "ELECOM HID devices"
312 Support for ELECOM devices:
313 - BM084 Bluetooth Mouse
314 - EX-G Trackballs (M-XT3DRBK, M-XT3URBK)
315 - DEFT Trackballs (M-DT1DRBK, M-DT1URBK, M-DT2DRBK, M-DT2URBK)
316 - HUGE Trackballs (M-HT1DRBK, M-HT1URBK)
319 tristate "ELO USB 4000/4500 touchscreen"
322 Support for the ELO USB 4000/4500 touchscreens. Note that this is for
323 different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
326 tristate "Ezkey BTC 8193 keyboard"
330 Support for Ezkey BTC 8193 keyboard.
333 tristate "Gembird Joypad"
336 Support for Gembird JPD-DualForce 2.
339 tristate "Google Fiber TV Box remote control support"
342 Support for Google Fiber TV Box remote controls
345 tristate "Holtek HID devices"
348 Support for Holtek based devices:
349 - Holtek On Line Grip based game controller
350 - Trust GXT 18 Gaming Keyboard
351 - Sharkoon Drakonia / Perixx MX-2000 gaming mice
352 - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
354 - SHARKOON DarkGlider Gaming mouse
355 - LEETGION Hellion Gaming Mouse
358 bool "Holtek On Line Grip force feedback support"
359 depends on HID_HOLTEK
360 select INPUT_FF_MEMLESS
362 Say Y here if you have a Holtek On Line Grip based game controller
363 and want to have force feedback support for it.
365 config HID_GOOGLE_HAMMER
366 tristate "Google Hammer Keyboard"
367 depends on USB_HID && LEDS_CLASS && MFD_CROS_EC
369 Say Y here if you have a Google Hammer device.
372 tristate "MSI GT68xR LED support"
373 depends on LEDS_CLASS && USB_HID
375 Say Y here if you want to enable support for the three MSI GT68xR LEDs
377 This driver support following modes:
378 - Normal: LEDs are fully on when enabled
379 - Audio: LEDs brightness depends on sound level
380 - Breathing: LEDs brightness varies at human breathing rate
382 Currently the following devices are know to be supported:
386 tristate "Keytouch HID devices"
389 Support for Keytouch HID devices not fully compliant with
390 the specification. Currently supported:
394 tristate "KYE/Genius devices"
397 Support for KYE/Genius devices not fully compliant with HID standard:
399 - EasyPen i405X tablet
400 - MousePen i608X tablet
401 - EasyPen M610X tablet
407 Support for UC-Logic and Huion tablets.
413 Support for Waltop tablets.
416 tristate "Gyration remote control"
419 Support for Gyration remote control.
422 tristate "ION iCade arcade controller"
425 Support for the ION iCade arcade controller to work as a joystick.
427 To compile this driver as a module, choose M here: the
428 module will be called hid-icade.
431 tristate "ITE devices"
435 Support for ITE devices not fully compliant with HID standard.
438 tristate "Jabra USB HID Driver"
441 Support for Jabra USB HID devices.
443 Prevents mapping of vendor defined HID usages to input events. Without
444 this driver HID reports from Jabra devices may incorrectly be seen as
446 Say M here if you may ever plug in a Jabra USB device.
449 tristate "Twinhan IR remote control"
452 Support for Twinhan IR remote control.
454 config HID_KENSINGTON
455 tristate "Kensington Slimblade Trackball"
459 Support for Kensington Slimblade Trackball.
465 Support for LC-Power RC1000MCE RF remote control.
468 tristate "Simple RGB LED support"
470 depends on LEDS_CLASS
472 Support for simple RGB LED devices. Currently supported are:
473 - Riso Kagaku Webmail Notifier
474 - Dream Cheeky Webmail Notifier and Friends Alert
476 - Delcom Visual Signal Indicator Generation 2
479 To compile this driver as a module, choose M here: the
480 module will be called hid-led.
483 tristate "Lenovo / Thinkpad devices"
488 Support for IBM/Lenovo devices that are not fully compliant with HID standard.
490 Say Y if you want support for horizontal scrolling of the IBM/Lenovo
491 Scrollpoint mice or the non-compliant features of the Lenovo Thinkpad
492 standalone keyboards, e.g:
493 - ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
495 - ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
496 - ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
499 tristate "Logitech devices"
503 Support for Logitech devices that are not fully compliant with HID standard.
505 config HID_LOGITECH_DJ
506 tristate "Logitech Unifying receivers full support"
508 depends on HID_LOGITECH
509 select HID_LOGITECH_HIDPP
511 Say Y if you want support for Logitech Unifying receivers and devices.
512 Unifying receivers are capable of pairing up to 6 Logitech compliant
513 devices to the same receiver. Without this driver it will be handled by
514 generic USB_HID driver and all incoming events will be multiplexed
515 into a single mouse and a single keyboard device.
517 config HID_LOGITECH_HIDPP
518 tristate "Logitech HID++ devices support"
519 depends on HID_LOGITECH
522 Support for Logitech devices relyingon the HID++ Logitech specification
524 Say Y if you want support for Logitech devices relying on the HID++
525 specification. Such devices are the various Logitech Touchpads (T650,
526 T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
530 bool "Logitech force feedback support"
531 depends on HID_LOGITECH
532 select INPUT_FF_MEMLESS
534 Say Y here if you have one of these devices:
535 - Logitech WingMan Cordless RumblePad
536 - Logitech WingMan Cordless RumblePad 2
537 - Logitech WingMan Force 3D
539 and if you want to enable force feedback for them.
540 Note: if you say N here, this device will still be supported, but without
543 config LOGIRUMBLEPAD2_FF
544 bool "Logitech force feedback support (variant 2)"
545 depends on HID_LOGITECH
546 select INPUT_FF_MEMLESS
548 Say Y here if you want to enable force feedback support for:
550 - Logitech Rumblepad 2
551 - Logitech Formula Vibration Feedback Wheel
554 bool "Logitech Flight System G940 force feedback support"
555 depends on HID_LOGITECH
556 select INPUT_FF_MEMLESS
558 Say Y here if you want to enable force feedback support for Logitech
559 Flight System G940 devices.
562 bool "Logitech wheels configuration and force feedback support"
563 depends on HID_LOGITECH
564 select INPUT_FF_MEMLESS
567 Say Y here if you want to enable force feedback and range setting(*)
568 support for following Logitech wheels:
572 - Logitech Driving Force
573 - Logitech Driving Force Pro (*)
574 - Logitech Driving Force GT (*)
575 - Logitech Driving Force EX/RX
576 - Logitech Driving Force Wireless
577 - Logitech Speed Force Wireless
578 - Logitech MOMO Force
579 - Logitech MOMO Racing Force
580 - Logitech Formula Force GP
581 - Logitech Formula Force EX/RX
582 - Logitech Wingman Formula Force GP
584 config HID_MAGICMOUSE
585 tristate "Apple Magic Mouse/Trackpad multi-touch support"
588 Support for the Apple Magic Mouse/Trackpad multi-touch.
590 Say Y here if you want support for the multi-touch features of the
591 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
594 tristate "Mayflash game controller adapter force feedback"
596 select INPUT_FF_MEMLESS
598 Say Y here if you have HJZ Mayflash PS3 game controller adapters
599 and want to enable force feedback support.
602 tristate "Redragon keyboards"
606 Support for Redragon keyboards that need fix-ups to work properly.
609 tristate "Microsoft non-fully HID-compliant devices"
612 select INPUT_FF_MEMLESS
614 Support for Microsoft devices that are not fully compliant with HID standard.
617 tristate "Monterey Genius KB29E keyboard"
621 Support for Monterey Genius KB29E.
623 config HID_MULTITOUCH
624 tristate "HID Multitouch panels"
627 Generic support for HID multitouch panels.
629 Say Y here if you have one of the following devices:
630 - 3M PCT touch screens
631 - ActionStar dual touch panels
633 - Cando dual touch panels
637 - Cypress TrueTouch panels
638 - Elan Microelectronics touch panels
639 - Elo TouchSystems IntelliTouch Plus panels
640 - GeneralTouch 'Sensing Win7-TwoFinger' panels
642 - Hanvon dual touch panels
643 - Ilitek dual touch panels
644 - IrTouch Infrared USB panels
645 - LG Display panels (Dell ST2220Tc)
646 - Lumio CrystalTouch panels
647 - MosArt dual-touch panels
648 - Panasonic multitouch panels
649 - PenMount dual touch panels
650 - Perixx Peripad 701 touchpad
651 - PixArt optical touch screen
652 - Pixcir dual touch panels
654 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
655 - SiS multitouch panels
656 - Stantum multitouch panels
657 - Touch International Panels
659 - Wistron optical touch panels
660 - XAT optical touch panels
661 - Xiroku optical touch panels
662 - Zytronic touch panels
666 To compile this driver as a module, choose M here: the
667 module will be called hid-multitouch.
670 tristate "NTI keyboard adapters"
672 Support for the "extra" Sun keyboard keys on keyboards attached
673 through Network Technologies USB-SUN keyboard adapters.
676 tristate "N-Trig touch screen"
679 Support for N-Trig touch screen.
682 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
685 There are certain devices which have LogicalMaximum wrong in the keyboard
686 usage page of their report descriptor. The most prevailing ones so far
687 are manufactured by Ortek, thus the name of the driver. Currently
688 supported devices by this driver are
692 - Skycable wireless presenter
694 config HID_PANTHERLORD
695 tristate "Pantherlord/GreenAsia game controller"
698 Say Y here if you have a PantherLord/GreenAsia based game controller
701 config PANTHERLORD_FF
702 bool "Pantherlord force feedback support"
703 depends on HID_PANTHERLORD
704 select INPUT_FF_MEMLESS
706 Say Y here if you have a PantherLord/GreenAsia based game controller
707 or adapter and want to enable force feedback support for it.
710 tristate "Penmount touch device"
713 This selects a driver for the PenMount 6000 touch controller.
715 The driver works around a problem in the report descript allowing
716 the userspace to touch events instead of mouse events.
718 Say Y here if you have a Penmount based touch controller.
721 tristate "Petalynx Maxter remote control"
724 Support for Petalynx Maxter remote control.
727 tristate "PicoLCD (graphic version)"
730 This provides support for Minibox PicoLCD devices, currently
731 only the graphical ones are supported.
733 This includes support for the following device features:
735 - Switching between Firmware and Flash mode
736 - EEProm / Flash access (via debugfs)
737 Features selectively enabled:
738 - Framebuffer for monochrome 256x64 display
741 - General purpose outputs
742 Features that are not (yet) supported:
745 config HID_PICOLCD_FB
746 bool "Framebuffer support" if EXPERT
748 depends on HID_PICOLCD
749 depends on HID_PICOLCD=FB || FB=y
750 select FB_DEFERRED_IO
751 select FB_SYS_FILLRECT
752 select FB_SYS_COPYAREA
753 select FB_SYS_IMAGEBLIT
756 Provide access to PicoLCD's 256x64 monochrome display via a
759 config HID_PICOLCD_BACKLIGHT
760 bool "Backlight control" if EXPERT
762 depends on HID_PICOLCD
763 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
765 Provide access to PicoLCD's backlight control via backlight
768 config HID_PICOLCD_LCD
769 bool "Contrast control" if EXPERT
771 depends on HID_PICOLCD
772 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
774 Provide access to PicoLCD's LCD contrast via lcd class.
776 config HID_PICOLCD_LEDS
777 bool "GPO via leds class" if EXPERT
779 depends on HID_PICOLCD
780 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
782 Provide access to PicoLCD's GPO pins via leds class.
784 config HID_PICOLCD_CIR
785 bool "CIR via RC class" if EXPERT
787 depends on HID_PICOLCD
788 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
790 Provide access to PicoLCD's CIR interface via remote control (LIRC).
792 config HID_PLANTRONICS
793 tristate "Plantronics USB HID Driver"
796 Provides HID support for Plantronics USB audio devices.
797 Correctly maps vendor unique volume up/down HID usages to
798 KEY_VOLUMEUP and KEY_VOLUMEDOWN events and prevents core mapping
799 of other vendor unique HID usages to random mouse events.
801 Say M here if you may ever plug in a Plantronics USB audio device.
804 tristate "Primax non-fully HID-compliant devices"
807 Support for Primax devices that are not fully compliant with the
811 tristate "Retrode 2 USB adapter for vintage video games"
815 * Retrode 2 cartridge and controller adapter
818 tristate "Roccat device support"
821 Support for Roccat devices.
822 Say Y here if you have a Roccat mouse or keyboard and want
823 support for its special functionalities.
826 tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
829 Support for Saitek devices that are not fully compliant with the
833 - PS1000 Dual Analog Pad
834 - Saitek R.A.T.7, R.A.T.9, M.M.O.7 Gaming Mice
835 - Mad Catz R.A.T.5, R.A.T.9 Gaming Mice
838 tristate "Samsung InfraRed remote control or keyboards"
841 Support for Samsung InfraRed remote control or keyboards.
844 tristate "Sony PS2/3/4 accessories"
847 depends on LEDS_CLASS
852 * Sony PS3 6-axis controllers
853 * Sony PS4 DualShock 4 controllers
855 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
856 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
859 bool "Sony PS2/3/4 accessories force feedback support"
861 select INPUT_FF_MEMLESS
863 Say Y here if you have a Sony PS2/3/4 accessory and want to enable
864 force feedback support for it.
867 tristate "Speedlink VAD Cezanne mouse support"
870 Support for Speedlink Vicious and Divine Cezanne mouse.
873 tristate "Steam Controller support"
877 Say Y here if you have a Steam Controller if you want to use it
878 without running the Steam Client. It supports both the wired and
879 the wireless adaptor.
881 config HID_STEELSERIES
882 tristate "Steelseries SRW-S1 steering wheel support"
885 Support for Steelseries SRW-S1 steering wheel
888 tristate "Sunplus wireless desktop"
891 Support for Sunplus wireless desktop.
894 tristate "Synaptics RMI4 device support"
902 Support for Synaptics RMI4 touchpads.
903 Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
904 and want support for its special functionalities.
907 tristate "GreenAsia (Product ID 0x12) game controller support"
910 Say Y here if you have a GreenAsia (Product ID 0x12) based game
911 controller or adapter.
914 bool "GreenAsia (Product ID 0x12) force feedback support"
915 depends on HID_GREENASIA
916 select INPUT_FF_MEMLESS
918 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
919 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
920 and want to enable force feedback support for it.
922 config HID_HYPERV_MOUSE
923 tristate "Microsoft Hyper-V mouse driver"
926 Select this option to enable the Hyper-V mouse driver.
928 config HID_SMARTJOYPLUS
929 tristate "SmartJoy PLUS PS2/USB adapter support"
932 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
933 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
935 Note that DDR (Dance Dance Revolution) mode is not supported, nor
936 is pressure sensitive buttons on the pro models.
938 config SMARTJOYPLUS_FF
939 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
940 depends on HID_SMARTJOYPLUS
941 select INPUT_FF_MEMLESS
943 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
944 enable force feedback support for it.
947 tristate "TiVo Slide Bluetooth remote control support"
950 Say Y if you have a TiVo Slide Bluetooth remote control.
953 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
956 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
957 CLLRCMCE remote control.
960 tristate "ThingM blink(1) USB RGB LED"
962 depends on LEDS_CLASS
965 Support for the ThingM blink(1) USB RGB LED. This driver has been
966 merged into the generic hid led driver. Config symbol HID_THINGM
967 just selects HID_LED and will be removed soon.
969 config HID_THRUSTMASTER
970 tristate "ThrustMaster devices support"
973 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
974 a THRUSTMASTER Ferrari GT Rumble Wheel.
976 config THRUSTMASTER_FF
977 bool "ThrustMaster devices force feedback support"
978 depends on HID_THRUSTMASTER
979 select INPUT_FF_MEMLESS
981 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
982 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
983 Rumble Force or Force Feedback Wheel.
986 tristate "THQ PS3 uDraw tablet"
989 Say Y here if you want to use the THQ uDraw gaming tablet for
993 tristate "Wacom Intuos/Graphire tablet support (USB)"
1000 Say Y here if you want to use the USB or BT version of the Wacom Intuos
1003 To compile this driver as a module, choose M here: the
1004 module will be called wacom.
1007 tristate "Nintendo Wii / Wii U peripherals"
1009 depends on LEDS_CLASS
1011 select INPUT_FF_MEMLESS
1013 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
1014 devices are the Wii Remote and its extension devices, but also devices
1015 based on the Wii Remote like the Wii U Pro Controller or the
1018 Support for all official Nintendo extensions is available, however, 3rd
1019 party extensions might not be supported. Please report these devices to:
1020 http://github.com/dvdhrm/xwiimote/issues
1022 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
1023 the Wii U Gamepad) might be supported in the future. But currently
1024 support is limited to Bluetooth based devices.
1028 To compile this driver as a module, choose M here: the
1029 module will be called hid-wiimote.
1032 tristate "Xin-Mo non-fully compliant devices"
1035 Support for Xin-Mo devices that are not fully compliant with the HID
1036 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
1037 if you have a Xin-Mo Dual Arcade controller.
1040 tristate "Zeroplus based game controller support"
1043 Say Y here if you have a Zeroplus based game controller.
1046 bool "Zeroplus based game controller force feedback support"
1047 depends on HID_ZEROPLUS
1048 select INPUT_FF_MEMLESS
1050 Say Y here if you have a Zeroplus based game controller and want
1051 to have force feedback support for it.
1054 tristate "Zydacron remote control support"
1057 Support for Zydacron remote control.
1059 config HID_SENSOR_HUB
1060 tristate "HID Sensors framework support"
1061 depends on HID && HAS_IOMEM
1065 Support for HID Sensor framework. This creates a MFD instance
1066 for a sensor hub and identifies all the sensors connected to it.
1067 Each sensor is registered as a MFD cell, so that sensor specific
1068 processing can be done in a separate driver. Each sensor
1069 drivers can use the service provided by this driver to register
1070 for events and handle data streams. Each sensor driver can format
1071 data and present to user mode using input or IIO interface.
1073 config HID_SENSOR_CUSTOM_SENSOR
1074 tristate "HID Sensors hub custom sensor support"
1075 depends on HID_SENSOR_HUB
1078 HID Sensor hub specification allows definition of some custom and
1079 generic sensors. Unlike other HID sensors, they can't be exported
1080 via Linux IIO because of custom fields. This is up to the manufacturer
1081 to decide how to interpret these special sensor ids and process in
1082 the user space. Currently some manufacturers are using these ids for
1083 sensor calibration and debugging other sensors. Manufacturers
1084 should't use these special custom sensor ids to export any of the
1086 Select this config option for custom/generic sensor support.
1089 tristate "Alps HID device support"
1092 Support for Alps I2C HID touchpads and StickPointer.
1093 Say Y here if you have a Alps touchpads over i2c-hid or usbhid
1094 and want support for its special functionalities.
1100 source "drivers/hid/usbhid/Kconfig"
1102 source "drivers/hid/i2c-hid/Kconfig"
1104 source "drivers/hid/intel-ish-hid/Kconfig"