xref: /openbmc/linux/drivers/hid/Kconfig (revision a2cce7a9)
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_GEMBIRD
255	tristate "Gembird Joypad"
256	depends on HID
257	---help---
258	Support for Gembird JPD-DualForce 2.
259
260config HID_HOLTEK
261	tristate "Holtek HID devices"
262	depends on USB_HID
263	---help---
264	Support for Holtek based devices:
265	  - Holtek On Line Grip based game controller
266	  - Trust GXT 18 Gaming Keyboard
267	  - Sharkoon Drakonia / Perixx MX-2000 gaming mice
268	  - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
269	    Zalman ZM-GM1
270	  - SHARKOON DarkGlider Gaming mouse
271	  - LEETGION Hellion Gaming Mouse
272
273config HOLTEK_FF
274	bool "Holtek On Line Grip force feedback support"
275	depends on HID_HOLTEK
276	select INPUT_FF_MEMLESS
277	---help---
278	  Say Y here if you have a Holtek On Line Grip based game controller
279	  and want to have force feedback support for it.
280
281config HID_GT683R
282	tristate "MSI GT68xR LED support"
283	depends on LEDS_CLASS && USB_HID
284	---help---
285	Say Y here if you want to enable support for the three MSI GT68xR LEDs
286
287	This driver support following modes:
288	  - Normal: LEDs are fully on when enabled
289	  - Audio:  LEDs brightness depends on sound level
290	  - Breathing: LEDs brightness varies at human breathing rate
291
292	Currently the following devices are know to be supported:
293	  - MSI GT683R
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 USB_HID
316	---help---
317	Support for UC-Logic and Huion 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"
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"
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"
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"
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	  - CJTouch panels
490	  - CVTouch panels
491	  - Cypress TrueTouch panels
492	  - Elan Microelectronics touch panels
493	  - Elo TouchSystems IntelliTouch Plus panels
494	  - GeneralTouch 'Sensing Win7-TwoFinger' panels
495	  - GoodTouch panels
496	  - Hanvon dual touch panels
497	  - Ilitek dual touch panels
498	  - IrTouch Infrared USB panels
499	  - LG Display panels (Dell ST2220Tc)
500	  - Lumio CrystalTouch panels
501	  - MosArt dual-touch panels
502	  - Panasonic multitouch panels
503	  - PenMount dual touch panels
504	  - Perixx Peripad 701 touchpad
505	  - PixArt optical touch screen
506	  - Pixcir dual touch panels
507	  - Quanta panels
508	  - eGalax dual-touch panels, including the Joojoo and Wetab tablets
509	  - SiS multitouch panels
510	  - Stantum multitouch panels
511	  - Touch International Panels
512	  - Unitec Panels
513	  - Wistron optical touch panels
514	  - XAT optical touch panels
515	  - Xiroku optical touch panels
516	  - Zytronic touch panels
517
518	  If unsure, say N.
519
520	  To compile this driver as a module, choose M here: the
521	  module will be called hid-multitouch.
522
523config HID_NTRIG
524	tristate "N-Trig touch screen"
525	depends on USB_HID
526	---help---
527	Support for N-Trig touch screen.
528
529config HID_ORTEK
530	tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
531	depends on HID
532	---help---
533	There are certain devices which have LogicalMaximum wrong in the keyboard
534	usage page of their report descriptor. The most prevailing ones so far
535	are manufactured by Ortek, thus the name of the driver. Currently
536	supported devices by this driver are
537
538	   - Ortek PKB-1700
539	   - Ortek WKB-2000
540	   - Skycable wireless presenter
541
542config HID_PANTHERLORD
543	tristate "Pantherlord/GreenAsia game controller"
544	depends on HID
545	---help---
546	  Say Y here if you have a PantherLord/GreenAsia based game controller
547	  or adapter.
548
549config PANTHERLORD_FF
550	bool "Pantherlord force feedback support"
551	depends on HID_PANTHERLORD
552	select INPUT_FF_MEMLESS
553	---help---
554	  Say Y here if you have a PantherLord/GreenAsia based game controller
555	  or adapter and want to enable force feedback support for it.
556
557config HID_PENMOUNT
558	tristate "Penmount touch device"
559	depends on USB_HID
560	---help---
561	  This selects a driver for the PenMount 6000 touch controller.
562
563	  The driver works around a problem in the report descript allowing
564	  the userspace to touch events instead of mouse events.
565
566	  Say Y here if you have a Penmount based touch controller.
567
568config HID_PETALYNX
569	tristate "Petalynx Maxter remote control"
570	depends on HID
571	---help---
572	Support for Petalynx Maxter remote control.
573
574config HID_PICOLCD
575	tristate "PicoLCD (graphic version)"
576	depends on HID
577	---help---
578	  This provides support for Minibox PicoLCD devices, currently
579	  only the graphical ones are supported.
580
581	  This includes support for the following device features:
582	  - Keypad
583	  - Switching between Firmware and Flash mode
584	  - EEProm / Flash access     (via debugfs)
585	  Features selectively enabled:
586	  - Framebuffer for monochrome 256x64 display
587	  - Backlight control
588	  - Contrast control
589	  - General purpose outputs
590	  Features that are not (yet) supported:
591	  - IR
592
593config HID_PICOLCD_FB
594	bool "Framebuffer support" if EXPERT
595	default !EXPERT
596	depends on HID_PICOLCD
597	depends on HID_PICOLCD=FB || FB=y
598	select FB_DEFERRED_IO
599	select FB_SYS_FILLRECT
600	select FB_SYS_COPYAREA
601	select FB_SYS_IMAGEBLIT
602	select FB_SYS_FOPS
603	---help---
604	  Provide access to PicoLCD's 256x64 monochrome display via a
605	  framebuffer device.
606
607config HID_PICOLCD_BACKLIGHT
608	bool "Backlight control" if EXPERT
609	default !EXPERT
610	depends on HID_PICOLCD
611	depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
612	---help---
613	  Provide access to PicoLCD's backlight control via backlight
614	  class.
615
616config HID_PICOLCD_LCD
617	bool "Contrast control" if EXPERT
618	default !EXPERT
619	depends on HID_PICOLCD
620	depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
621	---help---
622	  Provide access to PicoLCD's LCD contrast via lcd class.
623
624config HID_PICOLCD_LEDS
625	bool "GPO via leds class" if EXPERT
626	default !EXPERT
627	depends on HID_PICOLCD
628	depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
629	---help---
630	  Provide access to PicoLCD's GPO pins via leds class.
631
632config HID_PICOLCD_CIR
633	bool "CIR via RC class" if EXPERT
634	default !EXPERT
635	depends on HID_PICOLCD
636	depends on HID_PICOLCD=RC_CORE || RC_CORE=y
637	---help---
638	  Provide access to PicoLCD's CIR interface via remote control (LIRC).
639
640config HID_PLANTRONICS
641	tristate "Plantronics USB HID Driver"
642	depends on HID
643	---help---
644	  Provides HID support for Plantronics USB audio devices.
645	  Correctly maps vendor unique volume up/down HID usages to
646	  KEY_VOLUMEUP and KEY_VOLUMEDOWN events and prevents core mapping
647	  of other vendor unique HID usages to random mouse events.
648
649	  Say M here if you may ever plug in a Plantronics USB audio device.
650
651config HID_PRIMAX
652	tristate "Primax non-fully HID-compliant devices"
653	depends on HID
654	---help---
655	Support for Primax devices that are not fully compliant with the
656	HID standard.
657
658config HID_ROCCAT
659	tristate "Roccat device support"
660	depends on USB_HID
661	---help---
662	Support for Roccat devices.
663	Say Y here if you have a Roccat mouse or keyboard and want
664	support for its special functionalities.
665
666config HID_SAITEK
667	tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
668	depends on HID
669	---help---
670	Support for Saitek devices that are not fully compliant with the
671	HID standard.
672
673	Supported devices:
674	- PS1000 Dual Analog Pad
675	- R.A.T.9 Gaming Mouse
676	- R.A.T.7 Gaming Mouse
677	- M.M.O.7 Gaming Mouse
678
679config HID_SAMSUNG
680	tristate "Samsung InfraRed remote control or keyboards"
681	depends on HID
682	---help---
683	Support for Samsung InfraRed remote control or keyboards.
684
685config HID_SONY
686	tristate "Sony PS2/3/4 accessories"
687	depends on USB_HID
688	depends on NEW_LEDS
689	depends on LEDS_CLASS
690	select POWER_SUPPLY
691	---help---
692	Support for
693
694	  * Sony PS3 6-axis controllers
695	  * Sony PS4 DualShock 4 controllers
696	  * Buzz controllers
697	  * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
698	  * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
699
700config SONY_FF
701	bool "Sony PS2/3/4 accessories force feedback support"
702	depends on HID_SONY
703	select INPUT_FF_MEMLESS
704	---help---
705	Say Y here if you have a Sony PS2/3/4 accessory and want to enable
706	force feedback support for it.
707
708config HID_SPEEDLINK
709	tristate "Speedlink VAD Cezanne mouse support"
710	depends on HID
711	---help---
712	Support for Speedlink Vicious and Divine Cezanne mouse.
713
714config HID_STEELSERIES
715	tristate "Steelseries SRW-S1 steering wheel support"
716	depends on HID
717	---help---
718	Support for Steelseries SRW-S1 steering wheel
719
720config HID_SUNPLUS
721	tristate "Sunplus wireless desktop"
722	depends on HID
723	---help---
724	Support for Sunplus wireless desktop.
725
726config HID_RMI
727	tristate "Synaptics RMI4 device support"
728	depends on HID
729	---help---
730	Support for Synaptics RMI4 touchpads.
731	Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
732	and want support for its special functionalities.
733
734config HID_GREENASIA
735	tristate "GreenAsia (Product ID 0x12) game controller support"
736	depends on HID
737	---help---
738	  Say Y here if you have a GreenAsia (Product ID 0x12) based game
739	  controller or adapter.
740
741config GREENASIA_FF
742	bool "GreenAsia (Product ID 0x12) force feedback support"
743	depends on HID_GREENASIA
744	select INPUT_FF_MEMLESS
745	---help---
746	Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
747	(like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
748	and want to enable force feedback support for it.
749
750config HID_HYPERV_MOUSE
751	tristate "Microsoft Hyper-V mouse driver"
752	depends on HYPERV
753	---help---
754	Select this option to enable the Hyper-V mouse driver.
755
756config HID_SMARTJOYPLUS
757	tristate "SmartJoy PLUS PS2/USB adapter support"
758	depends on HID
759	---help---
760	Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
761	Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
762
763	Note that DDR (Dance Dance Revolution) mode is not supported, nor
764	is pressure sensitive buttons on the pro models.
765
766config SMARTJOYPLUS_FF
767	bool "SmartJoy PLUS PS2/USB adapter force feedback support"
768	depends on HID_SMARTJOYPLUS
769	select INPUT_FF_MEMLESS
770	---help---
771	Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
772	enable force feedback support for it.
773
774config HID_TIVO
775	tristate "TiVo Slide Bluetooth remote control support"
776	depends on HID
777	---help---
778	Say Y if you have a TiVo Slide Bluetooth remote control.
779
780config HID_TOPSEED
781	tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
782	depends on HID
783	---help---
784	Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
785	CLLRCMCE remote control.
786
787config HID_THINGM
788	tristate "ThingM blink(1) USB RGB LED"
789	depends on HID
790	depends on LEDS_CLASS
791	---help---
792	Support for the ThingM blink(1) USB RGB LED. This driver registers a
793	Linux LED class instance, plus additional sysfs attributes to control
794	RGB colors, fade time and playing. The device is exposed through hidraw
795	to access other functions.
796
797config HID_THRUSTMASTER
798	tristate "ThrustMaster devices support"
799	depends on HID
800	---help---
801	  Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
802	  a THRUSTMASTER Ferrari GT Rumble Wheel.
803
804config THRUSTMASTER_FF
805	bool "ThrustMaster devices force feedback support"
806	depends on HID_THRUSTMASTER
807	select INPUT_FF_MEMLESS
808	---help---
809	  Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
810	  a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
811	  Rumble Force or Force Feedback Wheel.
812
813config HID_WACOM
814	tristate "Wacom Intuos/Graphire tablet support (USB)"
815	depends on HID
816	select POWER_SUPPLY
817	select NEW_LEDS
818	select LEDS_CLASS
819	help
820	  Say Y here if you want to use the USB or BT version of the Wacom Intuos
821	  or Graphire tablet.
822
823	  To compile this driver as a module, choose M here: the
824	  module will be called wacom.
825
826config HID_WIIMOTE
827	tristate "Nintendo Wii / Wii U peripherals"
828	depends on HID
829	depends on LEDS_CLASS
830	select POWER_SUPPLY
831	select INPUT_FF_MEMLESS
832	---help---
833	Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
834	devices are the Wii Remote and its extension devices, but also devices
835	based on the Wii Remote like the Wii U Pro Controller or the
836	Wii Balance Board.
837
838	Support for all official Nintendo extensions is available, however, 3rd
839	party extensions might not be supported. Please report these devices to:
840	  http://github.com/dvdhrm/xwiimote/issues
841
842	Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
843	the Wii U Gamepad) might be supported in the future. But currently
844	support is limited to Bluetooth based devices.
845
846	If unsure, say N.
847
848	To compile this driver as a module, choose M here: the
849	module will be called hid-wiimote.
850
851config HID_XINMO
852	tristate "Xin-Mo non-fully compliant devices"
853	depends on HID
854	---help---
855	Support for Xin-Mo devices that are not fully compliant with the HID
856	standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
857	if you have a Xin-Mo Dual Arcade controller.
858
859config HID_ZEROPLUS
860	tristate "Zeroplus based game controller support"
861	depends on HID
862	---help---
863	  Say Y here if you have a Zeroplus based game controller.
864
865config ZEROPLUS_FF
866	bool "Zeroplus based game controller force feedback support"
867	depends on HID_ZEROPLUS
868	select INPUT_FF_MEMLESS
869	---help---
870	  Say Y here if you have a Zeroplus based game controller and want
871	  to have force feedback support for it.
872
873config HID_ZYDACRON
874	tristate "Zydacron remote control support"
875	depends on HID
876	---help---
877	Support for Zydacron remote control.
878
879config HID_SENSOR_HUB
880	tristate "HID Sensors framework support"
881	depends on HID && HAS_IOMEM
882	select MFD_CORE
883	default n
884	---help---
885	  Support for HID Sensor framework. This creates a MFD instance
886	  for a sensor hub and identifies all the sensors connected to it.
887	  Each sensor is registered as a MFD cell, so that sensor specific
888	  processing can be done in a separate driver. Each sensor
889	  drivers can use the service provided by this driver to register
890	  for events and handle data streams. Each sensor driver can format
891	  data and present to user mode using input or IIO interface.
892
893config HID_SENSOR_CUSTOM_SENSOR
894	tristate "HID Sensors hub custom sensor support"
895	depends on HID_SENSOR_HUB
896	default n
897	---help---
898	  HID Sensor hub specification allows definition of some custom and
899	  generic sensors. Unlike other HID sensors, they can't be exported
900	  via Linux IIO because of custom fields. This is up to the manufacturer
901	  to decide how to interpret these special sensor ids and process in
902	  the user space. Currently some manufacturers are using these ids for
903	  sensor calibration and debugging other sensors. Manufacturers
904	  should't use these special custom sensor ids to export any of the
905	  standard sensors.
906	  Select this config option for custom/generic sensor support.
907
908endmenu
909
910endif # HID
911
912source "drivers/hid/usbhid/Kconfig"
913
914source "drivers/hid/i2c-hid/Kconfig"
915
916endmenu
917