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_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"
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"
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"
162	depends on HID
163	default !EXPERT
164	---help---
165	Support for Cherry Cymotion keyboard.
166
167config HID_CHICONY
168	tristate "Chicony Tactical pad"
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"
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"
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_KEYTOUCH
290	tristate "Keytouch HID devices"
291	depends on HID
292	---help---
293	Support for Keytouch HID devices not fully compliant with
294	the specification. Currently supported:
295		- Keytouch IEC 60945
296
297config HID_KYE
298	tristate "KYE/Genius devices"
299	depends on HID
300	---help---
301	Support for KYE/Genius devices not fully compliant with HID standard:
302	- Ergo Mouse
303	- EasyPen i405X tablet
304	- MousePen i608X tablet
305	- EasyPen M610X tablet
306
307config HID_UCLOGIC
308	tristate "UC-Logic"
309	depends on USB_HID
310	---help---
311	Support for UC-Logic and Huion tablets.
312
313config HID_WALTOP
314	tristate "Waltop"
315	depends on HID
316	---help---
317	Support for Waltop tablets.
318
319config HID_GYRATION
320	tristate "Gyration remote control"
321	depends on HID
322	---help---
323	Support for Gyration remote control.
324
325config HID_ICADE
326	tristate "ION iCade arcade controller"
327	depends on HID
328	---help---
329	Support for the ION iCade arcade controller to work as a joystick.
330
331	To compile this driver as a module, choose M here: the
332	module will be called hid-icade.
333
334config HID_TWINHAN
335	tristate "Twinhan IR remote control"
336	depends on HID
337	---help---
338	Support for Twinhan IR remote control.
339
340config HID_KENSINGTON
341	tristate "Kensington Slimblade Trackball"
342	depends on HID
343	default !EXPERT
344	---help---
345	Support for Kensington Slimblade Trackball.
346
347config HID_LCPOWER
348	tristate "LC-Power"
349	depends on HID
350	---help---
351	Support for LC-Power RC1000MCE RF remote control.
352
353config HID_LENOVO
354	tristate "Lenovo / Thinkpad devices"
355	depends on HID
356	select NEW_LEDS
357	select LEDS_CLASS
358	---help---
359	Support for Lenovo devices that are not fully compliant with HID standard.
360
361	Say Y if you want support for the non-compliant features of the Lenovo
362	Thinkpad standalone keyboards, e.g:
363	- ThinkPad USB Keyboard with TrackPoint (supports extra LEDs and trackpoint
364	  configuration)
365	- ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
366	- ThinkPad Compact USB Keyboard with TrackPoint (supports Fn keys)
367
368config HID_LOGITECH
369	tristate "Logitech devices"
370	depends on HID
371	default !EXPERT
372	---help---
373	Support for Logitech devices that are not fully compliant with HID standard.
374
375config HID_LOGITECH_DJ
376	tristate "Logitech Unifying receivers full support"
377	depends on HIDRAW
378	depends on HID_LOGITECH
379	select HID_LOGITECH_HIDPP
380	---help---
381	Say Y if you want support for Logitech Unifying receivers and devices.
382	Unifying receivers are capable of pairing up to 6 Logitech compliant
383	devices to the same receiver. Without this driver it will be handled by
384	generic USB_HID driver and all incoming events will be multiplexed
385	into a single mouse and a single keyboard device.
386
387config HID_LOGITECH_HIDPP
388	tristate "Logitech HID++ devices support"
389	depends on HID_LOGITECH
390	---help---
391	Support for Logitech devices relyingon the HID++ Logitech specification
392
393	Say Y if you want support for Logitech devices relying on the HID++
394	specification. Such devices are the various Logitech Touchpads (T650,
395	T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
396	Keyboard).
397
398config LOGITECH_FF
399	bool "Logitech force feedback support"
400	depends on HID_LOGITECH
401	select INPUT_FF_MEMLESS
402	help
403	  Say Y here if you have one of these devices:
404	  - Logitech WingMan Cordless RumblePad
405	  - Logitech WingMan Cordless RumblePad 2
406	  - Logitech WingMan Force 3D
407	  - Logitech Formula Force EX
408	  - Logitech WingMan Formula Force GP
409
410	  and if you want to enable force feedback for them.
411	  Note: if you say N here, this device will still be supported, but without
412	  force feedback.
413
414config LOGIRUMBLEPAD2_FF
415	bool "Logitech force feedback support (variant 2)"
416	depends on HID_LOGITECH
417	select INPUT_FF_MEMLESS
418	help
419	  Say Y here if you want to enable force feedback support for:
420	  - Logitech RumblePad
421	  - Logitech Rumblepad 2
422	  - Logitech Formula Vibration Feedback Wheel
423
424config LOGIG940_FF
425	bool "Logitech Flight System G940 force feedback support"
426	depends on HID_LOGITECH
427	select INPUT_FF_MEMLESS
428	help
429	  Say Y here if you want to enable force feedback support for Logitech
430	  Flight System G940 devices.
431
432config LOGIWHEELS_FF
433	bool "Logitech wheels configuration and force feedback support"
434	depends on HID_LOGITECH
435	select INPUT_FF_MEMLESS
436	default LOGITECH_FF
437	help
438	  Say Y here if you want to enable force feedback and range setting
439	  support for following Logitech wheels:
440	  - Logitech Driving Force
441	  - Logitech Driving Force Pro
442	  - Logitech Driving Force GT
443	  - Logitech G25
444	  - Logitech G27
445	  - Logitech MOMO/MOMO 2
446	  - Logitech Formula Force EX
447
448config HID_MAGICMOUSE
449	tristate "Apple Magic Mouse/Trackpad multi-touch support"
450	depends on HID
451	---help---
452	Support for the Apple Magic Mouse/Trackpad multi-touch.
453
454	Say Y here if you want support for the multi-touch features of the
455	Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
456
457config HID_MICROSOFT
458	tristate "Microsoft non-fully HID-compliant devices"
459	depends on HID
460	default !EXPERT
461	---help---
462	Support for Microsoft devices that are not fully compliant with HID standard.
463
464config HID_MONTEREY
465	tristate "Monterey Genius KB29E keyboard"
466	depends on HID
467	default !EXPERT
468	---help---
469	Support for Monterey Genius KB29E.
470
471config HID_MULTITOUCH
472	tristate "HID Multitouch panels"
473	depends on HID
474	---help---
475	  Generic support for HID multitouch panels.
476
477	  Say Y here if you have one of the following devices:
478	  - 3M PCT touch screens
479	  - ActionStar dual touch panels
480	  - Atmel panels
481	  - Cando dual touch panels
482	  - Chunghwa panels
483	  - CVTouch panels
484	  - Cypress TrueTouch panels
485	  - Elan Microelectronics touch panels
486	  - Elo TouchSystems IntelliTouch Plus panels
487	  - GeneralTouch 'Sensing Win7-TwoFinger' panels
488	  - GoodTouch panels
489	  - Hanvon dual touch panels
490	  - Ilitek dual touch panels
491	  - IrTouch Infrared USB panels
492	  - LG Display panels (Dell ST2220Tc)
493	  - Lumio CrystalTouch panels
494	  - MosArt dual-touch panels
495	  - Panasonic multitouch panels
496	  - PenMount dual touch panels
497	  - Perixx Peripad 701 touchpad
498	  - PixArt optical touch screen
499	  - Pixcir dual touch panels
500	  - Quanta panels
501	  - eGalax dual-touch panels, including the Joojoo and Wetab tablets
502	  - SiS multitouch panels
503	  - Stantum multitouch panels
504	  - Touch International Panels
505	  - Unitec Panels
506	  - Wistron optical touch panels
507	  - XAT optical touch panels
508	  - Xiroku optical touch panels
509	  - Zytronic touch panels
510
511	  If unsure, say N.
512
513	  To compile this driver as a module, choose M here: the
514	  module will be called hid-multitouch.
515
516config HID_NTRIG
517	tristate "N-Trig touch screen"
518	depends on USB_HID
519	---help---
520	Support for N-Trig touch screen.
521
522config HID_ORTEK
523	tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
524	depends on HID
525	---help---
526	There are certain devices which have LogicalMaximum wrong in the keyboard
527	usage page of their report descriptor. The most prevailing ones so far
528	are manufactured by Ortek, thus the name of the driver. Currently
529	supported devices by this driver are
530
531	   - Ortek PKB-1700
532	   - Ortek WKB-2000
533	   - Skycable wireless presenter
534
535config HID_PANTHERLORD
536	tristate "Pantherlord/GreenAsia game controller"
537	depends on HID
538	---help---
539	  Say Y here if you have a PantherLord/GreenAsia based game controller
540	  or adapter.
541
542config PANTHERLORD_FF
543	bool "Pantherlord force feedback support"
544	depends on HID_PANTHERLORD
545	select INPUT_FF_MEMLESS
546	---help---
547	  Say Y here if you have a PantherLord/GreenAsia based game controller
548	  or adapter and want to enable force feedback support for it.
549
550config HID_PENMOUNT
551	tristate "Penmount touch device"
552	depends on USB_HID
553	---help---
554	  This selects a driver for the PenMount 6000 touch controller.
555
556	  The driver works around a problem in the report descript allowing
557	  the userspace to touch events instead of mouse events.
558
559	  Say Y here if you have a Penmount based touch controller.
560
561config HID_PETALYNX
562	tristate "Petalynx Maxter remote control"
563	depends on HID
564	---help---
565	Support for Petalynx Maxter remote control.
566
567config HID_PICOLCD
568	tristate "PicoLCD (graphic version)"
569	depends on HID
570	---help---
571	  This provides support for Minibox PicoLCD devices, currently
572	  only the graphical ones are supported.
573
574	  This includes support for the following device features:
575	  - Keypad
576	  - Switching between Firmware and Flash mode
577	  - EEProm / Flash access     (via debugfs)
578	  Features selectively enabled:
579	  - Framebuffer for monochrome 256x64 display
580	  - Backlight control
581	  - Contrast control
582	  - General purpose outputs
583	  Features that are not (yet) supported:
584	  - IR
585
586config HID_PICOLCD_FB
587	bool "Framebuffer support" if EXPERT
588	default !EXPERT
589	depends on HID_PICOLCD
590	depends on HID_PICOLCD=FB || FB=y
591	select FB_DEFERRED_IO
592	select FB_SYS_FILLRECT
593	select FB_SYS_COPYAREA
594	select FB_SYS_IMAGEBLIT
595	select FB_SYS_FOPS
596	---help---
597	  Provide access to PicoLCD's 256x64 monochrome display via a
598	  framebuffer device.
599
600config HID_PICOLCD_BACKLIGHT
601	bool "Backlight control" if EXPERT
602	default !EXPERT
603	depends on HID_PICOLCD
604	depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
605	---help---
606	  Provide access to PicoLCD's backlight control via backlight
607	  class.
608
609config HID_PICOLCD_LCD
610	bool "Contrast control" if EXPERT
611	default !EXPERT
612	depends on HID_PICOLCD
613	depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
614	---help---
615	  Provide access to PicoLCD's LCD contrast via lcd class.
616
617config HID_PICOLCD_LEDS
618	bool "GPO via leds class" if EXPERT
619	default !EXPERT
620	depends on HID_PICOLCD
621	depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
622	---help---
623	  Provide access to PicoLCD's GPO pins via leds class.
624
625config HID_PICOLCD_CIR
626	bool "CIR via RC class" if EXPERT
627	default !EXPERT
628	depends on HID_PICOLCD
629	depends on HID_PICOLCD=RC_CORE || RC_CORE=y
630	---help---
631	  Provide access to PicoLCD's CIR interface via remote control (LIRC).
632
633config HID_PLANTRONICS
634	tristate "Plantronics USB HID Driver"
635	depends on HID
636	---help---
637	Provides HID support for Plantronics telephony devices.
638
639config HID_PRIMAX
640	tristate "Primax non-fully HID-compliant devices"
641	depends on HID
642	---help---
643	Support for Primax devices that are not fully compliant with the
644	HID standard.
645
646config HID_ROCCAT
647	tristate "Roccat device support"
648	depends on USB_HID
649	---help---
650	Support for Roccat devices.
651	Say Y here if you have a Roccat mouse or keyboard and want
652	support for its special functionalities.
653
654config HID_SAITEK
655	tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
656	depends on HID
657	---help---
658	Support for Saitek devices that are not fully compliant with the
659	HID standard.
660
661	Supported devices:
662	- PS1000 Dual Analog Pad
663	- R.A.T.9 Gaming Mouse
664	- R.A.T.7 Gaming Mouse
665	- M.M.O.7 Gaming Mouse
666
667config HID_SAMSUNG
668	tristate "Samsung InfraRed remote control or keyboards"
669	depends on HID
670	---help---
671	Support for Samsung InfraRed remote control or keyboards.
672
673config HID_SONY
674	tristate "Sony PS2/3/4 accessories"
675	depends on USB_HID
676	depends on NEW_LEDS
677	depends on LEDS_CLASS
678	select POWER_SUPPLY
679	---help---
680	Support for
681
682	  * Sony PS3 6-axis controllers
683	  * Sony PS4 DualShock 4 controllers
684	  * Buzz controllers
685	  * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
686	  * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
687
688config SONY_FF
689	bool "Sony PS2/3/4 accessories force feedback support" 
690	depends on HID_SONY
691	select INPUT_FF_MEMLESS
692	---help---
693	Say Y here if you have a Sony PS2/3/4 accessory and want to enable
694	force feedback support for it.
695
696config HID_SPEEDLINK
697	tristate "Speedlink VAD Cezanne mouse support"
698	depends on HID
699	---help---
700	Support for Speedlink Vicious and Divine Cezanne mouse.
701
702config HID_STEELSERIES
703	tristate "Steelseries SRW-S1 steering wheel support"
704	depends on HID
705	---help---
706	Support for Steelseries SRW-S1 steering wheel
707
708config HID_SUNPLUS
709	tristate "Sunplus wireless desktop"
710	depends on HID
711	---help---
712	Support for Sunplus wireless desktop.
713
714config HID_RMI
715	tristate "Synaptics RMI4 device support"
716	depends on HID
717	---help---
718	Support for Synaptics RMI4 touchpads.
719	Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
720	and want support for its special functionalities.
721
722config HID_GREENASIA
723	tristate "GreenAsia (Product ID 0x12) game controller support"
724	depends on HID
725	---help---
726	  Say Y here if you have a GreenAsia (Product ID 0x12) based game
727	  controller or adapter.
728
729config GREENASIA_FF
730	bool "GreenAsia (Product ID 0x12) force feedback support"
731	depends on HID_GREENASIA
732	select INPUT_FF_MEMLESS
733	---help---
734	Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
735	(like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
736	and want to enable force feedback support for it.
737
738config HID_HYPERV_MOUSE
739	tristate "Microsoft Hyper-V mouse driver"
740	depends on HYPERV
741	---help---
742	Select this option to enable the Hyper-V mouse driver.
743
744config HID_SMARTJOYPLUS
745	tristate "SmartJoy PLUS PS2/USB adapter support"
746	depends on HID
747	---help---
748	Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
749	Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
750
751	Note that DDR (Dance Dance Revolution) mode is not supported, nor
752	is pressure sensitive buttons on the pro models.
753
754config SMARTJOYPLUS_FF
755	bool "SmartJoy PLUS PS2/USB adapter force feedback support"
756	depends on HID_SMARTJOYPLUS
757	select INPUT_FF_MEMLESS
758	---help---
759	Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
760	enable force feedback support for it.
761
762config HID_TIVO
763	tristate "TiVo Slide Bluetooth remote control support"
764	depends on HID
765	---help---
766	Say Y if you have a TiVo Slide Bluetooth remote control.
767
768config HID_TOPSEED
769	tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
770	depends on HID
771	---help---
772	Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
773	CLLRCMCE remote control.
774
775config HID_THINGM
776	tristate "ThingM blink(1) USB RGB LED"
777	depends on HID
778	depends on LEDS_CLASS
779	---help---
780	Support for the ThingM blink(1) USB RGB LED. This driver registers a
781	Linux LED class instance, plus additional sysfs attributes to control
782	RGB colors, fade time and playing. The device is exposed through hidraw
783	to access other functions.
784
785config HID_THRUSTMASTER
786	tristate "ThrustMaster devices support"
787	depends on HID
788	---help---
789	  Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
790	  a THRUSTMASTER Ferrari GT Rumble Wheel.
791
792config THRUSTMASTER_FF
793	bool "ThrustMaster devices force feedback support"
794	depends on HID_THRUSTMASTER
795	select INPUT_FF_MEMLESS
796	---help---
797	  Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
798	  a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
799	  Rumble Force or Force Feedback Wheel.
800
801config HID_WACOM
802	tristate "Wacom Intuos/Graphire tablet support (USB)"
803	depends on HID
804	select POWER_SUPPLY
805	select NEW_LEDS
806	select LEDS_CLASS
807	help
808	  Say Y here if you want to use the USB or BT version of the Wacom Intuos
809	  or Graphire tablet.
810
811	  To compile this driver as a module, choose M here: the
812	  module will be called wacom.
813
814config HID_WIIMOTE
815	tristate "Nintendo Wii / Wii U peripherals"
816	depends on HID
817	depends on LEDS_CLASS
818	select POWER_SUPPLY
819	select INPUT_FF_MEMLESS
820	---help---
821	Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
822	devices are the Wii Remote and its extension devices, but also devices
823	based on the Wii Remote like the Wii U Pro Controller or the
824	Wii Balance Board.
825
826	Support for all official Nintendo extensions is available, however, 3rd
827	party extensions might not be supported. Please report these devices to:
828	  http://github.com/dvdhrm/xwiimote/issues
829
830	Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
831	the Wii U Gamepad) might be supported in the future. But currently
832	support is limited to Bluetooth based devices.
833
834	If unsure, say N.
835
836	To compile this driver as a module, choose M here: the
837	module will be called hid-wiimote.
838
839config HID_XINMO
840	tristate "Xin-Mo non-fully compliant devices"
841	depends on HID
842	---help---
843	Support for Xin-Mo devices that are not fully compliant with the HID
844	standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
845	if you have a Xin-Mo Dual Arcade controller.
846
847config HID_ZEROPLUS
848	tristate "Zeroplus based game controller support"
849	depends on HID
850	---help---
851	  Say Y here if you have a Zeroplus based game controller.
852
853config ZEROPLUS_FF
854	bool "Zeroplus based game controller force feedback support"
855	depends on HID_ZEROPLUS
856	select INPUT_FF_MEMLESS
857	---help---
858	  Say Y here if you have a Zeroplus based game controller and want
859	  to have force feedback support for it.
860
861config HID_ZYDACRON
862	tristate "Zydacron remote control support"
863	depends on HID
864	---help---
865	Support for Zydacron remote control.
866
867config HID_SENSOR_HUB
868	tristate "HID Sensors framework support"
869	depends on HID && HAS_IOMEM
870	select MFD_CORE
871	default n
872	---help---
873	  Support for HID Sensor framework. This creates a MFD instance
874	  for a sensor hub and identifies all the sensors connected to it.
875	  Each sensor is registered as a MFD cell, so that sensor specific
876	  processing can be done in a separate driver. Each sensor
877	  drivers can use the service provided by this driver to register
878	  for events and handle data streams. Each sensor driver can format
879	  data and present to user mode using input or IIO interface.
880
881config HID_SENSOR_CUSTOM_SENSOR
882	tristate "HID Sensors hub custom sensor support"
883	depends on HID_SENSOR_HUB
884	default n
885	---help---
886	  HID Sensor hub specification allows definition of some custom and
887	  generic sensors. Unlike other HID sensors, they can't be exported
888	  via Linux IIO because of custom fields. This is up to the manufacturer
889	  to decide how to interpret these special sensor ids and process in
890	  the user space. Currently some manufacturers are using these ids for
891	  sensor calibration and debugging other sensors. Manufacturers
892	  should't use these special custom sensor ids to export any of the
893	  standard sensors.
894	  Select this config option for custom/generic sensor support.
895
896endmenu
897
898endif # HID
899
900source "drivers/hid/usbhid/Kconfig"
901
902source "drivers/hid/i2c-hid/Kconfig"
903
904endmenu
905