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
153 Support for Asus notebook built-in keyboard and touchpad via i2c, and
154 the Asus Republic of Gamers laptop keyboard special keys.
166 Support for Aureal Cy se W-01RN Remote Controller and other Aureal derived remotes.
169 tristate "Belkin Flip KVM and Wireless keyboard"
173 Support for Belkin Flip KVM and Wireless keyboard.
176 tristate "Betop Production Inc. force feedback support"
178 select INPUT_FF_MEMLESS
180 Say Y here if you want to enable force feedback support for devices by
181 BETOP Production Ltd.
182 Currently the following devices are known to be supported:
183 - BETOP 2185 PC & BFM MODE
186 tristate "Cherry Cymotion keyboard"
190 Support for Cherry Cymotion keyboard.
193 tristate "Chicony devices"
197 Support for Chicony Tactical pad and special keys on Chicony keyboards.
200 tristate "Corsair devices"
201 depends on HID && USB && LEDS_CLASS
203 Support for Corsair devices that are not fully compliant with the
211 tristate "Prodikeys PC-MIDI Keyboard support"
212 depends on HID && SND
215 Support for Prodikeys PC-MIDI Keyboard device support.
216 Say Y here to enable support for this device.
217 - Prodikeys PC-MIDI keyboard.
218 The Prodikeys PC-MIDI acts as a USB Audio device, with one MIDI
219 input and one MIDI output. These MIDI jacks appear as
220 a sound "card" in the ALSA sound system.
221 Note: if you say N here, this device will still function as a basic
222 multimedia keyboard, but will lack support for the musical keyboard
223 and some additional multimedia keys.
226 tristate "CMedia CM6533 HID audio jack controls"
229 Support for CMedia CM6533 HID audio jack controls.
232 tristate "Silicon Labs CP2112 HID USB-to-SMBus Bridge support"
233 depends on USB_HID && I2C && GPIOLIB
234 select GPIOLIB_IRQCHIP
236 Support for Silicon Labs CP2112 HID USB to SMBus Master Bridge.
237 This is a HID device driver which registers as an i2c adapter
238 and gpiochip to expose these functions of the CP2112. The
239 customizable USB descriptor fields are exposed as sysfs attributes.
242 tristate "Cypress mouse and barcode readers"
246 Support for cypress mouse and barcode readers.
248 config HID_DRAGONRISE
249 tristate "DragonRise Inc. game controller"
252 Say Y here if you have DragonRise Inc. game controllers.
253 These might be branded as:
255 - Media-tech MT1504 "Rogue"
257 - Defender Game Master
260 bool "DragonRise Inc. force feedback"
261 depends on HID_DRAGONRISE
262 select INPUT_FF_MEMLESS
264 Say Y here if you want to enable force feedback support for DragonRise Inc.
268 tristate "EMS Production Inc. force feedback support"
270 select INPUT_FF_MEMLESS
272 Say Y here if you want to enable force feedback support for devices by
274 Currently the following devices are known to be supported:
275 - Trio Linker Plus II
278 tristate "ELECOM HID devices"
281 Support for ELECOM devices:
282 - BM084 Bluetooth Mouse
283 - DEFT Trackball (Wired and wireless)
286 tristate "ELO USB 4000/4500 touchscreen"
289 Support for the ELO USB 4000/4500 touchscreens. Note that this is for
290 different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
293 tristate "Ezkey BTC 8193 keyboard"
297 Support for Ezkey BTC 8193 keyboard.
300 tristate "Gembird Joypad"
303 Support for Gembird JPD-DualForce 2.
306 tristate "Google Fiber TV Box remote control support"
309 Support for Google Fiber TV Box remote controls
312 tristate "Holtek HID devices"
315 Support for Holtek based devices:
316 - Holtek On Line Grip based game controller
317 - Trust GXT 18 Gaming Keyboard
318 - Sharkoon Drakonia / Perixx MX-2000 gaming mice
319 - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
321 - SHARKOON DarkGlider Gaming mouse
322 - LEETGION Hellion Gaming Mouse
325 bool "Holtek On Line Grip force feedback support"
326 depends on HID_HOLTEK
327 select INPUT_FF_MEMLESS
329 Say Y here if you have a Holtek On Line Grip based game controller
330 and want to have force feedback support for it.
333 tristate "MSI GT68xR LED support"
334 depends on LEDS_CLASS && USB_HID
336 Say Y here if you want to enable support for the three MSI GT68xR LEDs
338 This driver support following modes:
339 - Normal: LEDs are fully on when enabled
340 - Audio: LEDs brightness depends on sound level
341 - Breathing: LEDs brightness varies at human breathing rate
343 Currently the following devices are know to be supported:
347 tristate "Keytouch HID devices"
350 Support for Keytouch HID devices not fully compliant with
351 the specification. Currently supported:
355 tristate "KYE/Genius devices"
358 Support for KYE/Genius devices not fully compliant with HID standard:
360 - EasyPen i405X tablet
361 - MousePen i608X tablet
362 - EasyPen M610X tablet
368 Support for UC-Logic and Huion tablets.
374 Support for Waltop tablets.
377 tristate "Gyration remote control"
380 Support for Gyration remote control.
383 tristate "ION iCade arcade controller"
386 Support for the ION iCade arcade controller to work as a joystick.
388 To compile this driver as a module, choose M here: the
389 module will be called hid-icade.
392 tristate "Twinhan IR remote control"
395 Support for Twinhan IR remote control.
397 config HID_KENSINGTON
398 tristate "Kensington Slimblade Trackball"
402 Support for Kensington Slimblade Trackball.
408 Support for LC-Power RC1000MCE RF remote control.
411 tristate "Simple RGB LED support"
413 depends on LEDS_CLASS
415 Support for simple RGB LED devices. Currently supported are:
416 - Riso Kagaku Webmail Notifier
417 - Dream Cheeky Webmail Notifier and Friends Alert
419 - Delcom Visual Signal Indicator Generation 2
422 To compile this driver as a module, choose M here: the
423 module will be called hid-led.
426 tristate "Lenovo / Thinkpad devices"
431 Support for Lenovo devices that are not fully compliant with HID standard.
433 Say Y if you want support for the non-compliant features of the Lenovo
434 Thinkpad standalone keyboards, e.g:
435 - ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
437 - ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
438 - ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
441 tristate "Logitech devices"
445 Support for Logitech devices that are not fully compliant with HID standard.
447 config HID_LOGITECH_DJ
448 tristate "Logitech Unifying receivers full support"
450 depends on HID_LOGITECH
451 select HID_LOGITECH_HIDPP
453 Say Y if you want support for Logitech Unifying receivers and devices.
454 Unifying receivers are capable of pairing up to 6 Logitech compliant
455 devices to the same receiver. Without this driver it will be handled by
456 generic USB_HID driver and all incoming events will be multiplexed
457 into a single mouse and a single keyboard device.
459 config HID_LOGITECH_HIDPP
460 tristate "Logitech HID++ devices support"
461 depends on HID_LOGITECH
464 Support for Logitech devices relyingon the HID++ Logitech specification
466 Say Y if you want support for Logitech devices relying on the HID++
467 specification. Such devices are the various Logitech Touchpads (T650,
468 T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
472 bool "Logitech force feedback support"
473 depends on HID_LOGITECH
474 select INPUT_FF_MEMLESS
476 Say Y here if you have one of these devices:
477 - Logitech WingMan Cordless RumblePad
478 - Logitech WingMan Cordless RumblePad 2
479 - Logitech WingMan Force 3D
481 and if you want to enable force feedback for them.
482 Note: if you say N here, this device will still be supported, but without
485 config LOGIRUMBLEPAD2_FF
486 bool "Logitech force feedback support (variant 2)"
487 depends on HID_LOGITECH
488 select INPUT_FF_MEMLESS
490 Say Y here if you want to enable force feedback support for:
492 - Logitech Rumblepad 2
493 - Logitech Formula Vibration Feedback Wheel
496 bool "Logitech Flight System G940 force feedback support"
497 depends on HID_LOGITECH
498 select INPUT_FF_MEMLESS
500 Say Y here if you want to enable force feedback support for Logitech
501 Flight System G940 devices.
504 bool "Logitech wheels configuration and force feedback support"
505 depends on HID_LOGITECH
506 select INPUT_FF_MEMLESS
509 Say Y here if you want to enable force feedback and range setting(*)
510 support for following Logitech wheels:
514 - Logitech Driving Force
515 - Logitech Driving Force Pro (*)
516 - Logitech Driving Force GT (*)
517 - Logitech Driving Force EX/RX
518 - Logitech Driving Force Wireless
519 - Logitech Speed Force Wireless
520 - Logitech MOMO Force
521 - Logitech MOMO Racing Force
522 - Logitech Formula Force GP
523 - Logitech Formula Force EX/RX
524 - Logitech Wingman Formula Force GP
526 config HID_MAGICMOUSE
527 tristate "Apple Magic Mouse/Trackpad multi-touch support"
530 Support for the Apple Magic Mouse/Trackpad multi-touch.
532 Say Y here if you want support for the multi-touch features of the
533 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
536 tristate "Mayflash game controller adapter force feedback"
538 select INPUT_FF_MEMLESS
540 Say Y here if you have HJZ Mayflash PS3 game controller adapters
541 and want to enable force feedback support.
544 tristate "Microsoft non-fully HID-compliant devices"
548 Support for Microsoft devices that are not fully compliant with HID standard.
551 tristate "Monterey Genius KB29E keyboard"
555 Support for Monterey Genius KB29E.
557 config HID_MULTITOUCH
558 tristate "HID Multitouch panels"
561 Generic support for HID multitouch panels.
563 Say Y here if you have one of the following devices:
564 - 3M PCT touch screens
565 - ActionStar dual touch panels
567 - Cando dual touch panels
571 - Cypress TrueTouch panels
572 - Elan Microelectronics touch panels
573 - Elo TouchSystems IntelliTouch Plus panels
574 - GeneralTouch 'Sensing Win7-TwoFinger' panels
576 - Hanvon dual touch panels
577 - Ilitek dual touch panels
578 - IrTouch Infrared USB panels
579 - LG Display panels (Dell ST2220Tc)
580 - Lumio CrystalTouch panels
581 - MosArt dual-touch panels
582 - Panasonic multitouch panels
583 - PenMount dual touch panels
584 - Perixx Peripad 701 touchpad
585 - PixArt optical touch screen
586 - Pixcir dual touch panels
588 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
589 - SiS multitouch panels
590 - Stantum multitouch panels
591 - Touch International Panels
593 - Wistron optical touch panels
594 - XAT optical touch panels
595 - Xiroku optical touch panels
596 - Zytronic touch panels
600 To compile this driver as a module, choose M here: the
601 module will be called hid-multitouch.
604 tristate "NTI keyboard adapters"
606 Support for the "extra" Sun keyboard keys on keyboards attached
607 through Network Technologies USB-SUN keyboard adapters.
610 tristate "N-Trig touch screen"
613 Support for N-Trig touch screen.
616 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
619 There are certain devices which have LogicalMaximum wrong in the keyboard
620 usage page of their report descriptor. The most prevailing ones so far
621 are manufactured by Ortek, thus the name of the driver. Currently
622 supported devices by this driver are
626 - Skycable wireless presenter
628 config HID_PANTHERLORD
629 tristate "Pantherlord/GreenAsia game controller"
632 Say Y here if you have a PantherLord/GreenAsia based game controller
635 config PANTHERLORD_FF
636 bool "Pantherlord force feedback support"
637 depends on HID_PANTHERLORD
638 select INPUT_FF_MEMLESS
640 Say Y here if you have a PantherLord/GreenAsia based game controller
641 or adapter and want to enable force feedback support for it.
644 tristate "Penmount touch device"
647 This selects a driver for the PenMount 6000 touch controller.
649 The driver works around a problem in the report descript allowing
650 the userspace to touch events instead of mouse events.
652 Say Y here if you have a Penmount based touch controller.
655 tristate "Petalynx Maxter remote control"
658 Support for Petalynx Maxter remote control.
661 tristate "PicoLCD (graphic version)"
664 This provides support for Minibox PicoLCD devices, currently
665 only the graphical ones are supported.
667 This includes support for the following device features:
669 - Switching between Firmware and Flash mode
670 - EEProm / Flash access (via debugfs)
671 Features selectively enabled:
672 - Framebuffer for monochrome 256x64 display
675 - General purpose outputs
676 Features that are not (yet) supported:
679 config HID_PICOLCD_FB
680 bool "Framebuffer support" if EXPERT
682 depends on HID_PICOLCD
683 depends on HID_PICOLCD=FB || FB=y
684 select FB_DEFERRED_IO
685 select FB_SYS_FILLRECT
686 select FB_SYS_COPYAREA
687 select FB_SYS_IMAGEBLIT
690 Provide access to PicoLCD's 256x64 monochrome display via a
693 config HID_PICOLCD_BACKLIGHT
694 bool "Backlight control" if EXPERT
696 depends on HID_PICOLCD
697 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
699 Provide access to PicoLCD's backlight control via backlight
702 config HID_PICOLCD_LCD
703 bool "Contrast control" if EXPERT
705 depends on HID_PICOLCD
706 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
708 Provide access to PicoLCD's LCD contrast via lcd class.
710 config HID_PICOLCD_LEDS
711 bool "GPO via leds class" if EXPERT
713 depends on HID_PICOLCD
714 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
716 Provide access to PicoLCD's GPO pins via leds class.
718 config HID_PICOLCD_CIR
719 bool "CIR via RC class" if EXPERT
721 depends on HID_PICOLCD
722 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
724 Provide access to PicoLCD's CIR interface via remote control (LIRC).
726 config HID_PLANTRONICS
727 tristate "Plantronics USB HID Driver"
730 Provides HID support for Plantronics USB audio devices.
731 Correctly maps vendor unique volume up/down HID usages to
732 KEY_VOLUMEUP and KEY_VOLUMEDOWN events and prevents core mapping
733 of other vendor unique HID usages to random mouse events.
735 Say M here if you may ever plug in a Plantronics USB audio device.
738 tristate "Primax non-fully HID-compliant devices"
741 Support for Primax devices that are not fully compliant with the
745 tristate "Roccat device support"
748 Support for Roccat devices.
749 Say Y here if you have a Roccat mouse or keyboard and want
750 support for its special functionalities.
753 tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
756 Support for Saitek devices that are not fully compliant with the
760 - PS1000 Dual Analog Pad
761 - Saitek R.A.T.7, R.A.T.9, M.M.O.7 Gaming Mice
762 - Mad Catz R.A.T.5, R.A.T.9 Gaming Mice
765 tristate "Samsung InfraRed remote control or keyboards"
768 Support for Samsung InfraRed remote control or keyboards.
771 tristate "Sony PS2/3/4 accessories"
774 depends on LEDS_CLASS
779 * Sony PS3 6-axis controllers
780 * Sony PS4 DualShock 4 controllers
782 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
783 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
786 bool "Sony PS2/3/4 accessories force feedback support"
788 select INPUT_FF_MEMLESS
790 Say Y here if you have a Sony PS2/3/4 accessory and want to enable
791 force feedback support for it.
794 tristate "Speedlink VAD Cezanne mouse support"
797 Support for Speedlink Vicious and Divine Cezanne mouse.
799 config HID_STEELSERIES
800 tristate "Steelseries SRW-S1 steering wheel support"
803 Support for Steelseries SRW-S1 steering wheel
806 tristate "Sunplus wireless desktop"
809 Support for Sunplus wireless desktop.
812 tristate "Synaptics RMI4 device support"
820 Support for Synaptics RMI4 touchpads.
821 Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
822 and want support for its special functionalities.
825 tristate "GreenAsia (Product ID 0x12) game controller support"
828 Say Y here if you have a GreenAsia (Product ID 0x12) based game
829 controller or adapter.
832 bool "GreenAsia (Product ID 0x12) force feedback support"
833 depends on HID_GREENASIA
834 select INPUT_FF_MEMLESS
836 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
837 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
838 and want to enable force feedback support for it.
840 config HID_HYPERV_MOUSE
841 tristate "Microsoft Hyper-V mouse driver"
844 Select this option to enable the Hyper-V mouse driver.
846 config HID_SMARTJOYPLUS
847 tristate "SmartJoy PLUS PS2/USB adapter support"
850 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
851 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
853 Note that DDR (Dance Dance Revolution) mode is not supported, nor
854 is pressure sensitive buttons on the pro models.
856 config SMARTJOYPLUS_FF
857 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
858 depends on HID_SMARTJOYPLUS
859 select INPUT_FF_MEMLESS
861 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
862 enable force feedback support for it.
865 tristate "TiVo Slide Bluetooth remote control support"
868 Say Y if you have a TiVo Slide Bluetooth remote control.
871 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
874 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
875 CLLRCMCE remote control.
878 tristate "ThingM blink(1) USB RGB LED"
880 depends on LEDS_CLASS
883 Support for the ThingM blink(1) USB RGB LED. This driver has been
884 merged into the generic hid led driver. Config symbol HID_THINGM
885 just selects HID_LED and will be removed soon.
887 config HID_THRUSTMASTER
888 tristate "ThrustMaster devices support"
891 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
892 a THRUSTMASTER Ferrari GT Rumble Wheel.
894 config THRUSTMASTER_FF
895 bool "ThrustMaster devices force feedback support"
896 depends on HID_THRUSTMASTER
897 select INPUT_FF_MEMLESS
899 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
900 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
901 Rumble Force or Force Feedback Wheel.
904 tristate "THQ PS3 uDraw tablet"
907 Say Y here if you want to use the THQ uDraw gaming tablet for
911 tristate "Wacom Intuos/Graphire tablet support (USB)"
918 Say Y here if you want to use the USB or BT version of the Wacom Intuos
921 To compile this driver as a module, choose M here: the
922 module will be called wacom.
925 tristate "Nintendo Wii / Wii U peripherals"
927 depends on LEDS_CLASS
929 select INPUT_FF_MEMLESS
931 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
932 devices are the Wii Remote and its extension devices, but also devices
933 based on the Wii Remote like the Wii U Pro Controller or the
936 Support for all official Nintendo extensions is available, however, 3rd
937 party extensions might not be supported. Please report these devices to:
938 http://github.com/dvdhrm/xwiimote/issues
940 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
941 the Wii U Gamepad) might be supported in the future. But currently
942 support is limited to Bluetooth based devices.
946 To compile this driver as a module, choose M here: the
947 module will be called hid-wiimote.
950 tristate "Xin-Mo non-fully compliant devices"
953 Support for Xin-Mo devices that are not fully compliant with the HID
954 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
955 if you have a Xin-Mo Dual Arcade controller.
958 tristate "Zeroplus based game controller support"
961 Say Y here if you have a Zeroplus based game controller.
964 bool "Zeroplus based game controller force feedback support"
965 depends on HID_ZEROPLUS
966 select INPUT_FF_MEMLESS
968 Say Y here if you have a Zeroplus based game controller and want
969 to have force feedback support for it.
972 tristate "Zydacron remote control support"
975 Support for Zydacron remote control.
977 config HID_SENSOR_HUB
978 tristate "HID Sensors framework support"
979 depends on HID && HAS_IOMEM
983 Support for HID Sensor framework. This creates a MFD instance
984 for a sensor hub and identifies all the sensors connected to it.
985 Each sensor is registered as a MFD cell, so that sensor specific
986 processing can be done in a separate driver. Each sensor
987 drivers can use the service provided by this driver to register
988 for events and handle data streams. Each sensor driver can format
989 data and present to user mode using input or IIO interface.
991 config HID_SENSOR_CUSTOM_SENSOR
992 tristate "HID Sensors hub custom sensor support"
993 depends on HID_SENSOR_HUB
996 HID Sensor hub specification allows definition of some custom and
997 generic sensors. Unlike other HID sensors, they can't be exported
998 via Linux IIO because of custom fields. This is up to the manufacturer
999 to decide how to interpret these special sensor ids and process in
1000 the user space. Currently some manufacturers are using these ids for
1001 sensor calibration and debugging other sensors. Manufacturers
1002 should't use these special custom sensor ids to export any of the
1004 Select this config option for custom/generic sensor support.
1007 tristate "Alps HID device support"
1010 Support for Alps I2C HID touchpads and StickPointer.
1011 Say Y here if you have a Alps touchpads over i2c-hid or usbhid
1012 and want support for its special functionalities.
1018 source "drivers/hid/usbhid/Kconfig"
1020 source "drivers/hid/i2c-hid/Kconfig"
1022 source "drivers/hid/intel-ish-hid/Kconfig"