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.
153 Support for Asus notebook built-in keyboard and touchpad via i2c.
163 Support for Aureal Cy se W-01RN Remote Controller and other Aureal derived remotes.
166 tristate "Belkin Flip KVM and Wireless keyboard"
170 Support for Belkin Flip KVM and Wireless keyboard.
173 tristate "Betop Production Inc. force feedback support"
175 select INPUT_FF_MEMLESS
177 Say Y here if you want to enable force feedback support for devices by
178 BETOP Production Ltd.
179 Currently the following devices are known to be supported:
180 - BETOP 2185 PC & BFM MODE
183 tristate "Cherry Cymotion keyboard"
187 Support for Cherry Cymotion keyboard.
190 tristate "Chicony devices"
194 Support for Chicony Tactical pad and special keys on Chicony keyboards.
197 tristate "Corsair devices"
198 depends on HID && USB && LEDS_CLASS
200 Support for Corsair devices that are not fully compliant with the
208 tristate "Prodikeys PC-MIDI Keyboard support"
209 depends on HID && SND
212 Support for Prodikeys PC-MIDI Keyboard device support.
213 Say Y here to enable support for this device.
214 - Prodikeys PC-MIDI keyboard.
215 The Prodikeys PC-MIDI acts as a USB Audio device, with one MIDI
216 input and one MIDI output. These MIDI jacks appear as
217 a sound "card" in the ALSA sound system.
218 Note: if you say N here, this device will still function as a basic
219 multimedia keyboard, but will lack support for the musical keyboard
220 and some additional multimedia keys.
223 tristate "CMedia CM6533 HID audio jack controls"
226 Support for CMedia CM6533 HID audio jack controls.
229 tristate "Silicon Labs CP2112 HID USB-to-SMBus Bridge support"
230 depends on USB_HID && I2C && GPIOLIB
231 select GPIOLIB_IRQCHIP
233 Support for Silicon Labs CP2112 HID USB to SMBus Master Bridge.
234 This is a HID device driver which registers as an i2c adapter
235 and gpiochip to expose these functions of the CP2112. The
236 customizable USB descriptor fields are exposed as sysfs attributes.
239 tristate "Cypress mouse and barcode readers"
243 Support for cypress mouse and barcode readers.
245 config HID_DRAGONRISE
246 tristate "DragonRise Inc. game controller"
249 Say Y here if you have DragonRise Inc. game controllers.
250 These might be branded as:
252 - Media-tech MT1504 "Rogue"
254 - Defender Game Master
257 bool "DragonRise Inc. force feedback"
258 depends on HID_DRAGONRISE
259 select INPUT_FF_MEMLESS
261 Say Y here if you want to enable force feedback support for DragonRise Inc.
265 tristate "EMS Production Inc. force feedback support"
267 select INPUT_FF_MEMLESS
269 Say Y here if you want to enable force feedback support for devices by
271 Currently the following devices are known to be supported:
272 - Trio Linker Plus II
275 tristate "ELECOM BM084 bluetooth mouse"
278 Support for the ELECOM BM084 (bluetooth mouse).
281 tristate "ELO USB 4000/4500 touchscreen"
284 Support for the ELO USB 4000/4500 touchscreens. Note that this is for
285 different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
288 tristate "Ezkey BTC 8193 keyboard"
292 Support for Ezkey BTC 8193 keyboard.
295 tristate "Gembird Joypad"
298 Support for Gembird JPD-DualForce 2.
301 tristate "Google Fiber TV Box remote control support"
304 Support for Google Fiber TV Box remote controls
307 tristate "Holtek HID devices"
310 Support for Holtek based devices:
311 - Holtek On Line Grip based game controller
312 - Trust GXT 18 Gaming Keyboard
313 - Sharkoon Drakonia / Perixx MX-2000 gaming mice
314 - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
316 - SHARKOON DarkGlider Gaming mouse
317 - LEETGION Hellion Gaming Mouse
320 bool "Holtek On Line Grip force feedback support"
321 depends on HID_HOLTEK
322 select INPUT_FF_MEMLESS
324 Say Y here if you have a Holtek On Line Grip based game controller
325 and want to have force feedback support for it.
328 tristate "MSI GT68xR LED support"
329 depends on LEDS_CLASS && USB_HID
331 Say Y here if you want to enable support for the three MSI GT68xR LEDs
333 This driver support following modes:
334 - Normal: LEDs are fully on when enabled
335 - Audio: LEDs brightness depends on sound level
336 - Breathing: LEDs brightness varies at human breathing rate
338 Currently the following devices are know to be supported:
342 tristate "Keytouch HID devices"
345 Support for Keytouch HID devices not fully compliant with
346 the specification. Currently supported:
350 tristate "KYE/Genius devices"
353 Support for KYE/Genius devices not fully compliant with HID standard:
355 - EasyPen i405X tablet
356 - MousePen i608X tablet
357 - EasyPen M610X tablet
363 Support for UC-Logic and Huion tablets.
369 Support for Waltop tablets.
372 tristate "Gyration remote control"
375 Support for Gyration remote control.
378 tristate "ION iCade arcade controller"
381 Support for the ION iCade arcade controller to work as a joystick.
383 To compile this driver as a module, choose M here: the
384 module will be called hid-icade.
387 tristate "Twinhan IR remote control"
390 Support for Twinhan IR remote control.
392 config HID_KENSINGTON
393 tristate "Kensington Slimblade Trackball"
397 Support for Kensington Slimblade Trackball.
403 Support for LC-Power RC1000MCE RF remote control.
406 tristate "Simple RGB LED support"
408 depends on LEDS_CLASS
410 Support for simple RGB LED devices. Currently supported are:
411 - Riso Kagaku Webmail Notifier
412 - Dream Cheeky Webmail Notifier and Friends Alert
414 - Delcom Visual Signal Indicator Generation 2
417 To compile this driver as a module, choose M here: the
418 module will be called hid-led.
421 tristate "Lenovo / Thinkpad devices"
426 Support for Lenovo devices that are not fully compliant with HID standard.
428 Say Y if you want support for the non-compliant features of the Lenovo
429 Thinkpad standalone keyboards, e.g:
430 - ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
432 - ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
433 - ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
436 tristate "Logitech devices"
440 Support for Logitech devices that are not fully compliant with HID standard.
442 config HID_LOGITECH_DJ
443 tristate "Logitech Unifying receivers full support"
445 depends on HID_LOGITECH
446 select HID_LOGITECH_HIDPP
448 Say Y if you want support for Logitech Unifying receivers and devices.
449 Unifying receivers are capable of pairing up to 6 Logitech compliant
450 devices to the same receiver. Without this driver it will be handled by
451 generic USB_HID driver and all incoming events will be multiplexed
452 into a single mouse and a single keyboard device.
454 config HID_LOGITECH_HIDPP
455 tristate "Logitech HID++ devices support"
456 depends on HID_LOGITECH
459 Support for Logitech devices relyingon the HID++ Logitech specification
461 Say Y if you want support for Logitech devices relying on the HID++
462 specification. Such devices are the various Logitech Touchpads (T650,
463 T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
467 bool "Logitech force feedback support"
468 depends on HID_LOGITECH
469 select INPUT_FF_MEMLESS
471 Say Y here if you have one of these devices:
472 - Logitech WingMan Cordless RumblePad
473 - Logitech WingMan Cordless RumblePad 2
474 - Logitech WingMan Force 3D
476 and if you want to enable force feedback for them.
477 Note: if you say N here, this device will still be supported, but without
480 config LOGIRUMBLEPAD2_FF
481 bool "Logitech force feedback support (variant 2)"
482 depends on HID_LOGITECH
483 select INPUT_FF_MEMLESS
485 Say Y here if you want to enable force feedback support for:
487 - Logitech Rumblepad 2
488 - Logitech Formula Vibration Feedback Wheel
491 bool "Logitech Flight System G940 force feedback support"
492 depends on HID_LOGITECH
493 select INPUT_FF_MEMLESS
495 Say Y here if you want to enable force feedback support for Logitech
496 Flight System G940 devices.
499 bool "Logitech wheels configuration and force feedback support"
500 depends on HID_LOGITECH
501 select INPUT_FF_MEMLESS
504 Say Y here if you want to enable force feedback and range setting(*)
505 support for following Logitech wheels:
509 - Logitech Driving Force
510 - Logitech Driving Force Pro (*)
511 - Logitech Driving Force GT (*)
512 - Logitech Driving Force EX/RX
513 - Logitech Driving Force Wireless
514 - Logitech Speed Force Wireless
515 - Logitech MOMO Force
516 - Logitech MOMO Racing Force
517 - Logitech Formula Force GP
518 - Logitech Formula Force EX/RX
519 - Logitech Wingman Formula Force GP
521 config HID_MAGICMOUSE
522 tristate "Apple Magic Mouse/Trackpad multi-touch support"
525 Support for the Apple Magic Mouse/Trackpad multi-touch.
527 Say Y here if you want support for the multi-touch features of the
528 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
531 tristate "Mayflash game controller adapter force feedback"
533 select INPUT_FF_MEMLESS
535 Say Y here if you have HJZ Mayflash PS3 game controller adapters
536 and want to enable force feedback support.
539 tristate "Microsoft non-fully HID-compliant devices"
543 Support for Microsoft devices that are not fully compliant with HID standard.
546 tristate "Monterey Genius KB29E keyboard"
550 Support for Monterey Genius KB29E.
552 config HID_MULTITOUCH
553 tristate "HID Multitouch panels"
556 Generic support for HID multitouch panels.
558 Say Y here if you have one of the following devices:
559 - 3M PCT touch screens
560 - ActionStar dual touch panels
562 - Cando dual touch panels
566 - Cypress TrueTouch panels
567 - Elan Microelectronics touch panels
568 - Elo TouchSystems IntelliTouch Plus panels
569 - GeneralTouch 'Sensing Win7-TwoFinger' panels
571 - Hanvon dual touch panels
572 - Ilitek dual touch panels
573 - IrTouch Infrared USB panels
574 - LG Display panels (Dell ST2220Tc)
575 - Lumio CrystalTouch panels
576 - MosArt dual-touch panels
577 - Panasonic multitouch panels
578 - PenMount dual touch panels
579 - Perixx Peripad 701 touchpad
580 - PixArt optical touch screen
581 - Pixcir dual touch panels
583 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
584 - SiS multitouch panels
585 - Stantum multitouch panels
586 - Touch International Panels
588 - Wistron optical touch panels
589 - XAT optical touch panels
590 - Xiroku optical touch panels
591 - Zytronic touch panels
595 To compile this driver as a module, choose M here: the
596 module will be called hid-multitouch.
599 tristate "NTI keyboard adapters"
601 Support for the "extra" Sun keyboard keys on keyboards attached
602 through Network Technologies USB-SUN keyboard adapters.
605 tristate "N-Trig touch screen"
608 Support for N-Trig touch screen.
611 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
614 There are certain devices which have LogicalMaximum wrong in the keyboard
615 usage page of their report descriptor. The most prevailing ones so far
616 are manufactured by Ortek, thus the name of the driver. Currently
617 supported devices by this driver are
621 - Skycable wireless presenter
623 config HID_PANTHERLORD
624 tristate "Pantherlord/GreenAsia game controller"
627 Say Y here if you have a PantherLord/GreenAsia based game controller
630 config PANTHERLORD_FF
631 bool "Pantherlord force feedback support"
632 depends on HID_PANTHERLORD
633 select INPUT_FF_MEMLESS
635 Say Y here if you have a PantherLord/GreenAsia based game controller
636 or adapter and want to enable force feedback support for it.
639 tristate "Penmount touch device"
642 This selects a driver for the PenMount 6000 touch controller.
644 The driver works around a problem in the report descript allowing
645 the userspace to touch events instead of mouse events.
647 Say Y here if you have a Penmount based touch controller.
650 tristate "Petalynx Maxter remote control"
653 Support for Petalynx Maxter remote control.
656 tristate "PicoLCD (graphic version)"
659 This provides support for Minibox PicoLCD devices, currently
660 only the graphical ones are supported.
662 This includes support for the following device features:
664 - Switching between Firmware and Flash mode
665 - EEProm / Flash access (via debugfs)
666 Features selectively enabled:
667 - Framebuffer for monochrome 256x64 display
670 - General purpose outputs
671 Features that are not (yet) supported:
674 config HID_PICOLCD_FB
675 bool "Framebuffer support" if EXPERT
677 depends on HID_PICOLCD
678 depends on HID_PICOLCD=FB || FB=y
679 select FB_DEFERRED_IO
680 select FB_SYS_FILLRECT
681 select FB_SYS_COPYAREA
682 select FB_SYS_IMAGEBLIT
685 Provide access to PicoLCD's 256x64 monochrome display via a
688 config HID_PICOLCD_BACKLIGHT
689 bool "Backlight control" if EXPERT
691 depends on HID_PICOLCD
692 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
694 Provide access to PicoLCD's backlight control via backlight
697 config HID_PICOLCD_LCD
698 bool "Contrast control" if EXPERT
700 depends on HID_PICOLCD
701 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
703 Provide access to PicoLCD's LCD contrast via lcd class.
705 config HID_PICOLCD_LEDS
706 bool "GPO via leds class" if EXPERT
708 depends on HID_PICOLCD
709 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
711 Provide access to PicoLCD's GPO pins via leds class.
713 config HID_PICOLCD_CIR
714 bool "CIR via RC class" if EXPERT
716 depends on HID_PICOLCD
717 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
719 Provide access to PicoLCD's CIR interface via remote control (LIRC).
721 config HID_PLANTRONICS
722 tristate "Plantronics USB HID Driver"
725 Provides HID support for Plantronics USB audio devices.
726 Correctly maps vendor unique volume up/down HID usages to
727 KEY_VOLUMEUP and KEY_VOLUMEDOWN events and prevents core mapping
728 of other vendor unique HID usages to random mouse events.
730 Say M here if you may ever plug in a Plantronics USB audio device.
733 tristate "Primax non-fully HID-compliant devices"
736 Support for Primax devices that are not fully compliant with the
740 tristate "Roccat device support"
743 Support for Roccat devices.
744 Say Y here if you have a Roccat mouse or keyboard and want
745 support for its special functionalities.
748 tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
751 Support for Saitek devices that are not fully compliant with the
755 - PS1000 Dual Analog Pad
756 - Saitek R.A.T.7, R.A.T.9, M.M.O.7 Gaming Mice
757 - Mad Catz R.A.T.5, R.A.T.9 Gaming Mice
760 tristate "Samsung InfraRed remote control or keyboards"
763 Support for Samsung InfraRed remote control or keyboards.
766 tristate "Sony PS2/3/4 accessories"
769 depends on LEDS_CLASS
774 * Sony PS3 6-axis controllers
775 * Sony PS4 DualShock 4 controllers
777 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
778 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
781 bool "Sony PS2/3/4 accessories force feedback support"
783 select INPUT_FF_MEMLESS
785 Say Y here if you have a Sony PS2/3/4 accessory and want to enable
786 force feedback support for it.
789 tristate "Speedlink VAD Cezanne mouse support"
792 Support for Speedlink Vicious and Divine Cezanne mouse.
794 config HID_STEELSERIES
795 tristate "Steelseries SRW-S1 steering wheel support"
798 Support for Steelseries SRW-S1 steering wheel
801 tristate "Sunplus wireless desktop"
804 Support for Sunplus wireless desktop.
807 tristate "Synaptics RMI4 device support"
815 Support for Synaptics RMI4 touchpads.
816 Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
817 and want support for its special functionalities.
820 tristate "GreenAsia (Product ID 0x12) game controller support"
823 Say Y here if you have a GreenAsia (Product ID 0x12) based game
824 controller or adapter.
827 bool "GreenAsia (Product ID 0x12) force feedback support"
828 depends on HID_GREENASIA
829 select INPUT_FF_MEMLESS
831 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
832 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
833 and want to enable force feedback support for it.
835 config HID_HYPERV_MOUSE
836 tristate "Microsoft Hyper-V mouse driver"
839 Select this option to enable the Hyper-V mouse driver.
841 config HID_SMARTJOYPLUS
842 tristate "SmartJoy PLUS PS2/USB adapter support"
845 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
846 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
848 Note that DDR (Dance Dance Revolution) mode is not supported, nor
849 is pressure sensitive buttons on the pro models.
851 config SMARTJOYPLUS_FF
852 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
853 depends on HID_SMARTJOYPLUS
854 select INPUT_FF_MEMLESS
856 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
857 enable force feedback support for it.
860 tristate "TiVo Slide Bluetooth remote control support"
863 Say Y if you have a TiVo Slide Bluetooth remote control.
866 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
869 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
870 CLLRCMCE remote control.
873 tristate "ThingM blink(1) USB RGB LED"
875 depends on LEDS_CLASS
878 Support for the ThingM blink(1) USB RGB LED. This driver has been
879 merged into the generic hid led driver. Config symbol HID_THINGM
880 just selects HID_LED and will be removed soon.
882 config HID_THRUSTMASTER
883 tristate "ThrustMaster devices support"
886 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
887 a THRUSTMASTER Ferrari GT Rumble Wheel.
889 config THRUSTMASTER_FF
890 bool "ThrustMaster devices force feedback support"
891 depends on HID_THRUSTMASTER
892 select INPUT_FF_MEMLESS
894 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
895 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
896 Rumble Force or Force Feedback Wheel.
899 tristate "THQ PS3 uDraw tablet"
902 Say Y here if you want to use the THQ uDraw gaming tablet for
906 tristate "Wacom Intuos/Graphire tablet support (USB)"
913 Say Y here if you want to use the USB or BT version of the Wacom Intuos
916 To compile this driver as a module, choose M here: the
917 module will be called wacom.
920 tristate "Nintendo Wii / Wii U peripherals"
922 depends on LEDS_CLASS
924 select INPUT_FF_MEMLESS
926 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
927 devices are the Wii Remote and its extension devices, but also devices
928 based on the Wii Remote like the Wii U Pro Controller or the
931 Support for all official Nintendo extensions is available, however, 3rd
932 party extensions might not be supported. Please report these devices to:
933 http://github.com/dvdhrm/xwiimote/issues
935 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
936 the Wii U Gamepad) might be supported in the future. But currently
937 support is limited to Bluetooth based devices.
941 To compile this driver as a module, choose M here: the
942 module will be called hid-wiimote.
945 tristate "Xin-Mo non-fully compliant devices"
948 Support for Xin-Mo devices that are not fully compliant with the HID
949 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
950 if you have a Xin-Mo Dual Arcade controller.
953 tristate "Zeroplus based game controller support"
956 Say Y here if you have a Zeroplus based game controller.
959 bool "Zeroplus based game controller force feedback support"
960 depends on HID_ZEROPLUS
961 select INPUT_FF_MEMLESS
963 Say Y here if you have a Zeroplus based game controller and want
964 to have force feedback support for it.
967 tristate "Zydacron remote control support"
970 Support for Zydacron remote control.
972 config HID_SENSOR_HUB
973 tristate "HID Sensors framework support"
974 depends on HID && HAS_IOMEM
978 Support for HID Sensor framework. This creates a MFD instance
979 for a sensor hub and identifies all the sensors connected to it.
980 Each sensor is registered as a MFD cell, so that sensor specific
981 processing can be done in a separate driver. Each sensor
982 drivers can use the service provided by this driver to register
983 for events and handle data streams. Each sensor driver can format
984 data and present to user mode using input or IIO interface.
986 config HID_SENSOR_CUSTOM_SENSOR
987 tristate "HID Sensors hub custom sensor support"
988 depends on HID_SENSOR_HUB
991 HID Sensor hub specification allows definition of some custom and
992 generic sensors. Unlike other HID sensors, they can't be exported
993 via Linux IIO because of custom fields. This is up to the manufacturer
994 to decide how to interpret these special sensor ids and process in
995 the user space. Currently some manufacturers are using these ids for
996 sensor calibration and debugging other sensors. Manufacturers
997 should't use these special custom sensor ids to export any of the
999 Select this config option for custom/generic sensor support.
1002 tristate "Alps HID device support"
1005 Support for Alps I2C HID touchpads and StickPointer.
1006 Say Y here if you have a Alps touchpads over i2c-hid or usbhid
1007 and want support for its special functionalities.
1013 source "drivers/hid/usbhid/Kconfig"
1015 source "drivers/hid/i2c-hid/Kconfig"
1017 source "drivers/hid/intel-ish-hid/Kconfig"