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.
140 Support for Asus notebook built-in keyboard and touchpad via i2c, and
141 the Asus Republic of Gamers laptop keyboard special keys.
153 Support for Aureal Cy se W-01RN Remote Controller and other Aureal derived remotes.
156 tristate "Belkin Flip KVM and Wireless keyboard"
160 Support for Belkin Flip KVM and Wireless keyboard.
163 tristate "Betop Production Inc. force feedback support"
165 select INPUT_FF_MEMLESS
167 Say Y here if you want to enable force feedback support for devices by
168 BETOP Production Ltd.
169 Currently the following devices are known to be supported:
170 - BETOP 2185 PC & BFM MODE
173 tristate "Cherry Cymotion keyboard"
177 Support for Cherry Cymotion keyboard.
180 tristate "Chicony devices"
184 Support for Chicony Tactical pad and special keys on Chicony keyboards.
187 tristate "Corsair devices"
188 depends on HID && USB && LEDS_CLASS
190 Support for Corsair devices that are not fully compliant with the
198 tristate "Prodikeys PC-MIDI Keyboard support"
199 depends on HID && SND
202 Support for Prodikeys PC-MIDI Keyboard device support.
203 Say Y here to enable support for this device.
204 - Prodikeys PC-MIDI keyboard.
205 The Prodikeys PC-MIDI acts as a USB Audio device, with one MIDI
206 input and one MIDI output. These MIDI jacks appear as
207 a sound "card" in the ALSA sound system.
208 Note: if you say N here, this device will still function as a basic
209 multimedia keyboard, but will lack support for the musical keyboard
210 and some additional multimedia keys.
213 tristate "CMedia CM6533 HID audio jack controls"
216 Support for CMedia CM6533 HID audio jack controls.
219 tristate "Silicon Labs CP2112 HID USB-to-SMBus Bridge support"
220 depends on USB_HID && I2C && GPIOLIB && GPIOLIB_IRQCHIP
222 Support for Silicon Labs CP2112 HID USB to SMBus Master Bridge.
223 This is a HID device driver which registers as an i2c adapter
224 and gpiochip to expose these functions of the CP2112. The
225 customizable USB descriptor fields are exposed as sysfs attributes.
228 tristate "Cypress mouse and barcode readers"
232 Support for cypress mouse and barcode readers.
234 config HID_DRAGONRISE
235 tristate "DragonRise Inc. game controller"
238 Say Y here if you have DragonRise Inc. game controllers.
239 These might be branded as:
241 - Media-tech MT1504 "Rogue"
243 - Defender Game Master
246 bool "DragonRise Inc. force feedback"
247 depends on HID_DRAGONRISE
248 select INPUT_FF_MEMLESS
250 Say Y here if you want to enable force feedback support for DragonRise Inc.
254 tristate "EMS Production Inc. force feedback support"
256 select INPUT_FF_MEMLESS
258 Say Y here if you want to enable force feedback support for devices by
260 Currently the following devices are known to be supported:
261 - Trio Linker Plus II
264 tristate "ELECOM BM084 bluetooth mouse"
267 Support for the ELECOM BM084 (bluetooth mouse).
270 tristate "ELO USB 4000/4500 touchscreen"
273 Support for the ELO USB 4000/4500 touchscreens. Note that this is for
274 different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
277 tristate "Ezkey BTC 8193 keyboard"
281 Support for Ezkey BTC 8193 keyboard.
284 tristate "Gembird Joypad"
287 Support for Gembird JPD-DualForce 2.
290 tristate "Google Fiber TV Box remote control support"
293 Support for Google Fiber TV Box remote controls
296 tristate "Holtek HID devices"
299 Support for Holtek based devices:
300 - Holtek On Line Grip based game controller
301 - Trust GXT 18 Gaming Keyboard
302 - Sharkoon Drakonia / Perixx MX-2000 gaming mice
303 - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
305 - SHARKOON DarkGlider Gaming mouse
306 - LEETGION Hellion Gaming Mouse
309 bool "Holtek On Line Grip force feedback support"
310 depends on HID_HOLTEK
311 select INPUT_FF_MEMLESS
313 Say Y here if you have a Holtek On Line Grip based game controller
314 and want to have force feedback support for it.
317 tristate "MSI GT68xR LED support"
318 depends on LEDS_CLASS && USB_HID
320 Say Y here if you want to enable support for the three MSI GT68xR LEDs
322 This driver support following modes:
323 - Normal: LEDs are fully on when enabled
324 - Audio: LEDs brightness depends on sound level
325 - Breathing: LEDs brightness varies at human breathing rate
327 Currently the following devices are know to be supported:
331 tristate "Keytouch HID devices"
334 Support for Keytouch HID devices not fully compliant with
335 the specification. Currently supported:
339 tristate "KYE/Genius devices"
342 Support for KYE/Genius devices not fully compliant with HID standard:
344 - EasyPen i405X tablet
345 - MousePen i608X tablet
346 - EasyPen M610X tablet
352 Support for UC-Logic and Huion tablets.
358 Support for Waltop tablets.
361 tristate "Gyration remote control"
364 Support for Gyration remote control.
367 tristate "ION iCade arcade controller"
370 Support for the ION iCade arcade controller to work as a joystick.
372 To compile this driver as a module, choose M here: the
373 module will be called hid-icade.
376 tristate "Twinhan IR remote control"
379 Support for Twinhan IR remote control.
381 config HID_KENSINGTON
382 tristate "Kensington Slimblade Trackball"
386 Support for Kensington Slimblade Trackball.
392 Support for LC-Power RC1000MCE RF remote control.
395 tristate "Simple RGB LED support"
397 depends on LEDS_CLASS
399 Support for simple RGB LED devices. Currently supported are:
400 - Riso Kagaku Webmail Notifier
401 - Dream Cheeky Webmail Notifier and Friends Alert
403 - Delcom Visual Signal Indicator Generation 2
406 To compile this driver as a module, choose M here: the
407 module will be called hid-led.
410 tristate "Lenovo / Thinkpad devices"
415 Support for Lenovo devices that are not fully compliant with HID standard.
417 Say Y if you want support for the non-compliant features of the Lenovo
418 Thinkpad standalone keyboards, e.g:
419 - ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
421 - ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
422 - ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
425 tristate "Logitech devices"
429 Support for Logitech devices that are not fully compliant with HID standard.
431 config HID_LOGITECH_DJ
432 tristate "Logitech Unifying receivers full support"
434 depends on HID_LOGITECH
435 select HID_LOGITECH_HIDPP
437 Say Y if you want support for Logitech Unifying receivers and devices.
438 Unifying receivers are capable of pairing up to 6 Logitech compliant
439 devices to the same receiver. Without this driver it will be handled by
440 generic USB_HID driver and all incoming events will be multiplexed
441 into a single mouse and a single keyboard device.
443 config HID_LOGITECH_HIDPP
444 tristate "Logitech HID++ devices support"
445 depends on HID_LOGITECH
447 Support for Logitech devices relyingon the HID++ Logitech specification
449 Say Y if you want support for Logitech devices relying on the HID++
450 specification. Such devices are the various Logitech Touchpads (T650,
451 T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
455 bool "Logitech force feedback support"
456 depends on HID_LOGITECH
457 select INPUT_FF_MEMLESS
459 Say Y here if you have one of these devices:
460 - Logitech WingMan Cordless RumblePad
461 - Logitech WingMan Cordless RumblePad 2
462 - Logitech WingMan Force 3D
464 and if you want to enable force feedback for them.
465 Note: if you say N here, this device will still be supported, but without
468 config LOGIRUMBLEPAD2_FF
469 bool "Logitech force feedback support (variant 2)"
470 depends on HID_LOGITECH
471 select INPUT_FF_MEMLESS
473 Say Y here if you want to enable force feedback support for:
475 - Logitech Rumblepad 2
476 - Logitech Formula Vibration Feedback Wheel
479 bool "Logitech Flight System G940 force feedback support"
480 depends on HID_LOGITECH
481 select INPUT_FF_MEMLESS
483 Say Y here if you want to enable force feedback support for Logitech
484 Flight System G940 devices.
487 bool "Logitech wheels configuration and force feedback support"
488 depends on HID_LOGITECH
489 select INPUT_FF_MEMLESS
492 Say Y here if you want to enable force feedback and range setting(*)
493 support for following Logitech wheels:
497 - Logitech Driving Force
498 - Logitech Driving Force Pro (*)
499 - Logitech Driving Force GT (*)
500 - Logitech Driving Force EX/RX
501 - Logitech Driving Force Wireless
502 - Logitech Speed Force Wireless
503 - Logitech MOMO Force
504 - Logitech MOMO Racing Force
505 - Logitech Formula Force GP
506 - Logitech Formula Force EX/RX
507 - Logitech Wingman Formula Force GP
509 config HID_MAGICMOUSE
510 tristate "Apple Magic Mouse/Trackpad multi-touch support"
513 Support for the Apple Magic Mouse/Trackpad multi-touch.
515 Say Y here if you want support for the multi-touch features of the
516 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
519 tristate "Mayflash game controller adapter force feedback"
521 select INPUT_FF_MEMLESS
523 Say Y here if you have HJZ Mayflash PS3 game controller adapters
524 and want to enable force feedback support.
527 tristate "Microsoft non-fully HID-compliant devices"
531 Support for Microsoft devices that are not fully compliant with HID standard.
534 tristate "Monterey Genius KB29E keyboard"
538 Support for Monterey Genius KB29E.
540 config HID_MULTITOUCH
541 tristate "HID Multitouch panels"
544 Generic support for HID multitouch panels.
546 Say Y here if you have one of the following devices:
547 - 3M PCT touch screens
548 - ActionStar dual touch panels
550 - Cando dual touch panels
554 - Cypress TrueTouch panels
555 - Elan Microelectronics touch panels
556 - Elo TouchSystems IntelliTouch Plus panels
557 - GeneralTouch 'Sensing Win7-TwoFinger' panels
559 - Hanvon dual touch panels
560 - Ilitek dual touch panels
561 - IrTouch Infrared USB panels
562 - LG Display panels (Dell ST2220Tc)
563 - Lumio CrystalTouch panels
564 - MosArt dual-touch panels
565 - Panasonic multitouch panels
566 - PenMount dual touch panels
567 - Perixx Peripad 701 touchpad
568 - PixArt optical touch screen
569 - Pixcir dual touch panels
571 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
572 - SiS multitouch panels
573 - Stantum multitouch panels
574 - Touch International Panels
576 - Wistron optical touch panels
577 - XAT optical touch panels
578 - Xiroku optical touch panels
579 - Zytronic touch panels
583 To compile this driver as a module, choose M here: the
584 module will be called hid-multitouch.
587 tristate "N-Trig touch screen"
590 Support for N-Trig touch screen.
593 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
596 There are certain devices which have LogicalMaximum wrong in the keyboard
597 usage page of their report descriptor. The most prevailing ones so far
598 are manufactured by Ortek, thus the name of the driver. Currently
599 supported devices by this driver are
603 - Skycable wireless presenter
605 config HID_PANTHERLORD
606 tristate "Pantherlord/GreenAsia game controller"
609 Say Y here if you have a PantherLord/GreenAsia based game controller
612 config PANTHERLORD_FF
613 bool "Pantherlord force feedback support"
614 depends on HID_PANTHERLORD
615 select INPUT_FF_MEMLESS
617 Say Y here if you have a PantherLord/GreenAsia based game controller
618 or adapter and want to enable force feedback support for it.
621 tristate "Penmount touch device"
624 This selects a driver for the PenMount 6000 touch controller.
626 The driver works around a problem in the report descript allowing
627 the userspace to touch events instead of mouse events.
629 Say Y here if you have a Penmount based touch controller.
632 tristate "Petalynx Maxter remote control"
635 Support for Petalynx Maxter remote control.
638 tristate "PicoLCD (graphic version)"
641 This provides support for Minibox PicoLCD devices, currently
642 only the graphical ones are supported.
644 This includes support for the following device features:
646 - Switching between Firmware and Flash mode
647 - EEProm / Flash access (via debugfs)
648 Features selectively enabled:
649 - Framebuffer for monochrome 256x64 display
652 - General purpose outputs
653 Features that are not (yet) supported:
656 config HID_PICOLCD_FB
657 bool "Framebuffer support" if EXPERT
659 depends on HID_PICOLCD
660 depends on HID_PICOLCD=FB || FB=y
661 select FB_DEFERRED_IO
662 select FB_SYS_FILLRECT
663 select FB_SYS_COPYAREA
664 select FB_SYS_IMAGEBLIT
667 Provide access to PicoLCD's 256x64 monochrome display via a
670 config HID_PICOLCD_BACKLIGHT
671 bool "Backlight control" if EXPERT
673 depends on HID_PICOLCD
674 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
676 Provide access to PicoLCD's backlight control via backlight
679 config HID_PICOLCD_LCD
680 bool "Contrast control" if EXPERT
682 depends on HID_PICOLCD
683 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
685 Provide access to PicoLCD's LCD contrast via lcd class.
687 config HID_PICOLCD_LEDS
688 bool "GPO via leds class" if EXPERT
690 depends on HID_PICOLCD
691 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
693 Provide access to PicoLCD's GPO pins via leds class.
695 config HID_PICOLCD_CIR
696 bool "CIR via RC class" if EXPERT
698 depends on HID_PICOLCD
699 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
701 Provide access to PicoLCD's CIR interface via remote control (LIRC).
703 config HID_PLANTRONICS
704 tristate "Plantronics USB HID Driver"
707 Provides HID support for Plantronics USB audio devices.
708 Correctly maps vendor unique volume up/down HID usages to
709 KEY_VOLUMEUP and KEY_VOLUMEDOWN events and prevents core mapping
710 of other vendor unique HID usages to random mouse events.
712 Say M here if you may ever plug in a Plantronics USB audio device.
715 tristate "Primax non-fully HID-compliant devices"
718 Support for Primax devices that are not fully compliant with the
722 tristate "Roccat device support"
725 Support for Roccat devices.
726 Say Y here if you have a Roccat mouse or keyboard and want
727 support for its special functionalities.
730 tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
733 Support for Saitek devices that are not fully compliant with the
737 - PS1000 Dual Analog Pad
738 - Saitek R.A.T.7, R.A.T.9, M.M.O.7 Gaming Mice
739 - Mad Catz R.A.T.5, R.A.T.9 Gaming Mice
742 tristate "Samsung InfraRed remote control or keyboards"
745 Support for Samsung InfraRed remote control or keyboards.
748 tristate "Sony PS2/3/4 accessories"
751 depends on LEDS_CLASS
756 * Sony PS3 6-axis controllers
757 * Sony PS4 DualShock 4 controllers
759 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
760 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
763 bool "Sony PS2/3/4 accessories force feedback support"
765 select INPUT_FF_MEMLESS
767 Say Y here if you have a Sony PS2/3/4 accessory and want to enable
768 force feedback support for it.
771 tristate "Speedlink VAD Cezanne mouse support"
774 Support for Speedlink Vicious and Divine Cezanne mouse.
776 config HID_STEELSERIES
777 tristate "Steelseries SRW-S1 steering wheel support"
780 Support for Steelseries SRW-S1 steering wheel
783 tristate "Sunplus wireless desktop"
786 Support for Sunplus wireless desktop.
789 tristate "Synaptics RMI4 device support"
797 Support for Synaptics RMI4 touchpads.
798 Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
799 and want support for its special functionalities.
802 tristate "GreenAsia (Product ID 0x12) game controller support"
805 Say Y here if you have a GreenAsia (Product ID 0x12) based game
806 controller or adapter.
809 bool "GreenAsia (Product ID 0x12) force feedback support"
810 depends on HID_GREENASIA
811 select INPUT_FF_MEMLESS
813 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
814 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
815 and want to enable force feedback support for it.
817 config HID_HYPERV_MOUSE
818 tristate "Microsoft Hyper-V mouse driver"
821 Select this option to enable the Hyper-V mouse driver.
823 config HID_SMARTJOYPLUS
824 tristate "SmartJoy PLUS PS2/USB adapter support"
827 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
828 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
830 Note that DDR (Dance Dance Revolution) mode is not supported, nor
831 is pressure sensitive buttons on the pro models.
833 config SMARTJOYPLUS_FF
834 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
835 depends on HID_SMARTJOYPLUS
836 select INPUT_FF_MEMLESS
838 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
839 enable force feedback support for it.
842 tristate "TiVo Slide Bluetooth remote control support"
845 Say Y if you have a TiVo Slide Bluetooth remote control.
848 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
851 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
852 CLLRCMCE remote control.
855 tristate "ThingM blink(1) USB RGB LED"
857 depends on LEDS_CLASS
860 Support for the ThingM blink(1) USB RGB LED. This driver has been
861 merged into the generic hid led driver. Config symbol HID_THINGM
862 just selects HID_LED and will be removed soon.
864 config HID_THRUSTMASTER
865 tristate "ThrustMaster devices support"
868 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
869 a THRUSTMASTER Ferrari GT Rumble Wheel.
871 config THRUSTMASTER_FF
872 bool "ThrustMaster devices force feedback support"
873 depends on HID_THRUSTMASTER
874 select INPUT_FF_MEMLESS
876 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
877 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
878 Rumble Force or Force Feedback Wheel.
881 tristate "THQ PS3 uDraw tablet"
884 Say Y here if you want to use the THQ uDraw gaming tablet for
888 tristate "Wacom Intuos/Graphire tablet support (USB)"
895 Say Y here if you want to use the USB or BT version of the Wacom Intuos
898 To compile this driver as a module, choose M here: the
899 module will be called wacom.
902 tristate "Nintendo Wii / Wii U peripherals"
904 depends on LEDS_CLASS
906 select INPUT_FF_MEMLESS
908 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
909 devices are the Wii Remote and its extension devices, but also devices
910 based on the Wii Remote like the Wii U Pro Controller or the
913 Support for all official Nintendo extensions is available, however, 3rd
914 party extensions might not be supported. Please report these devices to:
915 http://github.com/dvdhrm/xwiimote/issues
917 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
918 the Wii U Gamepad) might be supported in the future. But currently
919 support is limited to Bluetooth based devices.
923 To compile this driver as a module, choose M here: the
924 module will be called hid-wiimote.
927 tristate "Xin-Mo non-fully compliant devices"
930 Support for Xin-Mo devices that are not fully compliant with the HID
931 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
932 if you have a Xin-Mo Dual Arcade controller.
935 tristate "Zeroplus based game controller support"
938 Say Y here if you have a Zeroplus based game controller.
941 bool "Zeroplus based game controller force feedback support"
942 depends on HID_ZEROPLUS
943 select INPUT_FF_MEMLESS
945 Say Y here if you have a Zeroplus based game controller and want
946 to have force feedback support for it.
949 tristate "Zydacron remote control support"
952 Support for Zydacron remote control.
954 config HID_SENSOR_HUB
955 tristate "HID Sensors framework support"
956 depends on HID && HAS_IOMEM
960 Support for HID Sensor framework. This creates a MFD instance
961 for a sensor hub and identifies all the sensors connected to it.
962 Each sensor is registered as a MFD cell, so that sensor specific
963 processing can be done in a separate driver. Each sensor
964 drivers can use the service provided by this driver to register
965 for events and handle data streams. Each sensor driver can format
966 data and present to user mode using input or IIO interface.
968 config HID_SENSOR_CUSTOM_SENSOR
969 tristate "HID Sensors hub custom sensor support"
970 depends on HID_SENSOR_HUB
973 HID Sensor hub specification allows definition of some custom and
974 generic sensors. Unlike other HID sensors, they can't be exported
975 via Linux IIO because of custom fields. This is up to the manufacturer
976 to decide how to interpret these special sensor ids and process in
977 the user space. Currently some manufacturers are using these ids for
978 sensor calibration and debugging other sensors. Manufacturers
979 should't use these special custom sensor ids to export any of the
981 Select this config option for custom/generic sensor support.
984 tristate "Alps HID device support"
987 Support for Alps I2C HID touchpads and StickPointer.
988 Say Y here if you have a Alps touchpads over i2c-hid or usbhid
989 and want support for its special functionalities.
995 source "drivers/hid/usbhid/Kconfig"
997 source "drivers/hid/i2c-hid/Kconfig"
999 source "drivers/hid/intel-ish-hid/Kconfig"