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.
142 Support for Asus notebook built-in keyboard via i2c.
152 Support for Aureal Cy se W-01RN Remote Controller and other Aureal derived remotes.
155 tristate "Belkin Flip KVM and Wireless keyboard"
159 Support for Belkin Flip KVM and Wireless keyboard.
162 tristate "Betop Production Inc. force feedback support"
164 select INPUT_FF_MEMLESS
166 Say Y here if you want to enable force feedback support for devices by
167 BETOP Production Ltd.
168 Currently the following devices are known to be supported:
169 - BETOP 2185 PC & BFM MODE
172 tristate "Cherry Cymotion keyboard"
176 Support for Cherry Cymotion keyboard.
179 tristate "Chicony devices"
183 Support for Chicony Tactical pad and special keys on Chicony keyboards.
186 tristate "Corsair devices"
187 depends on USB_HID && LEDS_CLASS
189 Support for Corsair devices that are not fully compliant with the
197 tristate "Prodikeys PC-MIDI Keyboard support"
198 depends on USB_HID && SND
201 Support for Prodikeys PC-MIDI Keyboard device support.
202 Say Y here to enable support for this device.
203 - Prodikeys PC-MIDI keyboard.
204 The Prodikeys PC-MIDI acts as a USB Audio device, with one MIDI
205 input and one MIDI output. These MIDI jacks appear as
206 a sound "card" in the ALSA sound system.
207 Note: if you say N here, this device will still function as a basic
208 multimedia keyboard, but will lack support for the musical keyboard
209 and some additional multimedia keys.
212 tristate "CMedia CM6533 HID audio jack controls"
215 Support for CMedia CM6533 HID audio jack controls.
218 tristate "Silicon Labs CP2112 HID USB-to-SMBus Bridge support"
219 depends on USB_HID && I2C && GPIOLIB
221 Support for Silicon Labs CP2112 HID USB to SMBus Master Bridge.
222 This is a HID device driver which registers as an i2c adapter
223 and gpiochip to expose these functions of the CP2112. The
224 customizable USB descriptor fields are exposed as sysfs attributes.
227 tristate "Cypress mouse and barcode readers"
231 Support for cypress mouse and barcode readers.
233 config HID_DRAGONRISE
234 tristate "DragonRise Inc. game controller"
237 Say Y here if you have DragonRise Inc. game controllers.
238 These might be branded as:
240 - Media-tech MT1504 "Rogue"
242 - Defender Game Master
245 bool "DragonRise Inc. force feedback"
246 depends on HID_DRAGONRISE
247 select INPUT_FF_MEMLESS
249 Say Y here if you want to enable force feedback support for DragonRise Inc.
253 tristate "EMS Production Inc. force feedback support"
255 select INPUT_FF_MEMLESS
257 Say Y here if you want to enable force feedback support for devices by
259 Currently the following devices are known to be supported:
260 - Trio Linker Plus II
263 tristate "ELECOM BM084 bluetooth mouse"
266 Support for the ELECOM BM084 (bluetooth mouse).
269 tristate "ELO USB 4000/4500 touchscreen"
272 Support for the ELO USB 4000/4500 touchscreens. Note that this is for
273 different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
276 tristate "Ezkey BTC 8193 keyboard"
280 Support for Ezkey BTC 8193 keyboard.
283 tristate "Gembird Joypad"
286 Support for Gembird JPD-DualForce 2.
289 tristate "Google Fiber TV Box remote control support"
292 Support for Google Fiber TV Box remote controls
295 tristate "Holtek HID devices"
298 Support for Holtek based devices:
299 - Holtek On Line Grip based game controller
300 - Trust GXT 18 Gaming Keyboard
301 - Sharkoon Drakonia / Perixx MX-2000 gaming mice
302 - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
304 - SHARKOON DarkGlider Gaming mouse
305 - LEETGION Hellion Gaming Mouse
308 bool "Holtek On Line Grip force feedback support"
309 depends on HID_HOLTEK
310 select INPUT_FF_MEMLESS
312 Say Y here if you have a Holtek On Line Grip based game controller
313 and want to have force feedback support for it.
316 tristate "MSI GT68xR LED support"
317 depends on LEDS_CLASS && USB_HID
319 Say Y here if you want to enable support for the three MSI GT68xR LEDs
321 This driver support following modes:
322 - Normal: LEDs are fully on when enabled
323 - Audio: LEDs brightness depends on sound level
324 - Breathing: LEDs brightness varies at human breathing rate
326 Currently the following devices are know to be supported:
330 tristate "Keytouch HID devices"
333 Support for Keytouch HID devices not fully compliant with
334 the specification. Currently supported:
338 tristate "KYE/Genius devices"
341 Support for KYE/Genius devices not fully compliant with HID standard:
343 - EasyPen i405X tablet
344 - MousePen i608X tablet
345 - EasyPen M610X tablet
351 Support for UC-Logic and Huion tablets.
357 Support for Waltop tablets.
360 tristate "Gyration remote control"
363 Support for Gyration remote control.
366 tristate "ION iCade arcade controller"
369 Support for the ION iCade arcade controller to work as a joystick.
371 To compile this driver as a module, choose M here: the
372 module will be called hid-icade.
375 tristate "Twinhan IR remote control"
378 Support for Twinhan IR remote control.
380 config HID_KENSINGTON
381 tristate "Kensington Slimblade Trackball"
385 Support for Kensington Slimblade Trackball.
391 Support for LC-Power RC1000MCE RF remote control.
394 tristate "Simple RGB LED support"
396 depends on LEDS_CLASS
398 Support for simple RGB LED devices. Currently supported are:
399 - Riso Kagaku Webmail Notifier
400 - Dream Cheeky Webmail Notifier and Friends Alert
402 - Delcom Visual Signal Indicator Generation 2
405 To compile this driver as a module, choose M here: the
406 module will be called hid-led.
409 tristate "Lenovo / Thinkpad devices"
414 Support for Lenovo devices that are not fully compliant with HID standard.
416 Say Y if you want support for the non-compliant features of the Lenovo
417 Thinkpad standalone keyboards, e.g:
418 - ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
420 - ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
421 - ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
424 tristate "Logitech devices"
428 Support for Logitech devices that are not fully compliant with HID standard.
430 config HID_LOGITECH_DJ
431 tristate "Logitech Unifying receivers full support"
433 depends on HID_LOGITECH
434 select HID_LOGITECH_HIDPP
436 Say Y if you want support for Logitech Unifying receivers and devices.
437 Unifying receivers are capable of pairing up to 6 Logitech compliant
438 devices to the same receiver. Without this driver it will be handled by
439 generic USB_HID driver and all incoming events will be multiplexed
440 into a single mouse and a single keyboard device.
442 config HID_LOGITECH_HIDPP
443 tristate "Logitech HID++ devices support"
444 depends on HID_LOGITECH
446 Support for Logitech devices relyingon the HID++ Logitech specification
448 Say Y if you want support for Logitech devices relying on the HID++
449 specification. Such devices are the various Logitech Touchpads (T650,
450 T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
454 bool "Logitech force feedback support"
455 depends on HID_LOGITECH
456 select INPUT_FF_MEMLESS
458 Say Y here if you have one of these devices:
459 - Logitech WingMan Cordless RumblePad
460 - Logitech WingMan Cordless RumblePad 2
461 - Logitech WingMan Force 3D
463 and if you want to enable force feedback for them.
464 Note: if you say N here, this device will still be supported, but without
467 config LOGIRUMBLEPAD2_FF
468 bool "Logitech force feedback support (variant 2)"
469 depends on HID_LOGITECH
470 select INPUT_FF_MEMLESS
472 Say Y here if you want to enable force feedback support for:
474 - Logitech Rumblepad 2
475 - Logitech Formula Vibration Feedback Wheel
478 bool "Logitech Flight System G940 force feedback support"
479 depends on HID_LOGITECH
480 select INPUT_FF_MEMLESS
482 Say Y here if you want to enable force feedback support for Logitech
483 Flight System G940 devices.
486 bool "Logitech wheels configuration and force feedback support"
487 depends on HID_LOGITECH
488 select INPUT_FF_MEMLESS
491 Say Y here if you want to enable force feedback and range setting(*)
492 support for following Logitech wheels:
496 - Logitech Driving Force
497 - Logitech Driving Force Pro (*)
498 - Logitech Driving Force GT (*)
499 - Logitech Driving Force EX/RX
500 - Logitech Driving Force Wireless
501 - Logitech Speed Force Wireless
502 - Logitech MOMO Force
503 - Logitech MOMO Racing Force
504 - Logitech Formula Force GP
505 - Logitech Formula Force EX/RX
506 - Logitech Wingman Formula Force GP
508 config HID_MAGICMOUSE
509 tristate "Apple Magic Mouse/Trackpad multi-touch support"
512 Support for the Apple Magic Mouse/Trackpad multi-touch.
514 Say Y here if you want support for the multi-touch features of the
515 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
518 tristate "Microsoft non-fully HID-compliant devices"
522 Support for Microsoft devices that are not fully compliant with HID standard.
525 tristate "Monterey Genius KB29E keyboard"
529 Support for Monterey Genius KB29E.
531 config HID_MULTITOUCH
532 tristate "HID Multitouch panels"
535 Generic support for HID multitouch panels.
537 Say Y here if you have one of the following devices:
538 - 3M PCT touch screens
539 - ActionStar dual touch panels
541 - Cando dual touch panels
545 - Cypress TrueTouch panels
546 - Elan Microelectronics touch panels
547 - Elo TouchSystems IntelliTouch Plus panels
548 - GeneralTouch 'Sensing Win7-TwoFinger' panels
550 - Hanvon dual touch panels
551 - Ilitek dual touch panels
552 - IrTouch Infrared USB panels
553 - LG Display panels (Dell ST2220Tc)
554 - Lumio CrystalTouch panels
555 - MosArt dual-touch panels
556 - Panasonic multitouch panels
557 - PenMount dual touch panels
558 - Perixx Peripad 701 touchpad
559 - PixArt optical touch screen
560 - Pixcir dual touch panels
562 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
563 - SiS multitouch panels
564 - Stantum multitouch panels
565 - Touch International Panels
567 - Wistron optical touch panels
568 - XAT optical touch panels
569 - Xiroku optical touch panels
570 - Zytronic touch panels
574 To compile this driver as a module, choose M here: the
575 module will be called hid-multitouch.
578 tristate "N-Trig touch screen"
581 Support for N-Trig touch screen.
584 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
587 There are certain devices which have LogicalMaximum wrong in the keyboard
588 usage page of their report descriptor. The most prevailing ones so far
589 are manufactured by Ortek, thus the name of the driver. Currently
590 supported devices by this driver are
594 - Skycable wireless presenter
596 config HID_PANTHERLORD
597 tristate "Pantherlord/GreenAsia game controller"
600 Say Y here if you have a PantherLord/GreenAsia based game controller
603 config PANTHERLORD_FF
604 bool "Pantherlord force feedback support"
605 depends on HID_PANTHERLORD
606 select INPUT_FF_MEMLESS
608 Say Y here if you have a PantherLord/GreenAsia based game controller
609 or adapter and want to enable force feedback support for it.
612 tristate "Penmount touch device"
615 This selects a driver for the PenMount 6000 touch controller.
617 The driver works around a problem in the report descript allowing
618 the userspace to touch events instead of mouse events.
620 Say Y here if you have a Penmount based touch controller.
623 tristate "Petalynx Maxter remote control"
626 Support for Petalynx Maxter remote control.
629 tristate "PicoLCD (graphic version)"
632 This provides support for Minibox PicoLCD devices, currently
633 only the graphical ones are supported.
635 This includes support for the following device features:
637 - Switching between Firmware and Flash mode
638 - EEProm / Flash access (via debugfs)
639 Features selectively enabled:
640 - Framebuffer for monochrome 256x64 display
643 - General purpose outputs
644 Features that are not (yet) supported:
647 config HID_PICOLCD_FB
648 bool "Framebuffer support" if EXPERT
650 depends on HID_PICOLCD
651 depends on HID_PICOLCD=FB || FB=y
652 select FB_DEFERRED_IO
653 select FB_SYS_FILLRECT
654 select FB_SYS_COPYAREA
655 select FB_SYS_IMAGEBLIT
658 Provide access to PicoLCD's 256x64 monochrome display via a
661 config HID_PICOLCD_BACKLIGHT
662 bool "Backlight control" if EXPERT
664 depends on HID_PICOLCD
665 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
667 Provide access to PicoLCD's backlight control via backlight
670 config HID_PICOLCD_LCD
671 bool "Contrast control" if EXPERT
673 depends on HID_PICOLCD
674 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
676 Provide access to PicoLCD's LCD contrast via lcd class.
678 config HID_PICOLCD_LEDS
679 bool "GPO via leds class" if EXPERT
681 depends on HID_PICOLCD
682 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
684 Provide access to PicoLCD's GPO pins via leds class.
686 config HID_PICOLCD_CIR
687 bool "CIR via RC class" if EXPERT
689 depends on HID_PICOLCD
690 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
692 Provide access to PicoLCD's CIR interface via remote control (LIRC).
694 config HID_PLANTRONICS
695 tristate "Plantronics USB HID Driver"
698 Provides HID support for Plantronics USB audio devices.
699 Correctly maps vendor unique volume up/down HID usages to
700 KEY_VOLUMEUP and KEY_VOLUMEDOWN events and prevents core mapping
701 of other vendor unique HID usages to random mouse events.
703 Say M here if you may ever plug in a Plantronics USB audio device.
706 tristate "Primax non-fully HID-compliant devices"
709 Support for Primax devices that are not fully compliant with the
713 tristate "Roccat device support"
716 Support for Roccat devices.
717 Say Y here if you have a Roccat mouse or keyboard and want
718 support for its special functionalities.
721 tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
724 Support for Saitek devices that are not fully compliant with the
728 - PS1000 Dual Analog Pad
729 - Saitek R.A.T.7, R.A.T.9, M.M.O.7 Gaming Mice
730 - Mad Catz R.A.T.5, R.A.T.9 Gaming Mice
733 tristate "Samsung InfraRed remote control or keyboards"
736 Support for Samsung InfraRed remote control or keyboards.
739 tristate "Sony PS2/3/4 accessories"
742 depends on LEDS_CLASS
747 * Sony PS3 6-axis controllers
748 * Sony PS4 DualShock 4 controllers
750 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
751 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
754 bool "Sony PS2/3/4 accessories force feedback support"
756 select INPUT_FF_MEMLESS
758 Say Y here if you have a Sony PS2/3/4 accessory and want to enable
759 force feedback support for it.
762 tristate "Speedlink VAD Cezanne mouse support"
765 Support for Speedlink Vicious and Divine Cezanne mouse.
767 config HID_STEELSERIES
768 tristate "Steelseries SRW-S1 steering wheel support"
771 Support for Steelseries SRW-S1 steering wheel
774 tristate "Sunplus wireless desktop"
777 Support for Sunplus wireless desktop.
780 tristate "Synaptics RMI4 device support"
783 Support for Synaptics RMI4 touchpads.
784 Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
785 and want support for its special functionalities.
788 tristate "GreenAsia (Product ID 0x12) game controller support"
791 Say Y here if you have a GreenAsia (Product ID 0x12) based game
792 controller or adapter.
795 bool "GreenAsia (Product ID 0x12) force feedback support"
796 depends on HID_GREENASIA
797 select INPUT_FF_MEMLESS
799 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
800 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
801 and want to enable force feedback support for it.
803 config HID_HYPERV_MOUSE
804 tristate "Microsoft Hyper-V mouse driver"
807 Select this option to enable the Hyper-V mouse driver.
809 config HID_SMARTJOYPLUS
810 tristate "SmartJoy PLUS PS2/USB adapter support"
813 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
814 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
816 Note that DDR (Dance Dance Revolution) mode is not supported, nor
817 is pressure sensitive buttons on the pro models.
819 config SMARTJOYPLUS_FF
820 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
821 depends on HID_SMARTJOYPLUS
822 select INPUT_FF_MEMLESS
824 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
825 enable force feedback support for it.
828 tristate "TiVo Slide Bluetooth remote control support"
831 Say Y if you have a TiVo Slide Bluetooth remote control.
834 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
837 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
838 CLLRCMCE remote control.
841 tristate "ThingM blink(1) USB RGB LED"
843 depends on LEDS_CLASS
846 Support for the ThingM blink(1) USB RGB LED. This driver has been
847 merged into the generic hid led driver. Config symbol HID_THINGM
848 just selects HID_LED and will be removed soon.
850 config HID_THRUSTMASTER
851 tristate "ThrustMaster devices support"
854 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
855 a THRUSTMASTER Ferrari GT Rumble Wheel.
857 config THRUSTMASTER_FF
858 bool "ThrustMaster devices force feedback support"
859 depends on HID_THRUSTMASTER
860 select INPUT_FF_MEMLESS
862 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
863 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
864 Rumble Force or Force Feedback Wheel.
867 tristate "Wacom Intuos/Graphire tablet support (USB)"
874 Say Y here if you want to use the USB or BT version of the Wacom Intuos
877 To compile this driver as a module, choose M here: the
878 module will be called wacom.
881 tristate "Nintendo Wii / Wii U peripherals"
883 depends on LEDS_CLASS
885 select INPUT_FF_MEMLESS
887 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
888 devices are the Wii Remote and its extension devices, but also devices
889 based on the Wii Remote like the Wii U Pro Controller or the
892 Support for all official Nintendo extensions is available, however, 3rd
893 party extensions might not be supported. Please report these devices to:
894 http://github.com/dvdhrm/xwiimote/issues
896 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
897 the Wii U Gamepad) might be supported in the future. But currently
898 support is limited to Bluetooth based devices.
902 To compile this driver as a module, choose M here: the
903 module will be called hid-wiimote.
906 tristate "Xin-Mo non-fully compliant devices"
909 Support for Xin-Mo devices that are not fully compliant with the HID
910 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
911 if you have a Xin-Mo Dual Arcade controller.
914 tristate "Zeroplus based game controller support"
917 Say Y here if you have a Zeroplus based game controller.
920 bool "Zeroplus based game controller force feedback support"
921 depends on HID_ZEROPLUS
922 select INPUT_FF_MEMLESS
924 Say Y here if you have a Zeroplus based game controller and want
925 to have force feedback support for it.
928 tristate "Zydacron remote control support"
931 Support for Zydacron remote control.
933 config HID_SENSOR_HUB
934 tristate "HID Sensors framework support"
935 depends on HID && HAS_IOMEM
939 Support for HID Sensor framework. This creates a MFD instance
940 for a sensor hub and identifies all the sensors connected to it.
941 Each sensor is registered as a MFD cell, so that sensor specific
942 processing can be done in a separate driver. Each sensor
943 drivers can use the service provided by this driver to register
944 for events and handle data streams. Each sensor driver can format
945 data and present to user mode using input or IIO interface.
947 config HID_SENSOR_CUSTOM_SENSOR
948 tristate "HID Sensors hub custom sensor support"
949 depends on HID_SENSOR_HUB
952 HID Sensor hub specification allows definition of some custom and
953 generic sensors. Unlike other HID sensors, they can't be exported
954 via Linux IIO because of custom fields. This is up to the manufacturer
955 to decide how to interpret these special sensor ids and process in
956 the user space. Currently some manufacturers are using these ids for
957 sensor calibration and debugging other sensors. Manufacturers
958 should't use these special custom sensor ids to export any of the
960 Select this config option for custom/generic sensor support.
963 tristate "Alps HID device support"
966 Support for Alps I2C HID touchpads and StickPointer.
967 Say Y here if you have a Alps touchpads over i2c-hid or usbhid
968 and want support for its special functionalities.
974 source "drivers/hid/usbhid/Kconfig"
976 source "drivers/hid/i2c-hid/Kconfig"
978 source "drivers/hid/intel-ish-hid/Kconfig"