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 BM084 bluetooth mouse"
281 Support for the ELECOM BM084 (bluetooth mouse).
284 tristate "ELO USB 4000/4500 touchscreen"
287 Support for the ELO USB 4000/4500 touchscreens. Note that this is for
288 different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
291 tristate "Ezkey BTC 8193 keyboard"
295 Support for Ezkey BTC 8193 keyboard.
298 tristate "Gembird Joypad"
301 Support for Gembird JPD-DualForce 2.
304 tristate "Google Fiber TV Box remote control support"
307 Support for Google Fiber TV Box remote controls
310 tristate "Holtek HID devices"
313 Support for Holtek based devices:
314 - Holtek On Line Grip based game controller
315 - Trust GXT 18 Gaming Keyboard
316 - Sharkoon Drakonia / Perixx MX-2000 gaming mice
317 - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
319 - SHARKOON DarkGlider Gaming mouse
320 - LEETGION Hellion Gaming Mouse
323 bool "Holtek On Line Grip force feedback support"
324 depends on HID_HOLTEK
325 select INPUT_FF_MEMLESS
327 Say Y here if you have a Holtek On Line Grip based game controller
328 and want to have force feedback support for it.
331 tristate "MSI GT68xR LED support"
332 depends on LEDS_CLASS && USB_HID
334 Say Y here if you want to enable support for the three MSI GT68xR LEDs
336 This driver support following modes:
337 - Normal: LEDs are fully on when enabled
338 - Audio: LEDs brightness depends on sound level
339 - Breathing: LEDs brightness varies at human breathing rate
341 Currently the following devices are know to be supported:
345 tristate "Keytouch HID devices"
348 Support for Keytouch HID devices not fully compliant with
349 the specification. Currently supported:
353 tristate "KYE/Genius devices"
356 Support for KYE/Genius devices not fully compliant with HID standard:
358 - EasyPen i405X tablet
359 - MousePen i608X tablet
360 - EasyPen M610X tablet
366 Support for UC-Logic and Huion tablets.
372 Support for Waltop tablets.
375 tristate "Gyration remote control"
378 Support for Gyration remote control.
381 tristate "ION iCade arcade controller"
384 Support for the ION iCade arcade controller to work as a joystick.
386 To compile this driver as a module, choose M here: the
387 module will be called hid-icade.
390 tristate "Twinhan IR remote control"
393 Support for Twinhan IR remote control.
395 config HID_KENSINGTON
396 tristate "Kensington Slimblade Trackball"
400 Support for Kensington Slimblade Trackball.
406 Support for LC-Power RC1000MCE RF remote control.
409 tristate "Simple RGB LED support"
411 depends on LEDS_CLASS
413 Support for simple RGB LED devices. Currently supported are:
414 - Riso Kagaku Webmail Notifier
415 - Dream Cheeky Webmail Notifier and Friends Alert
417 - Delcom Visual Signal Indicator Generation 2
420 To compile this driver as a module, choose M here: the
421 module will be called hid-led.
424 tristate "Lenovo / Thinkpad devices"
429 Support for Lenovo devices that are not fully compliant with HID standard.
431 Say Y if you want support for the non-compliant features of the Lenovo
432 Thinkpad standalone keyboards, e.g:
433 - ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
435 - ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
436 - ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
439 tristate "Logitech devices"
443 Support for Logitech devices that are not fully compliant with HID standard.
445 config HID_LOGITECH_DJ
446 tristate "Logitech Unifying receivers full support"
448 depends on HID_LOGITECH
449 select HID_LOGITECH_HIDPP
451 Say Y if you want support for Logitech Unifying receivers and devices.
452 Unifying receivers are capable of pairing up to 6 Logitech compliant
453 devices to the same receiver. Without this driver it will be handled by
454 generic USB_HID driver and all incoming events will be multiplexed
455 into a single mouse and a single keyboard device.
457 config HID_LOGITECH_HIDPP
458 tristate "Logitech HID++ devices support"
459 depends on HID_LOGITECH
462 Support for Logitech devices relyingon the HID++ Logitech specification
464 Say Y if you want support for Logitech devices relying on the HID++
465 specification. Such devices are the various Logitech Touchpads (T650,
466 T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
470 bool "Logitech force feedback support"
471 depends on HID_LOGITECH
472 select INPUT_FF_MEMLESS
474 Say Y here if you have one of these devices:
475 - Logitech WingMan Cordless RumblePad
476 - Logitech WingMan Cordless RumblePad 2
477 - Logitech WingMan Force 3D
479 and if you want to enable force feedback for them.
480 Note: if you say N here, this device will still be supported, but without
483 config LOGIRUMBLEPAD2_FF
484 bool "Logitech force feedback support (variant 2)"
485 depends on HID_LOGITECH
486 select INPUT_FF_MEMLESS
488 Say Y here if you want to enable force feedback support for:
490 - Logitech Rumblepad 2
491 - Logitech Formula Vibration Feedback Wheel
494 bool "Logitech Flight System G940 force feedback support"
495 depends on HID_LOGITECH
496 select INPUT_FF_MEMLESS
498 Say Y here if you want to enable force feedback support for Logitech
499 Flight System G940 devices.
502 bool "Logitech wheels configuration and force feedback support"
503 depends on HID_LOGITECH
504 select INPUT_FF_MEMLESS
507 Say Y here if you want to enable force feedback and range setting(*)
508 support for following Logitech wheels:
512 - Logitech Driving Force
513 - Logitech Driving Force Pro (*)
514 - Logitech Driving Force GT (*)
515 - Logitech Driving Force EX/RX
516 - Logitech Driving Force Wireless
517 - Logitech Speed Force Wireless
518 - Logitech MOMO Force
519 - Logitech MOMO Racing Force
520 - Logitech Formula Force GP
521 - Logitech Formula Force EX/RX
522 - Logitech Wingman Formula Force GP
524 config HID_MAGICMOUSE
525 tristate "Apple Magic Mouse/Trackpad multi-touch support"
528 Support for the Apple Magic Mouse/Trackpad multi-touch.
530 Say Y here if you want support for the multi-touch features of the
531 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
534 tristate "Mayflash game controller adapter force feedback"
536 select INPUT_FF_MEMLESS
538 Say Y here if you have HJZ Mayflash PS3 game controller adapters
539 and want to enable force feedback support.
542 tristate "Microsoft non-fully HID-compliant devices"
546 Support for Microsoft devices that are not fully compliant with HID standard.
549 tristate "Monterey Genius KB29E keyboard"
553 Support for Monterey Genius KB29E.
555 config HID_MULTITOUCH
556 tristate "HID Multitouch panels"
559 Generic support for HID multitouch panels.
561 Say Y here if you have one of the following devices:
562 - 3M PCT touch screens
563 - ActionStar dual touch panels
565 - Cando dual touch panels
569 - Cypress TrueTouch panels
570 - Elan Microelectronics touch panels
571 - Elo TouchSystems IntelliTouch Plus panels
572 - GeneralTouch 'Sensing Win7-TwoFinger' panels
574 - Hanvon dual touch panels
575 - Ilitek dual touch panels
576 - IrTouch Infrared USB panels
577 - LG Display panels (Dell ST2220Tc)
578 - Lumio CrystalTouch panels
579 - MosArt dual-touch panels
580 - Panasonic multitouch panels
581 - PenMount dual touch panels
582 - Perixx Peripad 701 touchpad
583 - PixArt optical touch screen
584 - Pixcir dual touch panels
586 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
587 - SiS multitouch panels
588 - Stantum multitouch panels
589 - Touch International Panels
591 - Wistron optical touch panels
592 - XAT optical touch panels
593 - Xiroku optical touch panels
594 - Zytronic touch panels
598 To compile this driver as a module, choose M here: the
599 module will be called hid-multitouch.
602 tristate "NTI keyboard adapters"
604 Support for the "extra" Sun keyboard keys on keyboards attached
605 through Network Technologies USB-SUN keyboard adapters.
608 tristate "N-Trig touch screen"
611 Support for N-Trig touch screen.
614 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
617 There are certain devices which have LogicalMaximum wrong in the keyboard
618 usage page of their report descriptor. The most prevailing ones so far
619 are manufactured by Ortek, thus the name of the driver. Currently
620 supported devices by this driver are
624 - Skycable wireless presenter
626 config HID_PANTHERLORD
627 tristate "Pantherlord/GreenAsia game controller"
630 Say Y here if you have a PantherLord/GreenAsia based game controller
633 config PANTHERLORD_FF
634 bool "Pantherlord force feedback support"
635 depends on HID_PANTHERLORD
636 select INPUT_FF_MEMLESS
638 Say Y here if you have a PantherLord/GreenAsia based game controller
639 or adapter and want to enable force feedback support for it.
642 tristate "Penmount touch device"
645 This selects a driver for the PenMount 6000 touch controller.
647 The driver works around a problem in the report descript allowing
648 the userspace to touch events instead of mouse events.
650 Say Y here if you have a Penmount based touch controller.
653 tristate "Petalynx Maxter remote control"
656 Support for Petalynx Maxter remote control.
659 tristate "PicoLCD (graphic version)"
662 This provides support for Minibox PicoLCD devices, currently
663 only the graphical ones are supported.
665 This includes support for the following device features:
667 - Switching between Firmware and Flash mode
668 - EEProm / Flash access (via debugfs)
669 Features selectively enabled:
670 - Framebuffer for monochrome 256x64 display
673 - General purpose outputs
674 Features that are not (yet) supported:
677 config HID_PICOLCD_FB
678 bool "Framebuffer support" if EXPERT
680 depends on HID_PICOLCD
681 depends on HID_PICOLCD=FB || FB=y
682 select FB_DEFERRED_IO
683 select FB_SYS_FILLRECT
684 select FB_SYS_COPYAREA
685 select FB_SYS_IMAGEBLIT
688 Provide access to PicoLCD's 256x64 monochrome display via a
691 config HID_PICOLCD_BACKLIGHT
692 bool "Backlight control" if EXPERT
694 depends on HID_PICOLCD
695 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
697 Provide access to PicoLCD's backlight control via backlight
700 config HID_PICOLCD_LCD
701 bool "Contrast control" if EXPERT
703 depends on HID_PICOLCD
704 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
706 Provide access to PicoLCD's LCD contrast via lcd class.
708 config HID_PICOLCD_LEDS
709 bool "GPO via leds class" if EXPERT
711 depends on HID_PICOLCD
712 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
714 Provide access to PicoLCD's GPO pins via leds class.
716 config HID_PICOLCD_CIR
717 bool "CIR via RC class" if EXPERT
719 depends on HID_PICOLCD
720 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
722 Provide access to PicoLCD's CIR interface via remote control (LIRC).
724 config HID_PLANTRONICS
725 tristate "Plantronics USB HID Driver"
728 Provides HID support for Plantronics USB audio devices.
729 Correctly maps vendor unique volume up/down HID usages to
730 KEY_VOLUMEUP and KEY_VOLUMEDOWN events and prevents core mapping
731 of other vendor unique HID usages to random mouse events.
733 Say M here if you may ever plug in a Plantronics USB audio device.
736 tristate "Primax non-fully HID-compliant devices"
739 Support for Primax devices that are not fully compliant with the
743 tristate "Roccat device support"
746 Support for Roccat devices.
747 Say Y here if you have a Roccat mouse or keyboard and want
748 support for its special functionalities.
751 tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
754 Support for Saitek devices that are not fully compliant with the
758 - PS1000 Dual Analog Pad
759 - Saitek R.A.T.7, R.A.T.9, M.M.O.7 Gaming Mice
760 - Mad Catz R.A.T.5, R.A.T.9 Gaming Mice
763 tristate "Samsung InfraRed remote control or keyboards"
766 Support for Samsung InfraRed remote control or keyboards.
769 tristate "Sony PS2/3/4 accessories"
772 depends on LEDS_CLASS
777 * Sony PS3 6-axis controllers
778 * Sony PS4 DualShock 4 controllers
780 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
781 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
784 bool "Sony PS2/3/4 accessories force feedback support"
786 select INPUT_FF_MEMLESS
788 Say Y here if you have a Sony PS2/3/4 accessory and want to enable
789 force feedback support for it.
792 tristate "Speedlink VAD Cezanne mouse support"
795 Support for Speedlink Vicious and Divine Cezanne mouse.
797 config HID_STEELSERIES
798 tristate "Steelseries SRW-S1 steering wheel support"
801 Support for Steelseries SRW-S1 steering wheel
804 tristate "Sunplus wireless desktop"
807 Support for Sunplus wireless desktop.
810 tristate "Synaptics RMI4 device support"
818 Support for Synaptics RMI4 touchpads.
819 Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
820 and want support for its special functionalities.
823 tristate "GreenAsia (Product ID 0x12) game controller support"
826 Say Y here if you have a GreenAsia (Product ID 0x12) based game
827 controller or adapter.
830 bool "GreenAsia (Product ID 0x12) force feedback support"
831 depends on HID_GREENASIA
832 select INPUT_FF_MEMLESS
834 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
835 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
836 and want to enable force feedback support for it.
838 config HID_HYPERV_MOUSE
839 tristate "Microsoft Hyper-V mouse driver"
842 Select this option to enable the Hyper-V mouse driver.
844 config HID_SMARTJOYPLUS
845 tristate "SmartJoy PLUS PS2/USB adapter support"
848 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
849 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
851 Note that DDR (Dance Dance Revolution) mode is not supported, nor
852 is pressure sensitive buttons on the pro models.
854 config SMARTJOYPLUS_FF
855 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
856 depends on HID_SMARTJOYPLUS
857 select INPUT_FF_MEMLESS
859 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
860 enable force feedback support for it.
863 tristate "TiVo Slide Bluetooth remote control support"
866 Say Y if you have a TiVo Slide Bluetooth remote control.
869 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
872 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
873 CLLRCMCE remote control.
876 tristate "ThingM blink(1) USB RGB LED"
878 depends on LEDS_CLASS
881 Support for the ThingM blink(1) USB RGB LED. This driver has been
882 merged into the generic hid led driver. Config symbol HID_THINGM
883 just selects HID_LED and will be removed soon.
885 config HID_THRUSTMASTER
886 tristate "ThrustMaster devices support"
889 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
890 a THRUSTMASTER Ferrari GT Rumble Wheel.
892 config THRUSTMASTER_FF
893 bool "ThrustMaster devices force feedback support"
894 depends on HID_THRUSTMASTER
895 select INPUT_FF_MEMLESS
897 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
898 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
899 Rumble Force or Force Feedback Wheel.
902 tristate "THQ PS3 uDraw tablet"
905 Say Y here if you want to use the THQ uDraw gaming tablet for
909 tristate "Wacom Intuos/Graphire tablet support (USB)"
916 Say Y here if you want to use the USB or BT version of the Wacom Intuos
919 To compile this driver as a module, choose M here: the
920 module will be called wacom.
923 tristate "Nintendo Wii / Wii U peripherals"
925 depends on LEDS_CLASS
927 select INPUT_FF_MEMLESS
929 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
930 devices are the Wii Remote and its extension devices, but also devices
931 based on the Wii Remote like the Wii U Pro Controller or the
934 Support for all official Nintendo extensions is available, however, 3rd
935 party extensions might not be supported. Please report these devices to:
936 http://github.com/dvdhrm/xwiimote/issues
938 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
939 the Wii U Gamepad) might be supported in the future. But currently
940 support is limited to Bluetooth based devices.
944 To compile this driver as a module, choose M here: the
945 module will be called hid-wiimote.
948 tristate "Xin-Mo non-fully compliant devices"
951 Support for Xin-Mo devices that are not fully compliant with the HID
952 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
953 if you have a Xin-Mo Dual Arcade controller.
956 tristate "Zeroplus based game controller support"
959 Say Y here if you have a Zeroplus based game controller.
962 bool "Zeroplus based game controller force feedback support"
963 depends on HID_ZEROPLUS
964 select INPUT_FF_MEMLESS
966 Say Y here if you have a Zeroplus based game controller and want
967 to have force feedback support for it.
970 tristate "Zydacron remote control support"
973 Support for Zydacron remote control.
975 config HID_SENSOR_HUB
976 tristate "HID Sensors framework support"
977 depends on HID && HAS_IOMEM
981 Support for HID Sensor framework. This creates a MFD instance
982 for a sensor hub and identifies all the sensors connected to it.
983 Each sensor is registered as a MFD cell, so that sensor specific
984 processing can be done in a separate driver. Each sensor
985 drivers can use the service provided by this driver to register
986 for events and handle data streams. Each sensor driver can format
987 data and present to user mode using input or IIO interface.
989 config HID_SENSOR_CUSTOM_SENSOR
990 tristate "HID Sensors hub custom sensor support"
991 depends on HID_SENSOR_HUB
994 HID Sensor hub specification allows definition of some custom and
995 generic sensors. Unlike other HID sensors, they can't be exported
996 via Linux IIO because of custom fields. This is up to the manufacturer
997 to decide how to interpret these special sensor ids and process in
998 the user space. Currently some manufacturers are using these ids for
999 sensor calibration and debugging other sensors. Manufacturers
1000 should't use these special custom sensor ids to export any of the
1002 Select this config option for custom/generic sensor support.
1005 tristate "Alps HID device support"
1008 Support for Alps I2C HID touchpads and StickPointer.
1009 Say Y here if you have a Alps touchpads over i2c-hid or usbhid
1010 and want support for its special functionalities.
1016 source "drivers/hid/usbhid/Kconfig"
1018 source "drivers/hid/i2c-hid/Kconfig"
1020 source "drivers/hid/intel-ish-hid/Kconfig"