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