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 "Ezkey BTC 8193 keyboard" if EXPERT
225 Support for Ezkey BTC 8193 keyboard.
228 tristate "Holtek HID devices"
231 Support for Holtek based devices:
232 - Holtek On Line Grip based game controller
233 - Trust GXT 18 Gaming Keyboard
236 bool "Holtek On Line Grip force feedback support"
237 depends on HID_HOLTEK
238 select INPUT_FF_MEMLESS
240 Say Y here if you have a Holtek On Line Grip based game controller
241 and want to have force feedback support for it.
244 tristate "Keytouch HID devices"
247 Support for Keytouch HID devices not fully compliant with
248 the specification. Currently supported:
252 tristate "KYE/Genius devices"
255 Support for KYE/Genius devices not fully compliant with HID standard:
257 - EasyPen i405X tablet
258 - MousePen i608X tablet
259 - EasyPen M610X tablet
265 Support for UC-Logic tablets.
271 Support for Waltop tablets.
274 tristate "Gyration remote control"
277 Support for Gyration remote control.
280 tristate "ION iCade arcade controller"
283 Support for the ION iCade arcade controller to work as a joystick.
285 To compile this driver as a module, choose M here: the
286 module will be called hid-icade.
289 tristate "Twinhan IR remote control"
292 Support for Twinhan IR remote control.
294 config HID_KENSINGTON
295 tristate "Kensington Slimblade Trackball" if EXPERT
299 Support for Kensington Slimblade Trackball.
305 Support for LC-Power RC1000MCE RF remote control.
307 config HID_LENOVO_TPKBD
308 tristate "Lenovo ThinkPad USB Keyboard with TrackPoint"
313 Support for the Lenovo ThinkPad USB Keyboard with TrackPoint.
315 Say Y here if you have a Lenovo ThinkPad USB Keyboard with TrackPoint
316 and would like to use device-specific features like changing the
317 sensitivity of the trackpoint, using the microphone mute button or
318 controlling the mute and microphone mute LEDs.
321 tristate "Logitech devices" if EXPERT
325 Support for Logitech devices that are not fully compliant with HID standard.
327 config HID_LOGITECH_DJ
328 tristate "Logitech Unifying receivers full support"
329 depends on HID_LOGITECH
331 Say Y if you want support for Logitech Unifying receivers and devices.
332 Unifying receivers are capable of pairing up to 6 Logitech compliant
333 devices to the same receiver. Without this driver it will be handled by
334 generic USB_HID driver and all incoming events will be multiplexed
335 into a single mouse and a single keyboard device.
338 bool "Logitech force feedback support"
339 depends on HID_LOGITECH
340 select INPUT_FF_MEMLESS
342 Say Y here if you have one of these devices:
343 - Logitech WingMan Cordless RumblePad
344 - Logitech WingMan Cordless RumblePad 2
345 - Logitech WingMan Force 3D
346 - Logitech Formula Force EX
347 - Logitech WingMan Formula Force GP
348 - Logitech MOMO Force wheel
350 and if you want to enable force feedback for them.
351 Note: if you say N here, this device will still be supported, but without
354 config LOGIRUMBLEPAD2_FF
355 bool "Logitech force feedback support (variant 2)"
356 depends on HID_LOGITECH
357 select INPUT_FF_MEMLESS
359 Say Y here if you want to enable force feedback support for:
361 - Logitech Rumblepad 2
362 - Logitech Formula Vibration Feedback Wheel
365 bool "Logitech Flight System G940 force feedback support"
366 depends on HID_LOGITECH
367 select INPUT_FF_MEMLESS
369 Say Y here if you want to enable force feedback support for Logitech
370 Flight System G940 devices.
373 bool "Logitech wheels configuration and force feedback support"
374 depends on HID_LOGITECH
375 select INPUT_FF_MEMLESS
378 Say Y here if you want to enable force feedback and range setting
379 support for following Logitech wheels:
380 - Logitech Driving Force
381 - Logitech Driving Force Pro
382 - Logitech Driving Force GT
385 - Logitech MOMO/MOMO 2
386 - Logitech Formula Force EX
388 config HID_MAGICMOUSE
389 tristate "Apple Magic Mouse/Trackpad multi-touch support"
392 Support for the Apple Magic Mouse/Trackpad multi-touch.
394 Say Y here if you want support for the multi-touch features of the
395 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
398 tristate "Microsoft non-fully HID-compliant devices" if EXPERT
402 Support for Microsoft devices that are not fully compliant with HID standard.
405 tristate "Monterey Genius KB29E keyboard" if EXPERT
409 Support for Monterey Genius KB29E.
411 config HID_MULTITOUCH
412 tristate "HID Multitouch panels"
415 Generic support for HID multitouch panels.
417 Say Y here if you have one of the following devices:
418 - 3M PCT touch screens
419 - ActionStar dual touch panels
421 - Cando dual touch panels
424 - Cypress TrueTouch panels
425 - Elo TouchSystems IntelliTouch Plus panels
426 - GeneralTouch 'Sensing Win7-TwoFinger' panels
428 - Hanvon dual touch panels
429 - Ilitek dual touch panels
430 - IrTouch Infrared USB panels
431 - LG Display panels (Dell ST2220Tc)
432 - Lumio CrystalTouch panels
433 - MosArt dual-touch panels
434 - Panasonic multitouch panels
435 - PenMount dual touch panels
436 - Perixx Peripad 701 touchpad
437 - PixArt optical touch screen
438 - Pixcir dual touch panels
440 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
441 - SiS multitouch panels
442 - Stantum multitouch panels
443 - Touch International Panels
445 - Wistron optical touch panels
446 - XAT optical touch panels
447 - Xiroku optical touch panels
448 - Zytronic touch panels
452 To compile this driver as a module, choose M here: the
453 module will be called hid-multitouch.
456 tristate "N-Trig touch screen"
459 Support for N-Trig touch screen.
462 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
465 There are certain devices which have LogicalMaximum wrong in the keyboard
466 usage page of their report descriptor. The most prevailing ones so far
467 are manufactured by Ortek, thus the name of the driver. Currently
468 supported devices by this driver are
472 - Skycable wireless presenter
474 config HID_PANTHERLORD
475 tristate "Pantherlord/GreenAsia game controller"
478 Say Y here if you have a PantherLord/GreenAsia based game controller
481 config PANTHERLORD_FF
482 bool "Pantherlord force feedback support"
483 depends on HID_PANTHERLORD
484 select INPUT_FF_MEMLESS
486 Say Y here if you have a PantherLord/GreenAsia based game controller
487 or adapter and want to enable force feedback support for it.
490 tristate "Petalynx Maxter remote control"
493 Support for Petalynx Maxter remote control.
496 tristate "PicoLCD (graphic version)"
499 This provides support for Minibox PicoLCD devices, currently
500 only the graphical ones are supported.
502 This includes support for the following device features:
504 - Switching between Firmware and Flash mode
505 - EEProm / Flash access (via debugfs)
506 Features selectively enabled:
507 - Framebuffer for monochrome 256x64 display
510 - General purpose outputs
511 Features that are not (yet) supported:
514 config HID_PICOLCD_FB
515 bool "Framebuffer support" if EXPERT
517 depends on HID_PICOLCD
518 depends on HID_PICOLCD=FB || FB=y
519 select FB_DEFERRED_IO
520 select FB_SYS_FILLRECT
521 select FB_SYS_COPYAREA
522 select FB_SYS_IMAGEBLIT
525 Provide access to PicoLCD's 256x64 monochrome display via a
528 config HID_PICOLCD_BACKLIGHT
529 bool "Backlight control" if EXPERT
531 depends on HID_PICOLCD
532 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
534 Provide access to PicoLCD's backlight control via backlight
537 config HID_PICOLCD_LCD
538 bool "Contrast control" if EXPERT
540 depends on HID_PICOLCD
541 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
543 Provide access to PicoLCD's LCD contrast via lcd class.
545 config HID_PICOLCD_LEDS
546 bool "GPO via leds class" if EXPERT
548 depends on HID_PICOLCD
549 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
551 Provide access to PicoLCD's GPO pins via leds class.
553 config HID_PICOLCD_CIR
554 bool "CIR via RC class" if EXPERT
556 depends on HID_PICOLCD
557 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
559 Provide access to PicoLCD's CIR interface via remote control (LIRC).
562 tristate "Primax non-fully HID-compliant devices"
565 Support for Primax devices that are not fully compliant with the
569 tristate "Sony PS3 BD Remote Control"
572 Support for the Sony PS3 Blue-ray Disk Remote Control and Logitech
573 Harmony Adapter for PS3, which connect over Bluetooth.
575 Support for the 6-axis controllers is provided by HID_SONY.
578 tristate "Roccat device support"
581 Support for Roccat devices.
582 Say Y here if you have a Roccat mouse or keyboard and want
583 support for its special functionalities.
586 tristate "Saitek non-fully HID-compliant devices"
589 Support for Saitek devices that are not fully compliant with the
592 Currently only supports the PS1000 controller.
595 tristate "Samsung InfraRed remote control or keyboards"
598 Support for Samsung InfraRed remote control or keyboards.
601 tristate "Sony PS3 controller"
604 Support for Sony PS3 6-axis controllers.
606 Support for the Sony PS3 BD Remote is provided by HID_PS3REMOTE.
609 tristate "Speedlink VAD Cezanne mouse support"
612 Support for Speedlink Vicious and Divine Cezanne mouse.
614 config HID_STEELSERIES
615 tristate "Steelseries SRW-S1 steering wheel support"
618 Support for Steelseries SRW-S1 steering wheel
621 tristate "Sunplus wireless desktop"
624 Support for Sunplus wireless desktop.
627 tristate "GreenAsia (Product ID 0x12) game controller support"
630 Say Y here if you have a GreenAsia (Product ID 0x12) based game
631 controller or adapter.
634 bool "GreenAsia (Product ID 0x12) force feedback support"
635 depends on HID_GREENASIA
636 select INPUT_FF_MEMLESS
638 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
639 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
640 and want to enable force feedback support for it.
642 config HID_HYPERV_MOUSE
643 tristate "Microsoft Hyper-V mouse driver"
646 Select this option to enable the Hyper-V mouse driver.
648 config HID_SMARTJOYPLUS
649 tristate "SmartJoy PLUS PS2/USB adapter support"
652 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
653 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
655 Note that DDR (Dance Dance Revolution) mode is not supported, nor
656 is pressure sensitive buttons on the pro models.
658 config SMARTJOYPLUS_FF
659 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
660 depends on HID_SMARTJOYPLUS
661 select INPUT_FF_MEMLESS
663 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
664 enable force feedback support for it.
667 tristate "TiVo Slide Bluetooth remote control support"
670 Say Y if you have a TiVo Slide Bluetooth remote control.
673 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
676 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
677 CLLRCMCE remote control.
680 tristate "ThingM blink(1) USB RGB LED"
682 depends on LEDS_CLASS
684 Support for the ThingM blink(1) USB RGB LED. This driver registers a
685 Linux LED class instance, plus additional sysfs attributes to control
686 RGB colors, fade time and playing. The device is exposed through hidraw
687 to access other functions.
689 config HID_THRUSTMASTER
690 tristate "ThrustMaster devices support"
693 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
694 a THRUSTMASTER Ferrari GT Rumble Wheel.
696 config THRUSTMASTER_FF
697 bool "ThrustMaster devices force feedback support"
698 depends on HID_THRUSTMASTER
699 select INPUT_FF_MEMLESS
701 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
702 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
703 Rumble Force or Force Feedback Wheel.
706 tristate "Wacom Bluetooth devices support"
708 depends on LEDS_CLASS
711 Support for Wacom Graphire Bluetooth and Intuos4 WL tablets.
714 tristate "Nintendo Wii Remote support"
716 depends on LEDS_CLASS
718 select INPUT_FF_MEMLESS
720 Support for the Nintendo Wii Remote bluetooth device.
722 config HID_WIIMOTE_EXT
723 bool "Nintendo Wii Remote Extension support"
724 depends on HID_WIIMOTE
727 Support for extension controllers of the Nintendo Wii Remote. Say yes
728 here if you want to use the Nintendo Motion+, Nunchuck or Classic
729 extension controllers with your Wii Remote.
732 tristate "Zeroplus based game controller support"
735 Say Y here if you have a Zeroplus based game controller.
738 bool "Zeroplus based game controller force feedback support"
739 depends on HID_ZEROPLUS
740 select INPUT_FF_MEMLESS
742 Say Y here if you have a Zeroplus based game controller and want
743 to have force feedback support for it.
746 tristate "Zydacron remote control support"
749 Support for Zydacron remote control.
751 config HID_SENSOR_HUB
752 tristate "HID Sensors framework support"
753 depends on HID && GENERIC_HARDIRQS
757 Support for HID Sensor framework. This creates a MFD instance
758 for a sensor hub and identifies all the sensors connected to it.
759 Each sensor is registered as a MFD cell, so that sensor specific
760 processing can be done in a separate driver. Each sensor
761 drivers can use the service provided by this driver to register
762 for events and handle data streams. Each sensor driver can format
763 data and present to user mode using input or IIO interface.
769 source "drivers/hid/usbhid/Kconfig"
771 source "drivers/hid/i2c-hid/Kconfig"