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