xref: /linux/drivers/hid/Kconfig (revision d257f9bf06129613de539ea71ecea60848b662cd)
1#
2# HID driver configuration
3#
4menu "HID support"
5     depends on INPUT
6
7config HID
8	tristate "HID bus support"
9	depends on INPUT
10	default y
11	---help---
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).
21
22	  For docs and specs, see http://www.usb.org/developers/hidpage/
23
24	  If unsure, say Y.
25
26if HID
27
28config HID_BATTERY_STRENGTH
29	bool "Battery level reporting for HID devices"
30	depends on HID
31	select POWER_SUPPLY
32	default n
33	---help---
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.
37
38config HIDRAW
39	bool "/dev/hidraw raw HID device support"
40	depends on HID
41	---help---
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.
45
46	This module supports these devices separately using a separate
47	event interface on /dev/hidraw.
48
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.
54
55	If unsure, say Y.
56
57config UHID
58	tristate "User-space I/O driver support for HID subsystem"
59	depends on HID
60	default n
61	---help---
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
66	user-space device.
67
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.
72
73	If unsure, say N.
74
75	To compile this driver as a module, choose M here: the
76	module will be called uhid.
77
78config HID_GENERIC
79	tristate "Generic HID driver"
80	depends on HID
81	default HID
82	---help---
83	Support for generic devices on the HID bus. This includes most
84	keyboards and mice, joysticks, tablets and digitizers.
85
86	To compile this driver as a module, choose M here: the module
87	will be called hid-generic.
88
89	If unsure, say Y.
90
91menu "Special HID drivers"
92	depends on HID
93
94config HID_A4TECH
95	tristate "A4 tech mice"
96	depends on HID
97	default !EXPERT
98	---help---
99	Support for A4 tech X5 and WOP-35 / Trust 450L mice.
100
101config HID_ACCUTOUCH
102	tristate "Accutouch touch device"
103	depends on USB_HID
104	---help---
105	  This selects a driver for the Accutouch 2216 touch controller.
106
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
109          a touchscreen.
110
111	  Say Y here if you have a Accutouch 2216 touch controller.
112
113config HID_ACRUX
114	tristate "ACRUX game controller support"
115	depends on HID
116	---help---
117	Say Y here if you want to enable support for ACRUX game controllers.
118
119config HID_ACRUX_FF
120	bool "ACRUX force feedback support"
121	depends on HID_ACRUX
122	select INPUT_FF_MEMLESS
123	---help---
124	Say Y here if you want to enable force feedback support for ACRUX
125	game controllers.
126
127config HID_APPLE
128	tristate "Apple {i,Power,Mac}Books"
129	depends on HID
130	default !EXPERT
131	---help---
132	Support for some Apple devices which less or more break
133	HID specification.
134
135	Say Y here if you want support for keyboards of	Apple iBooks, PowerBooks,
136	MacBooks, MacBook Pros and Apple Aluminum.
137
138config HID_APPLEIR
139	tristate "Apple infrared receiver"
140	depends on (USB_HID)
141	---help---
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.
146
147	Say Y here if you want support for Apple infrared remote control.
148
149config HID_ASUS
150	tristate "Asus"
151	depends on LEDS_CLASS
152	---help---
153	Support for Asus notebook built-in keyboard and touchpad via i2c, and
154	the Asus Republic of Gamers laptop keyboard special keys.
155
156	Supported devices:
157	- EeeBook X205TA
158	- VivoBook E200HA
159	- GL553V series
160	- GL753V series
161
162config HID_AUREAL
163	tristate "Aureal"
164	depends on HID
165	---help---
166	Support for Aureal Cy se W-01RN Remote Controller and other Aureal derived remotes.
167
168config HID_BELKIN
169	tristate "Belkin Flip KVM and Wireless keyboard"
170	depends on HID
171	default !EXPERT
172	---help---
173	Support for Belkin Flip KVM and Wireless keyboard.
174
175config HID_BETOP_FF
176	tristate "Betop Production Inc. force feedback support"
177	depends on USB_HID
178	select INPUT_FF_MEMLESS
179	---help---
180	Say Y here if you want to enable force feedback support for devices by
181	BETOP Production Ltd.
182	Currently the following devices are known to be supported:
183	 - BETOP 2185 PC & BFM MODE
184
185config HID_CHERRY
186	tristate "Cherry Cymotion keyboard"
187	depends on HID
188	default !EXPERT
189	---help---
190	Support for Cherry Cymotion keyboard.
191
192config HID_CHICONY
193	tristate "Chicony devices"
194	depends on HID
195	default !EXPERT
196	---help---
197	Support for Chicony Tactical pad and special keys on Chicony keyboards.
198
199config HID_CORSAIR
200	tristate "Corsair devices"
201	depends on HID && USB && LEDS_CLASS
202	---help---
203	Support for Corsair devices that are not fully compliant with the
204	HID standard.
205
206	Supported devices:
207	- Vengeance K90
208	- Scimitar PRO RGB
209
210config HID_PRODIKEYS
211	tristate "Prodikeys PC-MIDI Keyboard support"
212	depends on HID && SND
213	select SND_RAWMIDI
214	---help---
215	Support for Prodikeys PC-MIDI Keyboard device support.
216	Say Y here to enable support for this device.
217	- Prodikeys PC-MIDI keyboard.
218	  The Prodikeys PC-MIDI acts as a USB Audio device, with one MIDI
219	  input and one MIDI output. These MIDI jacks appear as
220	  a sound "card" in the ALSA sound system.
221	  Note: if you say N here, this device will still function as a basic
222	  multimedia keyboard, but will lack support for the musical keyboard
223	  and some additional multimedia keys.
224
225config HID_CMEDIA
226	tristate "CMedia CM6533 HID audio jack controls"
227	depends on HID
228	---help---
229	Support for CMedia CM6533 HID audio jack controls.
230
231config HID_CP2112
232	tristate "Silicon Labs CP2112 HID USB-to-SMBus Bridge support"
233	depends on USB_HID && I2C && GPIOLIB
234	select GPIOLIB_IRQCHIP
235	---help---
236	Support for Silicon Labs CP2112 HID USB to SMBus Master Bridge.
237	This is a HID device driver which registers as an i2c adapter
238	and gpiochip to expose these functions of the CP2112. The
239	customizable USB descriptor fields are exposed as sysfs attributes.
240
241config HID_CYPRESS
242	tristate "Cypress mouse and barcode readers"
243	depends on HID
244	default !EXPERT
245	---help---
246	Support for cypress mouse and barcode readers.
247
248config HID_DRAGONRISE
249	tristate "DragonRise Inc. game controller"
250	depends on HID
251	---help---
252	Say Y here if you have DragonRise Inc. game controllers.
253	These might be branded as:
254	- Tesun USB-703
255	- Media-tech MT1504 "Rogue"
256	- DVTech JS19 "Gear"
257	- Defender Game Master
258
259config DRAGONRISE_FF
260	bool "DragonRise Inc. force feedback"
261	depends on HID_DRAGONRISE
262	select INPUT_FF_MEMLESS
263	---help---
264	Say Y here if you want to enable force feedback support for DragonRise Inc.
265	game controllers.
266
267config HID_EMS_FF
268	tristate "EMS Production Inc. force feedback support"
269	depends on HID
270	select INPUT_FF_MEMLESS
271	---help---
272	Say Y here if you want to enable force feedback support for devices by
273	EMS Production Ltd.
274	Currently the following devices are known to be supported:
275	 - Trio Linker Plus II
276
277config HID_ELECOM
278	tristate "ELECOM HID devices"
279	depends on HID
280	---help---
281	Support for ELECOM devices:
282	  - BM084 Bluetooth Mouse
283	  - DEFT Trackball (Wired and wireless)
284
285config HID_ELO
286	tristate "ELO USB 4000/4500 touchscreen"
287	depends on USB_HID
288	---help---
289	Support for the ELO USB 4000/4500 touchscreens. Note that this is for
290	different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
291
292config HID_EZKEY
293	tristate "Ezkey BTC 8193 keyboard"
294	depends on HID
295	default !EXPERT
296	---help---
297	Support for Ezkey BTC 8193 keyboard.
298
299config HID_GEMBIRD
300	tristate "Gembird Joypad"
301	depends on HID
302	---help---
303	Support for Gembird JPD-DualForce 2.
304
305config HID_GFRM
306	tristate "Google Fiber TV Box remote control support"
307	depends on HID
308	---help---
309	Support for Google Fiber TV Box remote controls
310
311config HID_HOLTEK
312	tristate "Holtek HID devices"
313	depends on USB_HID
314	---help---
315	Support for Holtek based devices:
316	  - Holtek On Line Grip based game controller
317	  - Trust GXT 18 Gaming Keyboard
318	  - Sharkoon Drakonia / Perixx MX-2000 gaming mice
319	  - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
320	    Zalman ZM-GM1
321	  - SHARKOON DarkGlider Gaming mouse
322	  - LEETGION Hellion Gaming Mouse
323
324config HOLTEK_FF
325	bool "Holtek On Line Grip force feedback support"
326	depends on HID_HOLTEK
327	select INPUT_FF_MEMLESS
328	---help---
329	  Say Y here if you have a Holtek On Line Grip based game controller
330	  and want to have force feedback support for it.
331
332config HID_GT683R
333	tristate "MSI GT68xR LED support"
334	depends on LEDS_CLASS && USB_HID
335	---help---
336	Say Y here if you want to enable support for the three MSI GT68xR LEDs
337
338	This driver support following modes:
339	  - Normal: LEDs are fully on when enabled
340	  - Audio:  LEDs brightness depends on sound level
341	  - Breathing: LEDs brightness varies at human breathing rate
342
343	Currently the following devices are know to be supported:
344	  - MSI GT683R
345
346config HID_KEYTOUCH
347	tristate "Keytouch HID devices"
348	depends on HID
349	---help---
350	Support for Keytouch HID devices not fully compliant with
351	the specification. Currently supported:
352		- Keytouch IEC 60945
353
354config HID_KYE
355	tristate "KYE/Genius devices"
356	depends on HID
357	---help---
358	Support for KYE/Genius devices not fully compliant with HID standard:
359	- Ergo Mouse
360	- EasyPen i405X tablet
361	- MousePen i608X tablet
362	- EasyPen M610X tablet
363
364config HID_UCLOGIC
365	tristate "UC-Logic"
366	depends on USB_HID
367	---help---
368	Support for UC-Logic and Huion tablets.
369
370config HID_WALTOP
371	tristate "Waltop"
372	depends on HID
373	---help---
374	Support for Waltop tablets.
375
376config HID_GYRATION
377	tristate "Gyration remote control"
378	depends on HID
379	---help---
380	Support for Gyration remote control.
381
382config HID_ICADE
383	tristate "ION iCade arcade controller"
384	depends on HID
385	---help---
386	Support for the ION iCade arcade controller to work as a joystick.
387
388	To compile this driver as a module, choose M here: the
389	module will be called hid-icade.
390
391config HID_ITE
392	tristate "ITE devices"
393	depends on HID
394	default !EXPERT
395	---help---
396	Support for ITE devices not fully compliant with HID standard.
397
398config HID_TWINHAN
399	tristate "Twinhan IR remote control"
400	depends on HID
401	---help---
402	Support for Twinhan IR remote control.
403
404config HID_KENSINGTON
405	tristate "Kensington Slimblade Trackball"
406	depends on HID
407	default !EXPERT
408	---help---
409	Support for Kensington Slimblade Trackball.
410
411config HID_LCPOWER
412	tristate "LC-Power"
413	depends on HID
414	---help---
415	Support for LC-Power RC1000MCE RF remote control.
416
417config HID_LED
418	tristate "Simple RGB LED support"
419	depends on HID
420	depends on LEDS_CLASS
421	---help---
422	Support for simple RGB LED devices. Currently supported are:
423	- Riso Kagaku Webmail Notifier
424	- Dream Cheeky Webmail Notifier and Friends Alert
425	- ThingM blink(1)
426	- Delcom Visual Signal Indicator Generation 2
427	- Greynut Luxafor
428
429	To compile this driver as a module, choose M here: the
430	module will be called hid-led.
431
432config HID_LENOVO
433	tristate "Lenovo / Thinkpad devices"
434	depends on HID
435	select NEW_LEDS
436	select LEDS_CLASS
437	---help---
438	Support for Lenovo devices that are not fully compliant with HID standard.
439
440	Say Y if you want support for the non-compliant features of the Lenovo
441	Thinkpad standalone keyboards, e.g:
442	- ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
443	  configuration)
444	- ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
445	- ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
446
447config HID_LOGITECH
448	tristate "Logitech devices"
449	depends on HID
450	default !EXPERT
451	---help---
452	Support for Logitech devices that are not fully compliant with HID standard.
453
454config HID_LOGITECH_DJ
455	tristate "Logitech Unifying receivers full support"
456	depends on HIDRAW
457	depends on HID_LOGITECH
458	select HID_LOGITECH_HIDPP
459	---help---
460	Say Y if you want support for Logitech Unifying receivers and devices.
461	Unifying receivers are capable of pairing up to 6 Logitech compliant
462	devices to the same receiver. Without this driver it will be handled by
463	generic USB_HID driver and all incoming events will be multiplexed
464	into a single mouse and a single keyboard device.
465
466config HID_LOGITECH_HIDPP
467	tristate "Logitech HID++ devices support"
468	depends on HID_LOGITECH
469	select POWER_SUPPLY
470	---help---
471	Support for Logitech devices relyingon the HID++ Logitech specification
472
473	Say Y if you want support for Logitech devices relying on the HID++
474	specification. Such devices are the various Logitech Touchpads (T650,
475	T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
476	Keyboard).
477
478config LOGITECH_FF
479	bool "Logitech force feedback support"
480	depends on HID_LOGITECH
481	select INPUT_FF_MEMLESS
482	help
483	  Say Y here if you have one of these devices:
484	  - Logitech WingMan Cordless RumblePad
485	  - Logitech WingMan Cordless RumblePad 2
486	  - Logitech WingMan Force 3D
487
488	  and if you want to enable force feedback for them.
489	  Note: if you say N here, this device will still be supported, but without
490	  force feedback.
491
492config LOGIRUMBLEPAD2_FF
493	bool "Logitech force feedback support (variant 2)"
494	depends on HID_LOGITECH
495	select INPUT_FF_MEMLESS
496	help
497	  Say Y here if you want to enable force feedback support for:
498	  - Logitech RumblePad
499	  - Logitech Rumblepad 2
500	  - Logitech Formula Vibration Feedback Wheel
501
502config LOGIG940_FF
503	bool "Logitech Flight System G940 force feedback support"
504	depends on HID_LOGITECH
505	select INPUT_FF_MEMLESS
506	help
507	  Say Y here if you want to enable force feedback support for Logitech
508	  Flight System G940 devices.
509
510config LOGIWHEELS_FF
511	bool "Logitech wheels configuration and force feedback support"
512	depends on HID_LOGITECH
513	select INPUT_FF_MEMLESS
514	default LOGITECH_FF
515	help
516	  Say Y here if you want to enable force feedback and range setting(*)
517	  support for following Logitech wheels:
518	  - Logitech G25 (*)
519	  - Logitech G27 (*)
520	  - Logitech G29 (*)
521	  - Logitech Driving Force
522	  - Logitech Driving Force Pro (*)
523	  - Logitech Driving Force GT (*)
524	  - Logitech Driving Force EX/RX
525	  - Logitech Driving Force Wireless
526	  - Logitech Speed Force Wireless
527	  - Logitech MOMO Force
528	  - Logitech MOMO Racing Force
529	  - Logitech Formula Force GP
530	  - Logitech Formula Force EX/RX
531	  - Logitech Wingman Formula Force GP
532
533config HID_MAGICMOUSE
534	tristate "Apple Magic Mouse/Trackpad multi-touch support"
535	depends on HID
536	---help---
537	Support for the Apple Magic Mouse/Trackpad multi-touch.
538
539	Say Y here if you want support for the multi-touch features of the
540	Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
541
542config HID_MAYFLASH
543	tristate "Mayflash game controller adapter force feedback"
544	depends on HID
545	select INPUT_FF_MEMLESS
546	---help---
547	Say Y here if you have HJZ Mayflash PS3 game controller adapters
548	and want to enable force feedback support.
549
550config HID_MICROSOFT
551	tristate "Microsoft non-fully HID-compliant devices"
552	depends on HID
553	default !EXPERT
554	---help---
555	Support for Microsoft devices that are not fully compliant with HID standard.
556
557config HID_MONTEREY
558	tristate "Monterey Genius KB29E keyboard"
559	depends on HID
560	default !EXPERT
561	---help---
562	Support for Monterey Genius KB29E.
563
564config HID_MULTITOUCH
565	tristate "HID Multitouch panels"
566	depends on HID
567	---help---
568	  Generic support for HID multitouch panels.
569
570	  Say Y here if you have one of the following devices:
571	  - 3M PCT touch screens
572	  - ActionStar dual touch panels
573	  - Atmel panels
574	  - Cando dual touch panels
575	  - Chunghwa panels
576	  - CJTouch panels
577	  - CVTouch panels
578	  - Cypress TrueTouch panels
579	  - Elan Microelectronics touch panels
580	  - Elo TouchSystems IntelliTouch Plus panels
581	  - GeneralTouch 'Sensing Win7-TwoFinger' panels
582	  - GoodTouch panels
583	  - Hanvon dual touch panels
584	  - Ilitek dual touch panels
585	  - IrTouch Infrared USB panels
586	  - LG Display panels (Dell ST2220Tc)
587	  - Lumio CrystalTouch panels
588	  - MosArt dual-touch panels
589	  - Panasonic multitouch panels
590	  - PenMount dual touch panels
591	  - Perixx Peripad 701 touchpad
592	  - PixArt optical touch screen
593	  - Pixcir dual touch panels
594	  - Quanta panels
595	  - eGalax dual-touch panels, including the Joojoo and Wetab tablets
596	  - SiS multitouch panels
597	  - Stantum multitouch panels
598	  - Touch International Panels
599	  - Unitec Panels
600	  - Wistron optical touch panels
601	  - XAT optical touch panels
602	  - Xiroku optical touch panels
603	  - Zytronic touch panels
604
605	  If unsure, say N.
606
607	  To compile this driver as a module, choose M here: the
608	  module will be called hid-multitouch.
609
610config HID_NTI
611	tristate "NTI keyboard adapters"
612	---help---
613	Support for the "extra" Sun keyboard keys on keyboards attached
614	through Network Technologies USB-SUN keyboard adapters.
615
616config HID_NTRIG
617	tristate "N-Trig touch screen"
618	depends on USB_HID
619	---help---
620	Support for N-Trig touch screen.
621
622config HID_ORTEK
623	tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
624	depends on HID
625	---help---
626	There are certain devices which have LogicalMaximum wrong in the keyboard
627	usage page of their report descriptor. The most prevailing ones so far
628	are manufactured by Ortek, thus the name of the driver. Currently
629	supported devices by this driver are
630
631	   - Ortek PKB-1700
632	   - Ortek WKB-2000
633	   - Skycable wireless presenter
634
635config HID_PANTHERLORD
636	tristate "Pantherlord/GreenAsia game controller"
637	depends on HID
638	---help---
639	  Say Y here if you have a PantherLord/GreenAsia based game controller
640	  or adapter.
641
642config PANTHERLORD_FF
643	bool "Pantherlord force feedback support"
644	depends on HID_PANTHERLORD
645	select INPUT_FF_MEMLESS
646	---help---
647	  Say Y here if you have a PantherLord/GreenAsia based game controller
648	  or adapter and want to enable force feedback support for it.
649
650config HID_PENMOUNT
651	tristate "Penmount touch device"
652	depends on USB_HID
653	---help---
654	  This selects a driver for the PenMount 6000 touch controller.
655
656	  The driver works around a problem in the report descript allowing
657	  the userspace to touch events instead of mouse events.
658
659	  Say Y here if you have a Penmount based touch controller.
660
661config HID_PETALYNX
662	tristate "Petalynx Maxter remote control"
663	depends on HID
664	---help---
665	Support for Petalynx Maxter remote control.
666
667config HID_PICOLCD
668	tristate "PicoLCD (graphic version)"
669	depends on HID
670	---help---
671	  This provides support for Minibox PicoLCD devices, currently
672	  only the graphical ones are supported.
673
674	  This includes support for the following device features:
675	  - Keypad
676	  - Switching between Firmware and Flash mode
677	  - EEProm / Flash access     (via debugfs)
678	  Features selectively enabled:
679	  - Framebuffer for monochrome 256x64 display
680	  - Backlight control
681	  - Contrast control
682	  - General purpose outputs
683	  Features that are not (yet) supported:
684	  - IR
685
686config HID_PICOLCD_FB
687	bool "Framebuffer support" if EXPERT
688	default !EXPERT
689	depends on HID_PICOLCD
690	depends on HID_PICOLCD=FB || FB=y
691	select FB_DEFERRED_IO
692	select FB_SYS_FILLRECT
693	select FB_SYS_COPYAREA
694	select FB_SYS_IMAGEBLIT
695	select FB_SYS_FOPS
696	---help---
697	  Provide access to PicoLCD's 256x64 monochrome display via a
698	  framebuffer device.
699
700config HID_PICOLCD_BACKLIGHT
701	bool "Backlight control" if EXPERT
702	default !EXPERT
703	depends on HID_PICOLCD
704	depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
705	---help---
706	  Provide access to PicoLCD's backlight control via backlight
707	  class.
708
709config HID_PICOLCD_LCD
710	bool "Contrast control" if EXPERT
711	default !EXPERT
712	depends on HID_PICOLCD
713	depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
714	---help---
715	  Provide access to PicoLCD's LCD contrast via lcd class.
716
717config HID_PICOLCD_LEDS
718	bool "GPO via leds class" if EXPERT
719	default !EXPERT
720	depends on HID_PICOLCD
721	depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
722	---help---
723	  Provide access to PicoLCD's GPO pins via leds class.
724
725config HID_PICOLCD_CIR
726	bool "CIR via RC class" if EXPERT
727	default !EXPERT
728	depends on HID_PICOLCD
729	depends on HID_PICOLCD=RC_CORE || RC_CORE=y
730	---help---
731	  Provide access to PicoLCD's CIR interface via remote control (LIRC).
732
733config HID_PLANTRONICS
734	tristate "Plantronics USB HID Driver"
735	depends on HID
736	---help---
737	  Provides HID support for Plantronics USB audio devices.
738	  Correctly maps vendor unique volume up/down HID usages to
739	  KEY_VOLUMEUP and KEY_VOLUMEDOWN events and prevents core mapping
740	  of other vendor unique HID usages to random mouse events.
741
742	  Say M here if you may ever plug in a Plantronics USB audio device.
743
744config HID_PRIMAX
745	tristate "Primax non-fully HID-compliant devices"
746	depends on HID
747	---help---
748	Support for Primax devices that are not fully compliant with the
749	HID standard.
750
751config HID_RETRODE
752	tristate "Retrode"
753	depends on USB_HID
754	---help---
755	Support for
756
757	  * Retrode 2 cartridge and controller adapter
758
759config HID_ROCCAT
760	tristate "Roccat device support"
761	depends on USB_HID
762	---help---
763	Support for Roccat devices.
764	Say Y here if you have a Roccat mouse or keyboard and want
765	support for its special functionalities.
766
767config HID_SAITEK
768	tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
769	depends on HID
770	---help---
771	Support for Saitek devices that are not fully compliant with the
772	HID standard.
773
774	Supported devices:
775	- PS1000 Dual Analog Pad
776	- Saitek R.A.T.7, R.A.T.9, M.M.O.7 Gaming Mice
777	- Mad Catz R.A.T.5, R.A.T.9 Gaming Mice
778
779config HID_SAMSUNG
780	tristate "Samsung InfraRed remote control or keyboards"
781	depends on HID
782	---help---
783	Support for Samsung InfraRed remote control or keyboards.
784
785config HID_SONY
786	tristate "Sony PS2/3/4 accessories"
787	depends on USB_HID
788	depends on NEW_LEDS
789	depends on LEDS_CLASS
790	select POWER_SUPPLY
791	---help---
792	Support for
793
794	  * Sony PS3 6-axis controllers
795	  * Sony PS4 DualShock 4 controllers
796	  * Buzz controllers
797	  * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
798	  * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
799
800config SONY_FF
801	bool "Sony PS2/3/4 accessories force feedback support"
802	depends on HID_SONY
803	select INPUT_FF_MEMLESS
804	---help---
805	Say Y here if you have a Sony PS2/3/4 accessory and want to enable
806	force feedback support for it.
807
808config HID_SPEEDLINK
809	tristate "Speedlink VAD Cezanne mouse support"
810	depends on HID
811	---help---
812	Support for Speedlink Vicious and Divine Cezanne mouse.
813
814config HID_STEELSERIES
815	tristate "Steelseries SRW-S1 steering wheel support"
816	depends on HID
817	---help---
818	Support for Steelseries SRW-S1 steering wheel
819
820config HID_SUNPLUS
821	tristate "Sunplus wireless desktop"
822	depends on HID
823	---help---
824	Support for Sunplus wireless desktop.
825
826config HID_RMI
827	tristate "Synaptics RMI4 device support"
828	depends on HID
829	select RMI4_CORE
830	select RMI4_F03
831	select RMI4_F11
832	select RMI4_F12
833	select RMI4_F30
834	---help---
835	Support for Synaptics RMI4 touchpads.
836	Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
837	and want support for its special functionalities.
838
839config HID_GREENASIA
840	tristate "GreenAsia (Product ID 0x12) game controller support"
841	depends on HID
842	---help---
843	  Say Y here if you have a GreenAsia (Product ID 0x12) based game
844	  controller or adapter.
845
846config GREENASIA_FF
847	bool "GreenAsia (Product ID 0x12) force feedback support"
848	depends on HID_GREENASIA
849	select INPUT_FF_MEMLESS
850	---help---
851	Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
852	(like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
853	and want to enable force feedback support for it.
854
855config HID_HYPERV_MOUSE
856	tristate "Microsoft Hyper-V mouse driver"
857	depends on HYPERV
858	---help---
859	Select this option to enable the Hyper-V mouse driver.
860
861config HID_SMARTJOYPLUS
862	tristate "SmartJoy PLUS PS2/USB adapter support"
863	depends on HID
864	---help---
865	Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
866	Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
867
868	Note that DDR (Dance Dance Revolution) mode is not supported, nor
869	is pressure sensitive buttons on the pro models.
870
871config SMARTJOYPLUS_FF
872	bool "SmartJoy PLUS PS2/USB adapter force feedback support"
873	depends on HID_SMARTJOYPLUS
874	select INPUT_FF_MEMLESS
875	---help---
876	Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
877	enable force feedback support for it.
878
879config HID_TIVO
880	tristate "TiVo Slide Bluetooth remote control support"
881	depends on HID
882	---help---
883	Say Y if you have a TiVo Slide Bluetooth remote control.
884
885config HID_TOPSEED
886	tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
887	depends on HID
888	---help---
889	Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
890	CLLRCMCE remote control.
891
892config HID_THINGM
893	tristate "ThingM blink(1) USB RGB LED"
894	depends on HID
895	depends on LEDS_CLASS
896	select HID_LED
897	---help---
898	Support for the ThingM blink(1) USB RGB LED. This driver has been
899	merged into the generic hid led driver. Config symbol HID_THINGM
900	just selects HID_LED and will be removed soon.
901
902config HID_THRUSTMASTER
903	tristate "ThrustMaster devices support"
904	depends on HID
905	---help---
906	  Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
907	  a THRUSTMASTER Ferrari GT Rumble Wheel.
908
909config THRUSTMASTER_FF
910	bool "ThrustMaster devices force feedback support"
911	depends on HID_THRUSTMASTER
912	select INPUT_FF_MEMLESS
913	---help---
914	  Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
915	  a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
916	  Rumble Force or Force Feedback Wheel.
917
918config HID_UDRAW_PS3
919	tristate "THQ PS3 uDraw tablet"
920	depends on HID
921	---help---
922	  Say Y here if you want to use the THQ uDraw gaming tablet for
923	  the PS3.
924
925config HID_WACOM
926	tristate "Wacom Intuos/Graphire tablet support (USB)"
927	depends on HID
928	select POWER_SUPPLY
929	select NEW_LEDS
930	select LEDS_CLASS
931	select LEDS_TRIGGERS
932	help
933	  Say Y here if you want to use the USB or BT version of the Wacom Intuos
934	  or Graphire tablet.
935
936	  To compile this driver as a module, choose M here: the
937	  module will be called wacom.
938
939config HID_WIIMOTE
940	tristate "Nintendo Wii / Wii U peripherals"
941	depends on HID
942	depends on LEDS_CLASS
943	select POWER_SUPPLY
944	select INPUT_FF_MEMLESS
945	---help---
946	Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
947	devices are the Wii Remote and its extension devices, but also devices
948	based on the Wii Remote like the Wii U Pro Controller or the
949	Wii Balance Board.
950
951	Support for all official Nintendo extensions is available, however, 3rd
952	party extensions might not be supported. Please report these devices to:
953	  http://github.com/dvdhrm/xwiimote/issues
954
955	Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
956	the Wii U Gamepad) might be supported in the future. But currently
957	support is limited to Bluetooth based devices.
958
959	If unsure, say N.
960
961	To compile this driver as a module, choose M here: the
962	module will be called hid-wiimote.
963
964config HID_XINMO
965	tristate "Xin-Mo non-fully compliant devices"
966	depends on HID
967	---help---
968	Support for Xin-Mo devices that are not fully compliant with the HID
969	standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
970	if you have a Xin-Mo Dual Arcade controller.
971
972config HID_ZEROPLUS
973	tristate "Zeroplus based game controller support"
974	depends on HID
975	---help---
976	  Say Y here if you have a Zeroplus based game controller.
977
978config ZEROPLUS_FF
979	bool "Zeroplus based game controller force feedback support"
980	depends on HID_ZEROPLUS
981	select INPUT_FF_MEMLESS
982	---help---
983	  Say Y here if you have a Zeroplus based game controller and want
984	  to have force feedback support for it.
985
986config HID_ZYDACRON
987	tristate "Zydacron remote control support"
988	depends on HID
989	---help---
990	Support for Zydacron remote control.
991
992config HID_SENSOR_HUB
993	tristate "HID Sensors framework support"
994	depends on HID && HAS_IOMEM
995	select MFD_CORE
996	default n
997	---help---
998	  Support for HID Sensor framework. This creates a MFD instance
999	  for a sensor hub and identifies all the sensors connected to it.
1000	  Each sensor is registered as a MFD cell, so that sensor specific
1001	  processing can be done in a separate driver. Each sensor
1002	  drivers can use the service provided by this driver to register
1003	  for events and handle data streams. Each sensor driver can format
1004	  data and present to user mode using input or IIO interface.
1005
1006config HID_SENSOR_CUSTOM_SENSOR
1007	tristate "HID Sensors hub custom sensor support"
1008	depends on HID_SENSOR_HUB
1009	default n
1010	---help---
1011	  HID Sensor hub specification allows definition of some custom and
1012	  generic sensors. Unlike other HID sensors, they can't be exported
1013	  via Linux IIO because of custom fields. This is up to the manufacturer
1014	  to decide how to interpret these special sensor ids and process in
1015	  the user space. Currently some manufacturers are using these ids for
1016	  sensor calibration and debugging other sensors. Manufacturers
1017	  should't use these special custom sensor ids to export any of the
1018	  standard sensors.
1019	  Select this config option for custom/generic sensor support.
1020
1021config HID_ALPS
1022	tristate "Alps HID device support"
1023	depends on HID
1024	---help---
1025	Support for Alps I2C HID touchpads and StickPointer.
1026	Say Y here if you have a Alps touchpads over i2c-hid or usbhid
1027	and want support for its special functionalities.
1028
1029endmenu
1030
1031endif # HID
1032
1033source "drivers/hid/usbhid/Kconfig"
1034
1035source "drivers/hid/i2c-hid/Kconfig"
1036
1037source "drivers/hid/intel-ish-hid/Kconfig"
1038
1039endmenu
1040