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