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 "ACRUX game controller support"
105 Say Y here if you want to enable support for ACRUX game controllers.
108 bool "ACRUX force feedback support"
110 select INPUT_FF_MEMLESS
112 Say Y here if you want to enable force feedback support for ACRUX
116 tristate "Apple {i,Power,Mac}Books"
120 Support for some Apple devices which less or more break
123 Say Y here if you want support for keyboards of Apple iBooks, PowerBooks,
124 MacBooks, MacBook Pros and Apple Aluminum.
127 tristate "Apple infrared receiver"
130 Support for Apple infrared remote control. All the Apple computers from
131 2005 onwards include such a port, except the unibody Macbook (2009),
132 and Mac Pros. This receiver is also used in the Apple TV set-top box
133 prior to the 2010 model.
135 Say Y here if you want support for Apple infrared remote control.
139 depends on LEDS_CLASS
141 Support for Asus notebook built-in keyboard and touchpad via i2c, and
142 the Asus Republic of Gamers laptop keyboard special keys.
154 Support for Aureal Cy se W-01RN Remote Controller and other Aureal derived remotes.
157 tristate "Belkin Flip KVM and Wireless keyboard"
161 Support for Belkin Flip KVM and Wireless keyboard.
164 tristate "Betop Production Inc. force feedback support"
166 select INPUT_FF_MEMLESS
168 Say Y here if you want to enable force feedback support for devices by
169 BETOP Production Ltd.
170 Currently the following devices are known to be supported:
171 - BETOP 2185 PC & BFM MODE
174 tristate "Cherry Cymotion keyboard"
178 Support for Cherry Cymotion keyboard.
181 tristate "Chicony devices"
185 Support for Chicony Tactical pad and special keys on Chicony keyboards.
188 tristate "Corsair devices"
189 depends on HID && USB && LEDS_CLASS
191 Support for Corsair devices that are not fully compliant with the
199 tristate "Prodikeys PC-MIDI Keyboard support"
200 depends on HID && SND
203 Support for Prodikeys PC-MIDI Keyboard device support.
204 Say Y here to enable support for this device.
205 - Prodikeys PC-MIDI keyboard.
206 The Prodikeys PC-MIDI acts as a USB Audio device, with one MIDI
207 input and one MIDI output. These MIDI jacks appear as
208 a sound "card" in the ALSA sound system.
209 Note: if you say N here, this device will still function as a basic
210 multimedia keyboard, but will lack support for the musical keyboard
211 and some additional multimedia keys.
214 tristate "CMedia CM6533 HID audio jack controls"
217 Support for CMedia CM6533 HID audio jack controls.
220 tristate "Silicon Labs CP2112 HID USB-to-SMBus Bridge support"
221 depends on USB_HID && I2C && GPIOLIB && GPIOLIB_IRQCHIP
223 Support for Silicon Labs CP2112 HID USB to SMBus Master Bridge.
224 This is a HID device driver which registers as an i2c adapter
225 and gpiochip to expose these functions of the CP2112. The
226 customizable USB descriptor fields are exposed as sysfs attributes.
229 tristate "Cypress mouse and barcode readers"
233 Support for cypress mouse and barcode readers.
235 config HID_DRAGONRISE
236 tristate "DragonRise Inc. game controller"
239 Say Y here if you have DragonRise Inc. game controllers.
240 These might be branded as:
242 - Media-tech MT1504 "Rogue"
244 - Defender Game Master
247 bool "DragonRise Inc. force feedback"
248 depends on HID_DRAGONRISE
249 select INPUT_FF_MEMLESS
251 Say Y here if you want to enable force feedback support for DragonRise Inc.
255 tristate "EMS Production Inc. force feedback support"
257 select INPUT_FF_MEMLESS
259 Say Y here if you want to enable force feedback support for devices by
261 Currently the following devices are known to be supported:
262 - Trio Linker Plus II
265 tristate "ELECOM BM084 bluetooth mouse"
268 Support for the ELECOM BM084 (bluetooth mouse).
271 tristate "ELO USB 4000/4500 touchscreen"
274 Support for the ELO USB 4000/4500 touchscreens. Note that this is for
275 different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
278 tristate "Ezkey BTC 8193 keyboard"
282 Support for Ezkey BTC 8193 keyboard.
285 tristate "Gembird Joypad"
288 Support for Gembird JPD-DualForce 2.
291 tristate "Google Fiber TV Box remote control support"
294 Support for Google Fiber TV Box remote controls
297 tristate "Holtek HID devices"
300 Support for Holtek based devices:
301 - Holtek On Line Grip based game controller
302 - Trust GXT 18 Gaming Keyboard
303 - Sharkoon Drakonia / Perixx MX-2000 gaming mice
304 - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
306 - SHARKOON DarkGlider Gaming mouse
307 - LEETGION Hellion Gaming Mouse
310 bool "Holtek On Line Grip force feedback support"
311 depends on HID_HOLTEK
312 select INPUT_FF_MEMLESS
314 Say Y here if you have a Holtek On Line Grip based game controller
315 and want to have force feedback support for it.
318 tristate "MSI GT68xR LED support"
319 depends on LEDS_CLASS && USB_HID
321 Say Y here if you want to enable support for the three MSI GT68xR LEDs
323 This driver support following modes:
324 - Normal: LEDs are fully on when enabled
325 - Audio: LEDs brightness depends on sound level
326 - Breathing: LEDs brightness varies at human breathing rate
328 Currently the following devices are know to be supported:
332 tristate "Keytouch HID devices"
335 Support for Keytouch HID devices not fully compliant with
336 the specification. Currently supported:
340 tristate "KYE/Genius devices"
343 Support for KYE/Genius devices not fully compliant with HID standard:
345 - EasyPen i405X tablet
346 - MousePen i608X tablet
347 - EasyPen M610X tablet
353 Support for UC-Logic and Huion tablets.
359 Support for Waltop tablets.
362 tristate "Gyration remote control"
365 Support for Gyration remote control.
368 tristate "ION iCade arcade controller"
371 Support for the ION iCade arcade controller to work as a joystick.
373 To compile this driver as a module, choose M here: the
374 module will be called hid-icade.
377 tristate "Twinhan IR remote control"
380 Support for Twinhan IR remote control.
382 config HID_KENSINGTON
383 tristate "Kensington Slimblade Trackball"
387 Support for Kensington Slimblade Trackball.
393 Support for LC-Power RC1000MCE RF remote control.
396 tristate "Simple RGB LED support"
398 depends on LEDS_CLASS
400 Support for simple RGB LED devices. Currently supported are:
401 - Riso Kagaku Webmail Notifier
402 - Dream Cheeky Webmail Notifier and Friends Alert
404 - Delcom Visual Signal Indicator Generation 2
407 To compile this driver as a module, choose M here: the
408 module will be called hid-led.
411 tristate "Lenovo / Thinkpad devices"
416 Support for Lenovo devices that are not fully compliant with HID standard.
418 Say Y if you want support for the non-compliant features of the Lenovo
419 Thinkpad standalone keyboards, e.g:
420 - ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
422 - ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
423 - ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
426 tristate "Logitech devices"
430 Support for Logitech devices that are not fully compliant with HID standard.
432 config HID_LOGITECH_DJ
433 tristate "Logitech Unifying receivers full support"
435 depends on HID_LOGITECH
436 select HID_LOGITECH_HIDPP
438 Say Y if you want support for Logitech Unifying receivers and devices.
439 Unifying receivers are capable of pairing up to 6 Logitech compliant
440 devices to the same receiver. Without this driver it will be handled by
441 generic USB_HID driver and all incoming events will be multiplexed
442 into a single mouse and a single keyboard device.
444 config HID_LOGITECH_HIDPP
445 tristate "Logitech HID++ devices support"
446 depends on HID_LOGITECH
448 Support for Logitech devices relyingon the HID++ Logitech specification
450 Say Y if you want support for Logitech devices relying on the HID++
451 specification. Such devices are the various Logitech Touchpads (T650,
452 T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
456 bool "Logitech force feedback support"
457 depends on HID_LOGITECH
458 select INPUT_FF_MEMLESS
460 Say Y here if you have one of these devices:
461 - Logitech WingMan Cordless RumblePad
462 - Logitech WingMan Cordless RumblePad 2
463 - Logitech WingMan Force 3D
465 and if you want to enable force feedback for them.
466 Note: if you say N here, this device will still be supported, but without
469 config LOGIRUMBLEPAD2_FF
470 bool "Logitech force feedback support (variant 2)"
471 depends on HID_LOGITECH
472 select INPUT_FF_MEMLESS
474 Say Y here if you want to enable force feedback support for:
476 - Logitech Rumblepad 2
477 - Logitech Formula Vibration Feedback Wheel
480 bool "Logitech Flight System G940 force feedback support"
481 depends on HID_LOGITECH
482 select INPUT_FF_MEMLESS
484 Say Y here if you want to enable force feedback support for Logitech
485 Flight System G940 devices.
488 bool "Logitech wheels configuration and force feedback support"
489 depends on HID_LOGITECH
490 select INPUT_FF_MEMLESS
493 Say Y here if you want to enable force feedback and range setting(*)
494 support for following Logitech wheels:
498 - Logitech Driving Force
499 - Logitech Driving Force Pro (*)
500 - Logitech Driving Force GT (*)
501 - Logitech Driving Force EX/RX
502 - Logitech Driving Force Wireless
503 - Logitech Speed Force Wireless
504 - Logitech MOMO Force
505 - Logitech MOMO Racing Force
506 - Logitech Formula Force GP
507 - Logitech Formula Force EX/RX
508 - Logitech Wingman Formula Force GP
510 config HID_MAGICMOUSE
511 tristate "Apple Magic Mouse/Trackpad multi-touch support"
514 Support for the Apple Magic Mouse/Trackpad multi-touch.
516 Say Y here if you want support for the multi-touch features of the
517 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
520 tristate "Mayflash game controller adapter force feedback"
522 select INPUT_FF_MEMLESS
524 Say Y here if you have HJZ Mayflash PS3 game controller adapters
525 and want to enable force feedback support.
528 tristate "Microsoft non-fully HID-compliant devices"
532 Support for Microsoft devices that are not fully compliant with HID standard.
535 tristate "Monterey Genius KB29E keyboard"
539 Support for Monterey Genius KB29E.
541 config HID_MULTITOUCH
542 tristate "HID Multitouch panels"
545 Generic support for HID multitouch panels.
547 Say Y here if you have one of the following devices:
548 - 3M PCT touch screens
549 - ActionStar dual touch panels
551 - Cando dual touch panels
555 - Cypress TrueTouch panels
556 - Elan Microelectronics touch panels
557 - Elo TouchSystems IntelliTouch Plus panels
558 - GeneralTouch 'Sensing Win7-TwoFinger' panels
560 - Hanvon dual touch panels
561 - Ilitek dual touch panels
562 - IrTouch Infrared USB panels
563 - LG Display panels (Dell ST2220Tc)
564 - Lumio CrystalTouch panels
565 - MosArt dual-touch panels
566 - Panasonic multitouch panels
567 - PenMount dual touch panels
568 - Perixx Peripad 701 touchpad
569 - PixArt optical touch screen
570 - Pixcir dual touch panels
572 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
573 - SiS multitouch panels
574 - Stantum multitouch panels
575 - Touch International Panels
577 - Wistron optical touch panels
578 - XAT optical touch panels
579 - Xiroku optical touch panels
580 - Zytronic touch panels
584 To compile this driver as a module, choose M here: the
585 module will be called hid-multitouch.
588 tristate "N-Trig touch screen"
591 Support for N-Trig touch screen.
594 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
597 There are certain devices which have LogicalMaximum wrong in the keyboard
598 usage page of their report descriptor. The most prevailing ones so far
599 are manufactured by Ortek, thus the name of the driver. Currently
600 supported devices by this driver are
604 - Skycable wireless presenter
606 config HID_PANTHERLORD
607 tristate "Pantherlord/GreenAsia game controller"
610 Say Y here if you have a PantherLord/GreenAsia based game controller
613 config PANTHERLORD_FF
614 bool "Pantherlord force feedback support"
615 depends on HID_PANTHERLORD
616 select INPUT_FF_MEMLESS
618 Say Y here if you have a PantherLord/GreenAsia based game controller
619 or adapter and want to enable force feedback support for it.
622 tristate "Penmount touch device"
625 This selects a driver for the PenMount 6000 touch controller.
627 The driver works around a problem in the report descript allowing
628 the userspace to touch events instead of mouse events.
630 Say Y here if you have a Penmount based touch controller.
633 tristate "Petalynx Maxter remote control"
636 Support for Petalynx Maxter remote control.
639 tristate "PicoLCD (graphic version)"
642 This provides support for Minibox PicoLCD devices, currently
643 only the graphical ones are supported.
645 This includes support for the following device features:
647 - Switching between Firmware and Flash mode
648 - EEProm / Flash access (via debugfs)
649 Features selectively enabled:
650 - Framebuffer for monochrome 256x64 display
653 - General purpose outputs
654 Features that are not (yet) supported:
657 config HID_PICOLCD_FB
658 bool "Framebuffer support" if EXPERT
660 depends on HID_PICOLCD
661 depends on HID_PICOLCD=FB || FB=y
662 select FB_DEFERRED_IO
663 select FB_SYS_FILLRECT
664 select FB_SYS_COPYAREA
665 select FB_SYS_IMAGEBLIT
668 Provide access to PicoLCD's 256x64 monochrome display via a
671 config HID_PICOLCD_BACKLIGHT
672 bool "Backlight control" if EXPERT
674 depends on HID_PICOLCD
675 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
677 Provide access to PicoLCD's backlight control via backlight
680 config HID_PICOLCD_LCD
681 bool "Contrast control" if EXPERT
683 depends on HID_PICOLCD
684 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
686 Provide access to PicoLCD's LCD contrast via lcd class.
688 config HID_PICOLCD_LEDS
689 bool "GPO via leds class" if EXPERT
691 depends on HID_PICOLCD
692 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
694 Provide access to PicoLCD's GPO pins via leds class.
696 config HID_PICOLCD_CIR
697 bool "CIR via RC class" if EXPERT
699 depends on HID_PICOLCD
700 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
702 Provide access to PicoLCD's CIR interface via remote control (LIRC).
704 config HID_PLANTRONICS
705 tristate "Plantronics USB HID Driver"
708 Provides HID support for Plantronics USB audio devices.
709 Correctly maps vendor unique volume up/down HID usages to
710 KEY_VOLUMEUP and KEY_VOLUMEDOWN events and prevents core mapping
711 of other vendor unique HID usages to random mouse events.
713 Say M here if you may ever plug in a Plantronics USB audio device.
716 tristate "Primax non-fully HID-compliant devices"
719 Support for Primax devices that are not fully compliant with the
723 tristate "Roccat device support"
726 Support for Roccat devices.
727 Say Y here if you have a Roccat mouse or keyboard and want
728 support for its special functionalities.
731 tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
734 Support for Saitek devices that are not fully compliant with the
738 - PS1000 Dual Analog Pad
739 - Saitek R.A.T.7, R.A.T.9, M.M.O.7 Gaming Mice
740 - Mad Catz R.A.T.5, R.A.T.9 Gaming Mice
743 tristate "Samsung InfraRed remote control or keyboards"
746 Support for Samsung InfraRed remote control or keyboards.
749 tristate "Sony PS2/3/4 accessories"
752 depends on LEDS_CLASS
757 * Sony PS3 6-axis controllers
758 * Sony PS4 DualShock 4 controllers
760 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
761 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
764 bool "Sony PS2/3/4 accessories force feedback support"
766 select INPUT_FF_MEMLESS
768 Say Y here if you have a Sony PS2/3/4 accessory and want to enable
769 force feedback support for it.
772 tristate "Speedlink VAD Cezanne mouse support"
775 Support for Speedlink Vicious and Divine Cezanne mouse.
777 config HID_STEELSERIES
778 tristate "Steelseries SRW-S1 steering wheel support"
781 Support for Steelseries SRW-S1 steering wheel
784 tristate "Sunplus wireless desktop"
787 Support for Sunplus wireless desktop.
790 tristate "Synaptics RMI4 device support"
798 Support for Synaptics RMI4 touchpads.
799 Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
800 and want support for its special functionalities.
803 tristate "GreenAsia (Product ID 0x12) game controller support"
806 Say Y here if you have a GreenAsia (Product ID 0x12) based game
807 controller or adapter.
810 bool "GreenAsia (Product ID 0x12) force feedback support"
811 depends on HID_GREENASIA
812 select INPUT_FF_MEMLESS
814 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
815 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
816 and want to enable force feedback support for it.
818 config HID_HYPERV_MOUSE
819 tristate "Microsoft Hyper-V mouse driver"
822 Select this option to enable the Hyper-V mouse driver.
824 config HID_SMARTJOYPLUS
825 tristate "SmartJoy PLUS PS2/USB adapter support"
828 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
829 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
831 Note that DDR (Dance Dance Revolution) mode is not supported, nor
832 is pressure sensitive buttons on the pro models.
834 config SMARTJOYPLUS_FF
835 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
836 depends on HID_SMARTJOYPLUS
837 select INPUT_FF_MEMLESS
839 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
840 enable force feedback support for it.
843 tristate "TiVo Slide Bluetooth remote control support"
846 Say Y if you have a TiVo Slide Bluetooth remote control.
849 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
852 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
853 CLLRCMCE remote control.
856 tristate "ThingM blink(1) USB RGB LED"
858 depends on LEDS_CLASS
861 Support for the ThingM blink(1) USB RGB LED. This driver has been
862 merged into the generic hid led driver. Config symbol HID_THINGM
863 just selects HID_LED and will be removed soon.
865 config HID_THRUSTMASTER
866 tristate "ThrustMaster devices support"
869 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
870 a THRUSTMASTER Ferrari GT Rumble Wheel.
872 config THRUSTMASTER_FF
873 bool "ThrustMaster devices force feedback support"
874 depends on HID_THRUSTMASTER
875 select INPUT_FF_MEMLESS
877 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
878 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
879 Rumble Force or Force Feedback Wheel.
882 tristate "THQ PS3 uDraw tablet"
885 Say Y here if you want to use the THQ uDraw gaming tablet for
889 tristate "Wacom Intuos/Graphire tablet support (USB)"
896 Say Y here if you want to use the USB or BT version of the Wacom Intuos
899 To compile this driver as a module, choose M here: the
900 module will be called wacom.
903 tristate "Nintendo Wii / Wii U peripherals"
905 depends on LEDS_CLASS
907 select INPUT_FF_MEMLESS
909 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
910 devices are the Wii Remote and its extension devices, but also devices
911 based on the Wii Remote like the Wii U Pro Controller or the
914 Support for all official Nintendo extensions is available, however, 3rd
915 party extensions might not be supported. Please report these devices to:
916 http://github.com/dvdhrm/xwiimote/issues
918 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
919 the Wii U Gamepad) might be supported in the future. But currently
920 support is limited to Bluetooth based devices.
924 To compile this driver as a module, choose M here: the
925 module will be called hid-wiimote.
928 tristate "Xin-Mo non-fully compliant devices"
931 Support for Xin-Mo devices that are not fully compliant with the HID
932 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
933 if you have a Xin-Mo Dual Arcade controller.
936 tristate "Zeroplus based game controller support"
939 Say Y here if you have a Zeroplus based game controller.
942 bool "Zeroplus based game controller force feedback support"
943 depends on HID_ZEROPLUS
944 select INPUT_FF_MEMLESS
946 Say Y here if you have a Zeroplus based game controller and want
947 to have force feedback support for it.
950 tristate "Zydacron remote control support"
953 Support for Zydacron remote control.
955 config HID_SENSOR_HUB
956 tristate "HID Sensors framework support"
957 depends on HID && HAS_IOMEM
961 Support for HID Sensor framework. This creates a MFD instance
962 for a sensor hub and identifies all the sensors connected to it.
963 Each sensor is registered as a MFD cell, so that sensor specific
964 processing can be done in a separate driver. Each sensor
965 drivers can use the service provided by this driver to register
966 for events and handle data streams. Each sensor driver can format
967 data and present to user mode using input or IIO interface.
969 config HID_SENSOR_CUSTOM_SENSOR
970 tristate "HID Sensors hub custom sensor support"
971 depends on HID_SENSOR_HUB
974 HID Sensor hub specification allows definition of some custom and
975 generic sensors. Unlike other HID sensors, they can't be exported
976 via Linux IIO because of custom fields. This is up to the manufacturer
977 to decide how to interpret these special sensor ids and process in
978 the user space. Currently some manufacturers are using these ids for
979 sensor calibration and debugging other sensors. Manufacturers
980 should't use these special custom sensor ids to export any of the
982 Select this config option for custom/generic sensor support.
985 tristate "Alps HID device support"
988 Support for Alps I2C HID touchpads and StickPointer.
989 Say Y here if you have a Alps touchpads over i2c-hid or usbhid
990 and want support for its special functionalities.
996 source "drivers/hid/usbhid/Kconfig"
998 source "drivers/hid/i2c-hid/Kconfig"
1000 source "drivers/hid/intel-ish-hid/Kconfig"