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