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.
141 Support for Asus notebook built-in keyboard via i2c.
151 Support for Aureal Cy se W-01RN Remote Controller and other Aureal derived remotes.
154 tristate "Belkin Flip KVM and Wireless keyboard"
158 Support for Belkin Flip KVM and Wireless keyboard.
161 tristate "Betop Production Inc. force feedback support"
163 select INPUT_FF_MEMLESS
165 Say Y here if you want to enable force feedback support for devices by
166 BETOP Production Ltd.
167 Currently the following devices are known to be supported:
168 - BETOP 2185 PC & BFM MODE
171 tristate "Cherry Cymotion keyboard"
175 Support for Cherry Cymotion keyboard.
178 tristate "Chicony Tactical pad"
182 Support for Chicony Tactical pad.
185 tristate "Corsair devices"
186 depends on HID && USB && LEDS_CLASS
188 Support for Corsair devices that are not fully compliant with the
195 tristate "Prodikeys PC-MIDI Keyboard support"
196 depends on HID && SND
199 Support for Prodikeys PC-MIDI Keyboard device support.
200 Say Y here to enable support for this device.
201 - Prodikeys PC-MIDI keyboard.
202 The Prodikeys PC-MIDI acts as a USB Audio device, with one MIDI
203 input and one MIDI output. These MIDI jacks appear as
204 a sound "card" in the ALSA sound system.
205 Note: if you say N here, this device will still function as a basic
206 multimedia keyboard, but will lack support for the musical keyboard
207 and some additional multimedia keys.
210 tristate "CMedia CM6533 HID audio jack controls"
213 Support for CMedia CM6533 HID audio jack controls.
216 tristate "Silicon Labs CP2112 HID USB-to-SMBus Bridge support"
217 depends on USB_HID && I2C && GPIOLIB
219 Support for Silicon Labs CP2112 HID USB to SMBus Master Bridge.
220 This is a HID device driver which registers as an i2c adapter
221 and gpiochip to expose these functions of the CP2112. The
222 customizable USB descriptor fields are exposed as sysfs attributes.
225 tristate "Cypress mouse and barcode readers"
229 Support for cypress mouse and barcode readers.
231 config HID_DRAGONRISE
232 tristate "DragonRise Inc. game controller"
235 Say Y here if you have DragonRise Inc. game controllers.
236 These might be branded as:
238 - Media-tech MT1504 "Rogue"
240 - Defender Game Master
243 bool "DragonRise Inc. force feedback"
244 depends on HID_DRAGONRISE
245 select INPUT_FF_MEMLESS
247 Say Y here if you want to enable force feedback support for DragonRise Inc.
251 tristate "EMS Production Inc. force feedback support"
253 select INPUT_FF_MEMLESS
255 Say Y here if you want to enable force feedback support for devices by
257 Currently the following devices are known to be supported:
258 - Trio Linker Plus II
261 tristate "ELECOM BM084 bluetooth mouse"
264 Support for the ELECOM BM084 (bluetooth mouse).
267 tristate "ELO USB 4000/4500 touchscreen"
270 Support for the ELO USB 4000/4500 touchscreens. Note that this is for
271 different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
274 tristate "Ezkey BTC 8193 keyboard"
278 Support for Ezkey BTC 8193 keyboard.
281 tristate "Gembird Joypad"
284 Support for Gembird JPD-DualForce 2.
287 tristate "Google Fiber TV Box remote control support"
290 Support for Google Fiber TV Box remote controls
293 tristate "Holtek HID devices"
296 Support for Holtek based devices:
297 - Holtek On Line Grip based game controller
298 - Trust GXT 18 Gaming Keyboard
299 - Sharkoon Drakonia / Perixx MX-2000 gaming mice
300 - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
302 - SHARKOON DarkGlider Gaming mouse
303 - LEETGION Hellion Gaming Mouse
306 bool "Holtek On Line Grip force feedback support"
307 depends on HID_HOLTEK
308 select INPUT_FF_MEMLESS
310 Say Y here if you have a Holtek On Line Grip based game controller
311 and want to have force feedback support for it.
314 tristate "MSI GT68xR LED support"
315 depends on LEDS_CLASS && USB_HID
317 Say Y here if you want to enable support for the three MSI GT68xR LEDs
319 This driver support following modes:
320 - Normal: LEDs are fully on when enabled
321 - Audio: LEDs brightness depends on sound level
322 - Breathing: LEDs brightness varies at human breathing rate
324 Currently the following devices are know to be supported:
328 tristate "Keytouch HID devices"
331 Support for Keytouch HID devices not fully compliant with
332 the specification. Currently supported:
336 tristate "KYE/Genius devices"
339 Support for KYE/Genius devices not fully compliant with HID standard:
341 - EasyPen i405X tablet
342 - MousePen i608X tablet
343 - EasyPen M610X tablet
349 Support for UC-Logic and Huion tablets.
355 Support for Waltop tablets.
358 tristate "Gyration remote control"
361 Support for Gyration remote control.
364 tristate "ION iCade arcade controller"
367 Support for the ION iCade arcade controller to work as a joystick.
369 To compile this driver as a module, choose M here: the
370 module will be called hid-icade.
373 tristate "Twinhan IR remote control"
376 Support for Twinhan IR remote control.
378 config HID_KENSINGTON
379 tristate "Kensington Slimblade Trackball"
383 Support for Kensington Slimblade Trackball.
389 Support for LC-Power RC1000MCE RF remote control.
392 tristate "Simple RGB LED support"
394 depends on LEDS_CLASS
396 Support for simple RGB LED devices. Currently supported are:
397 - Riso Kagaku Webmail Notifier
398 - Dream Cheeky Webmail Notifier and Friends Alert
401 To compile this driver as a module, choose M here: the
402 module will be called hid-led.
405 tristate "Lenovo / Thinkpad devices"
410 Support for Lenovo devices that are not fully compliant with HID standard.
412 Say Y if you want support for the non-compliant features of the Lenovo
413 Thinkpad standalone keyboards, e.g:
414 - ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
416 - ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
417 - ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
420 tristate "Logitech devices"
424 Support for Logitech devices that are not fully compliant with HID standard.
426 config HID_LOGITECH_DJ
427 tristate "Logitech Unifying receivers full support"
429 depends on HID_LOGITECH
430 select HID_LOGITECH_HIDPP
432 Say Y if you want support for Logitech Unifying receivers and devices.
433 Unifying receivers are capable of pairing up to 6 Logitech compliant
434 devices to the same receiver. Without this driver it will be handled by
435 generic USB_HID driver and all incoming events will be multiplexed
436 into a single mouse and a single keyboard device.
438 config HID_LOGITECH_HIDPP
439 tristate "Logitech HID++ devices support"
440 depends on HID_LOGITECH
442 Support for Logitech devices relyingon the HID++ Logitech specification
444 Say Y if you want support for Logitech devices relying on the HID++
445 specification. Such devices are the various Logitech Touchpads (T650,
446 T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
450 bool "Logitech force feedback support"
451 depends on HID_LOGITECH
452 select INPUT_FF_MEMLESS
454 Say Y here if you have one of these devices:
455 - Logitech WingMan Cordless RumblePad
456 - Logitech WingMan Cordless RumblePad 2
457 - Logitech WingMan Force 3D
458 - Logitech Formula Force EX
459 - Logitech WingMan Formula Force GP
461 and if you want to enable force feedback for them.
462 Note: if you say N here, this device will still be supported, but without
465 config LOGIRUMBLEPAD2_FF
466 bool "Logitech force feedback support (variant 2)"
467 depends on HID_LOGITECH
468 select INPUT_FF_MEMLESS
470 Say Y here if you want to enable force feedback support for:
472 - Logitech Rumblepad 2
473 - Logitech Formula Vibration Feedback Wheel
476 bool "Logitech Flight System G940 force feedback support"
477 depends on HID_LOGITECH
478 select INPUT_FF_MEMLESS
480 Say Y here if you want to enable force feedback support for Logitech
481 Flight System G940 devices.
484 bool "Logitech wheels configuration and force feedback support"
485 depends on HID_LOGITECH
486 select INPUT_FF_MEMLESS
489 Say Y here if you want to enable force feedback and range setting
490 support for following Logitech wheels:
491 - Logitech Driving Force
492 - Logitech Driving Force Pro
493 - Logitech Driving Force GT
496 - Logitech MOMO/MOMO 2
497 - Logitech Formula Force EX
499 config HID_MAGICMOUSE
500 tristate "Apple Magic Mouse/Trackpad multi-touch support"
503 Support for the Apple Magic Mouse/Trackpad multi-touch.
505 Say Y here if you want support for the multi-touch features of the
506 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
509 tristate "Microsoft non-fully HID-compliant devices"
513 Support for Microsoft devices that are not fully compliant with HID standard.
516 tristate "Monterey Genius KB29E keyboard"
520 Support for Monterey Genius KB29E.
522 config HID_MULTITOUCH
523 tristate "HID Multitouch panels"
526 Generic support for HID multitouch panels.
528 Say Y here if you have one of the following devices:
529 - 3M PCT touch screens
530 - ActionStar dual touch panels
532 - Cando dual touch panels
536 - Cypress TrueTouch panels
537 - Elan Microelectronics touch panels
538 - Elo TouchSystems IntelliTouch Plus panels
539 - GeneralTouch 'Sensing Win7-TwoFinger' panels
541 - Hanvon dual touch panels
542 - Ilitek dual touch panels
543 - IrTouch Infrared USB panels
544 - LG Display panels (Dell ST2220Tc)
545 - Lumio CrystalTouch panels
546 - MosArt dual-touch panels
547 - Panasonic multitouch panels
548 - PenMount dual touch panels
549 - Perixx Peripad 701 touchpad
550 - PixArt optical touch screen
551 - Pixcir dual touch panels
553 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
554 - SiS multitouch panels
555 - Stantum multitouch panels
556 - Touch International Panels
558 - Wistron optical touch panels
559 - XAT optical touch panels
560 - Xiroku optical touch panels
561 - Zytronic touch panels
565 To compile this driver as a module, choose M here: the
566 module will be called hid-multitouch.
569 tristate "N-Trig touch screen"
572 Support for N-Trig touch screen.
575 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
578 There are certain devices which have LogicalMaximum wrong in the keyboard
579 usage page of their report descriptor. The most prevailing ones so far
580 are manufactured by Ortek, thus the name of the driver. Currently
581 supported devices by this driver are
585 - Skycable wireless presenter
587 config HID_PANTHERLORD
588 tristate "Pantherlord/GreenAsia game controller"
591 Say Y here if you have a PantherLord/GreenAsia based game controller
594 config PANTHERLORD_FF
595 bool "Pantherlord force feedback support"
596 depends on HID_PANTHERLORD
597 select INPUT_FF_MEMLESS
599 Say Y here if you have a PantherLord/GreenAsia based game controller
600 or adapter and want to enable force feedback support for it.
603 tristate "Penmount touch device"
606 This selects a driver for the PenMount 6000 touch controller.
608 The driver works around a problem in the report descript allowing
609 the userspace to touch events instead of mouse events.
611 Say Y here if you have a Penmount based touch controller.
614 tristate "Petalynx Maxter remote control"
617 Support for Petalynx Maxter remote control.
620 tristate "PicoLCD (graphic version)"
623 This provides support for Minibox PicoLCD devices, currently
624 only the graphical ones are supported.
626 This includes support for the following device features:
628 - Switching between Firmware and Flash mode
629 - EEProm / Flash access (via debugfs)
630 Features selectively enabled:
631 - Framebuffer for monochrome 256x64 display
634 - General purpose outputs
635 Features that are not (yet) supported:
638 config HID_PICOLCD_FB
639 bool "Framebuffer support" if EXPERT
641 depends on HID_PICOLCD
642 depends on HID_PICOLCD=FB || FB=y
643 select FB_DEFERRED_IO
644 select FB_SYS_FILLRECT
645 select FB_SYS_COPYAREA
646 select FB_SYS_IMAGEBLIT
649 Provide access to PicoLCD's 256x64 monochrome display via a
652 config HID_PICOLCD_BACKLIGHT
653 bool "Backlight control" if EXPERT
655 depends on HID_PICOLCD
656 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
658 Provide access to PicoLCD's backlight control via backlight
661 config HID_PICOLCD_LCD
662 bool "Contrast control" if EXPERT
664 depends on HID_PICOLCD
665 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
667 Provide access to PicoLCD's LCD contrast via lcd class.
669 config HID_PICOLCD_LEDS
670 bool "GPO via leds class" if EXPERT
672 depends on HID_PICOLCD
673 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
675 Provide access to PicoLCD's GPO pins via leds class.
677 config HID_PICOLCD_CIR
678 bool "CIR via RC class" if EXPERT
680 depends on HID_PICOLCD
681 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
683 Provide access to PicoLCD's CIR interface via remote control (LIRC).
685 config HID_PLANTRONICS
686 tristate "Plantronics USB HID Driver"
689 Provides HID support for Plantronics USB audio devices.
690 Correctly maps vendor unique volume up/down HID usages to
691 KEY_VOLUMEUP and KEY_VOLUMEDOWN events and prevents core mapping
692 of other vendor unique HID usages to random mouse events.
694 Say M here if you may ever plug in a Plantronics USB audio device.
697 tristate "Primax non-fully HID-compliant devices"
700 Support for Primax devices that are not fully compliant with the
704 tristate "Roccat device support"
707 Support for Roccat devices.
708 Say Y here if you have a Roccat mouse or keyboard and want
709 support for its special functionalities.
712 tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
715 Support for Saitek devices that are not fully compliant with the
719 - PS1000 Dual Analog Pad
720 - Saitek R.A.T.7, R.A.T.9, M.M.O.7 Gaming Mice
721 - Mad Catz R.A.T.5, R.A.T.9 Gaming Mice
724 tristate "Samsung InfraRed remote control or keyboards"
727 Support for Samsung InfraRed remote control or keyboards.
730 tristate "Sony PS2/3/4 accessories"
733 depends on LEDS_CLASS
738 * Sony PS3 6-axis controllers
739 * Sony PS4 DualShock 4 controllers
741 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
742 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
745 bool "Sony PS2/3/4 accessories force feedback support"
747 select INPUT_FF_MEMLESS
749 Say Y here if you have a Sony PS2/3/4 accessory and want to enable
750 force feedback support for it.
753 tristate "Speedlink VAD Cezanne mouse support"
756 Support for Speedlink Vicious and Divine Cezanne mouse.
758 config HID_STEELSERIES
759 tristate "Steelseries SRW-S1 steering wheel support"
762 Support for Steelseries SRW-S1 steering wheel
765 tristate "Sunplus wireless desktop"
768 Support for Sunplus wireless desktop.
771 tristate "Synaptics RMI4 device support"
774 Support for Synaptics RMI4 touchpads.
775 Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
776 and want support for its special functionalities.
779 tristate "GreenAsia (Product ID 0x12) game controller support"
782 Say Y here if you have a GreenAsia (Product ID 0x12) based game
783 controller or adapter.
786 bool "GreenAsia (Product ID 0x12) force feedback support"
787 depends on HID_GREENASIA
788 select INPUT_FF_MEMLESS
790 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
791 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
792 and want to enable force feedback support for it.
794 config HID_HYPERV_MOUSE
795 tristate "Microsoft Hyper-V mouse driver"
798 Select this option to enable the Hyper-V mouse driver.
800 config HID_SMARTJOYPLUS
801 tristate "SmartJoy PLUS PS2/USB adapter support"
804 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
805 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
807 Note that DDR (Dance Dance Revolution) mode is not supported, nor
808 is pressure sensitive buttons on the pro models.
810 config SMARTJOYPLUS_FF
811 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
812 depends on HID_SMARTJOYPLUS
813 select INPUT_FF_MEMLESS
815 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
816 enable force feedback support for it.
819 tristate "TiVo Slide Bluetooth remote control support"
822 Say Y if you have a TiVo Slide Bluetooth remote control.
825 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
828 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
829 CLLRCMCE remote control.
832 tristate "ThingM blink(1) USB RGB LED"
834 depends on LEDS_CLASS
837 Support for the ThingM blink(1) USB RGB LED. This driver has been
838 merged into the generic hid led driver. Config symbol HID_THINGM
839 just selects HID_LED and will be removed soon.
841 config HID_THRUSTMASTER
842 tristate "ThrustMaster devices support"
845 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
846 a THRUSTMASTER Ferrari GT Rumble Wheel.
848 config THRUSTMASTER_FF
849 bool "ThrustMaster devices force feedback support"
850 depends on HID_THRUSTMASTER
851 select INPUT_FF_MEMLESS
853 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
854 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
855 Rumble Force or Force Feedback Wheel.
858 tristate "Wacom Intuos/Graphire tablet support (USB)"
864 Say Y here if you want to use the USB or BT version of the Wacom Intuos
867 To compile this driver as a module, choose M here: the
868 module will be called wacom.
871 tristate "Nintendo Wii / Wii U peripherals"
873 depends on LEDS_CLASS
875 select INPUT_FF_MEMLESS
877 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
878 devices are the Wii Remote and its extension devices, but also devices
879 based on the Wii Remote like the Wii U Pro Controller or the
882 Support for all official Nintendo extensions is available, however, 3rd
883 party extensions might not be supported. Please report these devices to:
884 http://github.com/dvdhrm/xwiimote/issues
886 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
887 the Wii U Gamepad) might be supported in the future. But currently
888 support is limited to Bluetooth based devices.
892 To compile this driver as a module, choose M here: the
893 module will be called hid-wiimote.
896 tristate "Xin-Mo non-fully compliant devices"
899 Support for Xin-Mo devices that are not fully compliant with the HID
900 standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
901 if you have a Xin-Mo Dual Arcade controller.
904 tristate "Zeroplus based game controller support"
907 Say Y here if you have a Zeroplus based game controller.
910 bool "Zeroplus based game controller force feedback support"
911 depends on HID_ZEROPLUS
912 select INPUT_FF_MEMLESS
914 Say Y here if you have a Zeroplus based game controller and want
915 to have force feedback support for it.
918 tristate "Zydacron remote control support"
921 Support for Zydacron remote control.
923 config HID_SENSOR_HUB
924 tristate "HID Sensors framework support"
925 depends on HID && HAS_IOMEM
929 Support for HID Sensor framework. This creates a MFD instance
930 for a sensor hub and identifies all the sensors connected to it.
931 Each sensor is registered as a MFD cell, so that sensor specific
932 processing can be done in a separate driver. Each sensor
933 drivers can use the service provided by this driver to register
934 for events and handle data streams. Each sensor driver can format
935 data and present to user mode using input or IIO interface.
937 config HID_SENSOR_CUSTOM_SENSOR
938 tristate "HID Sensors hub custom sensor support"
939 depends on HID_SENSOR_HUB
942 HID Sensor hub specification allows definition of some custom and
943 generic sensors. Unlike other HID sensors, they can't be exported
944 via Linux IIO because of custom fields. This is up to the manufacturer
945 to decide how to interpret these special sensor ids and process in
946 the user space. Currently some manufacturers are using these ids for
947 sensor calibration and debugging other sensors. Manufacturers
948 should't use these special custom sensor ids to export any of the
950 Select this config option for custom/generic sensor support.
956 source "drivers/hid/usbhid/Kconfig"
958 source "drivers/hid/i2c-hid/Kconfig"