2 # HID driver configuration
8 tristate "HID bus support"
12 A human interface device (HID) is a type of computer device that
13 interacts directly with and takes input from humans. The term "HID"
14 most commonly used to refer to the USB-HID specification, but other
15 devices (such as, but not strictly limited to, Bluetooth) are
16 designed using HID specification (this involves certain keyboards,
17 mice, tablets, etc). This option adds the HID bus to the kernel,
18 together with generic HID layer code. The HID devices are added and
19 removed from the HID bus by the transport-layer drivers, such as
20 usbhid (USB_HID) and hidp (BT_HIDP).
22 For docs and specs, see http://www.usb.org/developers/hidpage/
28 config HID_BATTERY_STRENGTH
29 bool "Battery level reporting for HID devices"
30 depends on HID && POWER_SUPPLY && HID = POWER_SUPPLY
33 This option adds support of reporting battery strength (for HID devices
34 that support this feature) through power_supply class so that userspace
35 tools, such as upower, can display it.
38 bool "/dev/hidraw raw HID device support"
41 Say Y here if you want to support HID devices (from the USB
42 specification standpoint) that aren't strictly user interface
43 devices, like monitor controls and Uninterruptable Power Supplies.
45 This module supports these devices separately using a separate
46 event interface on /dev/hidraw.
48 There is also a /dev/hiddev configuration option in the USB HID
49 configuration menu. In comparison to hiddev, this device does not process
50 the hid events at all (no parsing, no lookups). This lets applications
51 to work on raw hid events when they want to, and avoid using transport-specific
52 userspace libhid/libusb libraries.
57 tristate "User-space I/O driver support for HID subsystem"
61 Say Y here if you want to provide HID I/O Drivers from user-space.
62 This allows to write I/O drivers in user-space and feed the data from
63 the device into the kernel. The kernel parses the HID reports, loads the
64 corresponding HID Device Driver or provides input devices on top of your
67 This driver cannot be used to parse HID-reports in user-space and write
68 special HID-drivers. You should use hidraw for that.
69 Instead, this driver allows to write the transport-layer driver in
70 user-space like USB-HID and Bluetooth-HID do in kernel-space.
74 To compile this driver as a module, choose M here: the
75 module will be called uhid.
78 tristate "Generic HID driver"
82 Support for generic devices on the HID bus. This includes most
83 keyboards and mice, joysticks, tablets and digitizers.
85 To compile this driver as a module, choose M here: the module
86 will be called hid-generic.
90 menu "Special HID drivers"
94 tristate "A4 tech mice" if EXPERT
98 Support for A4 tech X5 and WOP-35 / Trust 450L mice.
101 tristate "ACRUX game controller support"
104 Say Y here if you want to enable support for ACRUX game controllers.
107 bool "ACRUX force feedback support"
109 select INPUT_FF_MEMLESS
111 Say Y here if you want to enable force feedback support for ACRUX
115 tristate "Apple {i,Power,Mac}Books" if EXPERT
119 Support for some Apple devices which less or more break
122 Say Y here if you want support for keyboards of Apple iBooks, PowerBooks,
123 MacBooks, MacBook Pros and Apple Aluminum.
126 tristate "Apple infrared receiver"
129 Support for Apple infrared remote control. All the Apple computers from
130 2005 onwards include such a port, except the unibody Macbook (2009),
131 and Mac Pros. This receiver is also used in the Apple TV set-top box
132 prior to the 2010 model.
134 Say Y here if you want support for Apple infrared remote control.
140 Support for Aureal Cy se W-01RN Remote Controller and other Aureal derived remotes.
143 tristate "Belkin Flip KVM and Wireless keyboard" if EXPERT
147 Support for Belkin Flip KVM and Wireless keyboard.
150 tristate "Cherry Cymotion keyboard" if EXPERT
154 Support for Cherry Cymotion keyboard.
157 tristate "Chicony Tactical pad" if EXPERT
161 Support for Chicony Tactical pad.
164 tristate "Prodikeys PC-MIDI Keyboard support"
165 depends on HID && SND
168 Support for Prodikeys PC-MIDI Keyboard device support.
169 Say Y here to enable support for this device.
170 - Prodikeys PC-MIDI keyboard.
171 The Prodikeys PC-MIDI acts as a USB Audio device, with one MIDI
172 input and one MIDI output. These MIDI jacks appear as
173 a sound "card" in the ALSA sound system.
174 Note: if you say N here, this device will still function as a basic
175 multimedia keyboard, but will lack support for the musical keyboard
176 and some additional multimedia keys.
179 tristate "Cypress mouse and barcode readers" if EXPERT
183 Support for cypress mouse and barcode readers.
185 config HID_DRAGONRISE
186 tristate "DragonRise Inc. game controller"
189 Say Y here if you have DragonRise Inc. game controllers.
190 These might be branded as:
192 - Media-tech MT1504 "Rogue"
194 - Defender Game Master
197 bool "DragonRise Inc. force feedback"
198 depends on HID_DRAGONRISE
199 select INPUT_FF_MEMLESS
201 Say Y here if you want to enable force feedback support for DragonRise Inc.
205 tristate "EMS Production Inc. force feedback support"
207 select INPUT_FF_MEMLESS
209 Say Y here if you want to enable force feedback support for devices by
211 Currently the following devices are known to be supported:
212 - Trio Linker Plus II
215 tristate "ELECOM BM084 bluetooth mouse"
218 Support for the ELECOM BM084 (bluetooth mouse).
221 tristate "ELO USB 4000/4500 touchscreen"
224 Support for the ELO USB 4000/4500 touchscreens. Note that this is for
225 different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
228 tristate "Ezkey BTC 8193 keyboard" if EXPERT
232 Support for Ezkey BTC 8193 keyboard.
235 tristate "Holtek HID devices"
238 Support for Holtek based devices:
239 - Holtek On Line Grip based game controller
240 - Trust GXT 18 Gaming Keyboard
241 - Sharkoon Drakonia / Perixx MX-2000 gaming mice
242 - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
246 bool "Holtek On Line Grip force feedback support"
247 depends on HID_HOLTEK
248 select INPUT_FF_MEMLESS
250 Say Y here if you have a Holtek On Line Grip based game controller
251 and want to have force feedback support for it.
254 tristate "Huion tablets"
257 Support for Huion 580 tablet.
260 tristate "Keytouch HID devices"
263 Support for Keytouch HID devices not fully compliant with
264 the specification. Currently supported:
268 tristate "KYE/Genius devices"
271 Support for KYE/Genius devices not fully compliant with HID standard:
273 - EasyPen i405X tablet
274 - MousePen i608X tablet
275 - EasyPen M610X tablet
281 Support for UC-Logic tablets.
287 Support for Waltop tablets.
290 tristate "Gyration remote control"
293 Support for Gyration remote control.
296 tristate "ION iCade arcade controller"
299 Support for the ION iCade arcade controller to work as a joystick.
301 To compile this driver as a module, choose M here: the
302 module will be called hid-icade.
305 tristate "Twinhan IR remote control"
308 Support for Twinhan IR remote control.
310 config HID_KENSINGTON
311 tristate "Kensington Slimblade Trackball" if EXPERT
315 Support for Kensington Slimblade Trackball.
321 Support for LC-Power RC1000MCE RF remote control.
323 config HID_LENOVO_TPKBD
324 tristate "Lenovo ThinkPad USB Keyboard with TrackPoint"
329 Support for the Lenovo ThinkPad USB Keyboard with TrackPoint.
331 Say Y here if you have a Lenovo ThinkPad USB Keyboard with TrackPoint
332 and would like to use device-specific features like changing the
333 sensitivity of the trackpoint, using the microphone mute button or
334 controlling the mute and microphone mute LEDs.
337 tristate "Logitech devices" if EXPERT
341 Support for Logitech devices that are not fully compliant with HID standard.
343 config HID_LOGITECH_DJ
344 tristate "Logitech Unifying receivers full support"
345 depends on HID_LOGITECH
347 Say Y if you want support for Logitech Unifying receivers and devices.
348 Unifying receivers are capable of pairing up to 6 Logitech compliant
349 devices to the same receiver. Without this driver it will be handled by
350 generic USB_HID driver and all incoming events will be multiplexed
351 into a single mouse and a single keyboard device.
354 bool "Logitech force feedback support"
355 depends on HID_LOGITECH
356 select INPUT_FF_MEMLESS
358 Say Y here if you have one of these devices:
359 - Logitech WingMan Cordless RumblePad
360 - Logitech WingMan Cordless RumblePad 2
361 - Logitech WingMan Force 3D
362 - Logitech Formula Force EX
363 - Logitech WingMan Formula Force GP
364 - Logitech MOMO Force wheel
366 and if you want to enable force feedback for them.
367 Note: if you say N here, this device will still be supported, but without
370 config LOGIRUMBLEPAD2_FF
371 bool "Logitech RumblePad/Rumblepad 2 force feedback support"
372 depends on HID_LOGITECH
373 select INPUT_FF_MEMLESS
375 Say Y here if you want to enable force feedback support for Logitech
376 RumblePad and Rumblepad 2 devices.
379 bool "Logitech Flight System G940 force feedback support"
380 depends on HID_LOGITECH
381 select INPUT_FF_MEMLESS
383 Say Y here if you want to enable force feedback support for Logitech
384 Flight System G940 devices.
387 bool "Logitech wheels configuration and force feedback support"
388 depends on HID_LOGITECH
389 select INPUT_FF_MEMLESS
392 Say Y here if you want to enable force feedback and range setting
393 support for following Logitech wheels:
394 - Logitech Driving Force
395 - Logitech Driving Force Pro
396 - Logitech Driving Force GT
399 - Logitech MOMO/MOMO 2
400 - Logitech Formula Force EX
402 config HID_MAGICMOUSE
403 tristate "Apple Magic Mouse/Trackpad multi-touch support"
406 Support for the Apple Magic Mouse/Trackpad multi-touch.
408 Say Y here if you want support for the multi-touch features of the
409 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
412 tristate "Microsoft non-fully HID-compliant devices" if EXPERT
416 Support for Microsoft devices that are not fully compliant with HID standard.
419 tristate "Monterey Genius KB29E keyboard" if EXPERT
423 Support for Monterey Genius KB29E.
425 config HID_MULTITOUCH
426 tristate "HID Multitouch panels"
429 Generic support for HID multitouch panels.
431 Say Y here if you have one of the following devices:
432 - 3M PCT touch screens
433 - ActionStar dual touch panels
435 - Cando dual touch panels
438 - Cypress TrueTouch panels
439 - Elan Microelectronics touch panels
440 - Elo TouchSystems IntelliTouch Plus panels
441 - GeneralTouch 'Sensing Win7-TwoFinger' panels
443 - Hanvon dual touch panels
444 - Ilitek dual touch panels
445 - IrTouch Infrared USB panels
446 - LG Display panels (Dell ST2220Tc)
447 - Lumio CrystalTouch panels
448 - MosArt dual-touch panels
449 - Panasonic multitouch panels
450 - PenMount dual touch panels
451 - Perixx Peripad 701 touchpad
452 - PixArt optical touch screen
453 - Pixcir dual touch panels
455 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
456 - SiS multitouch panels
457 - Stantum multitouch panels
458 - Touch International Panels
460 - XAT optical touch panels
461 - Xiroku optical touch panels
462 - Zytronic touch panels
466 To compile this driver as a module, choose M here: the
467 module will be called hid-multitouch.
470 tristate "N-Trig touch screen"
473 Support for N-Trig touch screen.
476 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
479 There are certain devices which have LogicalMaximum wrong in the keyboard
480 usage page of their report descriptor. The most prevailing ones so far
481 are manufactured by Ortek, thus the name of the driver. Currently
482 supported devices by this driver are
486 - Skycable wireless presenter
488 config HID_PANTHERLORD
489 tristate "Pantherlord/GreenAsia game controller"
492 Say Y here if you have a PantherLord/GreenAsia based game controller
495 config PANTHERLORD_FF
496 bool "Pantherlord force feedback support"
497 depends on HID_PANTHERLORD
498 select INPUT_FF_MEMLESS
500 Say Y here if you have a PantherLord/GreenAsia based game controller
501 or adapter and want to enable force feedback support for it.
504 tristate "Petalynx Maxter remote control"
507 Support for Petalynx Maxter remote control.
510 tristate "PicoLCD (graphic version)"
513 This provides support for Minibox PicoLCD devices, currently
514 only the graphical ones are supported.
516 This includes support for the following device features:
518 - Switching between Firmware and Flash mode
519 - EEProm / Flash access (via debugfs)
520 Features selectively enabled:
521 - Framebuffer for monochrome 256x64 display
524 - General purpose outputs
525 Features that are not (yet) supported:
528 config HID_PICOLCD_FB
529 bool "Framebuffer support" if EXPERT
531 depends on HID_PICOLCD
532 depends on HID_PICOLCD=FB || FB=y
533 select FB_DEFERRED_IO
534 select FB_SYS_FILLRECT
535 select FB_SYS_COPYAREA
536 select FB_SYS_IMAGEBLIT
539 Provide access to PicoLCD's 256x64 monochrome display via a
542 config HID_PICOLCD_BACKLIGHT
543 bool "Backlight control" if EXPERT
545 depends on HID_PICOLCD
546 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
548 Provide access to PicoLCD's backlight control via backlight
551 config HID_PICOLCD_LCD
552 bool "Contrast control" if EXPERT
554 depends on HID_PICOLCD
555 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
557 Provide access to PicoLCD's LCD contrast via lcd class.
559 config HID_PICOLCD_LEDS
560 bool "GPO via leds class" if EXPERT
562 depends on HID_PICOLCD
563 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
565 Provide access to PicoLCD's GPO pins via leds class.
567 config HID_PICOLCD_CIR
568 bool "CIR via RC class" if EXPERT
570 depends on HID_PICOLCD
571 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
573 Provide access to PicoLCD's CIR interface via remote control (LIRC).
576 tristate "Primax non-fully HID-compliant devices"
579 Support for Primax devices that are not fully compliant with the
583 tristate "Roccat device support"
586 Support for Roccat devices.
587 Say Y here if you have a Roccat mouse or keyboard and want
588 support for its special functionalities.
591 tristate "Saitek non-fully HID-compliant devices"
594 Support for Saitek devices that are not fully compliant with the
597 Currently only supports the PS1000 controller.
600 tristate "Samsung InfraRed remote control or keyboards"
603 Support for Samsung InfraRed remote control or keyboards.
606 tristate "Sony PS2/3 accessories"
609 depends on LEDS_CLASS
613 * Sony PS3 6-axis controllers
615 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
616 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
619 tristate "Speedlink VAD Cezanne mouse support"
622 Support for Speedlink Vicious and Divine Cezanne mouse.
624 config HID_STEELSERIES
625 tristate "Steelseries SRW-S1 steering wheel support"
628 Support for Steelseries SRW-S1 steering wheel
631 tristate "Sunplus wireless desktop"
634 Support for Sunplus wireless desktop.
637 tristate "GreenAsia (Product ID 0x12) game controller support"
640 Say Y here if you have a GreenAsia (Product ID 0x12) based game
641 controller or adapter.
644 bool "GreenAsia (Product ID 0x12) force feedback support"
645 depends on HID_GREENASIA
646 select INPUT_FF_MEMLESS
648 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
649 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
650 and want to enable force feedback support for it.
652 config HID_HYPERV_MOUSE
653 tristate "Microsoft Hyper-V mouse driver"
656 Select this option to enable the Hyper-V mouse driver.
658 config HID_SMARTJOYPLUS
659 tristate "SmartJoy PLUS PS2/USB adapter support"
662 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
663 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
665 Note that DDR (Dance Dance Revolution) mode is not supported, nor
666 is pressure sensitive buttons on the pro models.
668 config SMARTJOYPLUS_FF
669 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
670 depends on HID_SMARTJOYPLUS
671 select INPUT_FF_MEMLESS
673 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
674 enable force feedback support for it.
677 tristate "TiVo Slide Bluetooth remote control support"
680 Say Y if you have a TiVo Slide Bluetooth remote control.
683 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
686 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
687 CLLRCMCE remote control.
690 tristate "ThingM blink(1) USB RGB LED"
692 depends on LEDS_CLASS
694 Support for the ThingM blink(1) USB RGB LED. This driver registers a
695 Linux LED class instance, plus additional sysfs attributes to control
696 RGB colors, fade time and playing. The device is exposed through hidraw
697 to access other functions.
699 config HID_THRUSTMASTER
700 tristate "ThrustMaster devices support"
703 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
704 a THRUSTMASTER Ferrari GT Rumble Wheel.
706 config THRUSTMASTER_FF
707 bool "ThrustMaster devices force feedback support"
708 depends on HID_THRUSTMASTER
709 select INPUT_FF_MEMLESS
711 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
712 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
713 Rumble Force or Force Feedback Wheel.
716 tristate "Wacom Bluetooth devices support"
718 depends on LEDS_CLASS
721 Support for Wacom Graphire Bluetooth and Intuos4 WL tablets.
724 tristate "Nintendo Wii / Wii U peripherals"
726 depends on LEDS_CLASS
728 select INPUT_FF_MEMLESS
730 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
731 devices are the Wii Remote and its extension devices, but also devices
732 based on the Wii Remote like the Wii U Pro Controller or the
735 Support for all official Nintendo extensions is available, however, 3rd
736 party extensions might not be supported. Please report these devices to:
737 http://github.com/dvdhrm/xwiimote/issues
739 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
740 the Wii U Gamepad) might be supported in the future. But currently
741 support is limited to Bluetooth based devices.
745 To compile this driver as a module, choose M here: the
746 module will be called hid-wiimote.
749 tristate "Xin-Mo non-fully compliant devices"
752 Support for Xin-Mo devices that are not fully compliant with the HID
753 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
754 if you have a Xin-Mo Dual Arcade controller.
757 tristate "Zeroplus based game controller support"
760 Say Y here if you have a Zeroplus based game controller.
763 bool "Zeroplus based game controller force feedback support"
764 depends on HID_ZEROPLUS
765 select INPUT_FF_MEMLESS
767 Say Y here if you have a Zeroplus based game controller and want
768 to have force feedback support for it.
771 tristate "Zydacron remote control support"
774 Support for Zydacron remote control.
776 config HID_SENSOR_HUB
777 tristate "HID Sensors framework support"
782 Support for HID Sensor framework. This creates a MFD instance
783 for a sensor hub and identifies all the sensors connected to it.
784 Each sensor is registered as a MFD cell, so that sensor specific
785 processing can be done in a separate driver. Each sensor
786 drivers can use the service provided by this driver to register
787 for events and handle data streams. Each sensor driver can format
788 data and present to user mode using input or IIO interface.
794 source "drivers/hid/usbhid/Kconfig"
796 source "drivers/hid/i2c-hid/Kconfig"