xref: /openbmc/linux/drivers/hid/Kconfig (revision 7da7cbbb)
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 && POWER_SUPPLY && HID = POWER_SUPPLY
31	default n
32	---help---
33	This option adds support of reporting battery strength (for HID devices
34	that support this feature) through power_supply class so that userspace
35	tools, such as upower, can display it.
36
37config HIDRAW
38	bool "/dev/hidraw raw HID device support"
39	depends on HID
40	---help---
41	Say Y here if you want to support HID devices (from the USB
42	specification standpoint) that aren't strictly user interface
43	devices, like monitor controls and Uninterruptable Power Supplies.
44
45	This module supports these devices separately using a separate
46	event interface on /dev/hidraw.
47
48	There is also a /dev/hiddev configuration option in the USB HID
49	configuration menu. In comparison to hiddev, this device does not process
50	the hid events at all (no parsing, no lookups). This lets applications
51	to work on raw hid events when they want to, and avoid using transport-specific
52	userspace libhid/libusb libraries.
53
54	If unsure, say Y.
55
56config UHID
57	tristate "User-space I/O driver support for HID subsystem"
58	depends on HID
59	default n
60	---help---
61	Say Y here if you want to provide HID I/O Drivers from user-space.
62	This allows to write I/O drivers in user-space and feed the data from
63	the device into the kernel. The kernel parses the HID reports, loads the
64	corresponding HID Device Driver or provides input devices on top of your
65	user-space device.
66
67	This driver cannot be used to parse HID-reports in user-space and write
68	special HID-drivers. You should use hidraw for that.
69	Instead, this driver allows to write the transport-layer driver in
70	user-space like USB-HID and Bluetooth-HID do in kernel-space.
71
72	If unsure, say N.
73
74	To compile this driver as a module, choose M here: the
75	module will be called uhid.
76
77config HID_GENERIC
78	tristate "Generic HID driver"
79	depends on HID
80	default HID
81	---help---
82	Support for generic devices on the HID bus. This includes most
83	keyboards and mice, joysticks, tablets and digitizers.
84
85	To compile this driver as a module, choose M here: the module
86	will be called hid-generic.
87
88	If unsure, say Y.
89
90menu "Special HID drivers"
91	depends on HID
92
93config HID_A4TECH
94	tristate "A4 tech mice" if EXPERT
95	depends on HID
96	default !EXPERT
97	---help---
98	Support for A4 tech X5 and WOP-35 / Trust 450L mice.
99
100config HID_ACRUX
101	tristate "ACRUX game controller support"
102	depends on HID
103	---help---
104	Say Y here if you want to enable support for ACRUX game controllers.
105
106config HID_ACRUX_FF
107	bool "ACRUX force feedback support"
108	depends on HID_ACRUX
109	select INPUT_FF_MEMLESS
110	---help---
111	Say Y here if you want to enable force feedback support for ACRUX
112	game controllers.
113
114config HID_APPLE
115	tristate "Apple {i,Power,Mac}Books" if EXPERT
116	depends on HID
117	default !EXPERT
118	---help---
119	Support for some Apple devices which less or more break
120	HID specification.
121
122	Say Y here if you want support for keyboards of	Apple iBooks, PowerBooks,
123	MacBooks, MacBook Pros and Apple Aluminum.
124
125config HID_APPLEIR
126	tristate "Apple infrared receiver"
127	depends on (USB_HID)
128	---help---
129	Support for Apple infrared remote control. All the Apple computers from
130	  2005 onwards include such a port, except the unibody Macbook (2009),
131	  and Mac Pros. This receiver is also used in the Apple TV set-top box
132	  prior to the 2010 model.
133
134	Say Y here if you want support for Apple infrared remote control.
135
136config HID_AUREAL
137	tristate "Aureal"
138	depends on HID
139	---help---
140	Support for Aureal Cy se W-01RN Remote Controller and other Aureal derived remotes.
141
142config HID_BELKIN
143	tristate "Belkin Flip KVM and Wireless keyboard" if EXPERT
144	depends on HID
145	default !EXPERT
146	---help---
147	Support for Belkin Flip KVM and Wireless keyboard.
148
149config HID_CHERRY
150	tristate "Cherry Cymotion keyboard" if EXPERT
151	depends on HID
152	default !EXPERT
153	---help---
154	Support for Cherry Cymotion keyboard.
155
156config HID_CHICONY
157	tristate "Chicony Tactical pad" if EXPERT
158	depends on HID
159	default !EXPERT
160	---help---
161	Support for Chicony Tactical pad.
162
163config HID_PRODIKEYS
164	tristate "Prodikeys PC-MIDI Keyboard support"
165	depends on HID && SND
166	select SND_RAWMIDI
167	---help---
168	Support for Prodikeys PC-MIDI Keyboard device support.
169	Say Y here to enable support for this device.
170	- Prodikeys PC-MIDI keyboard.
171	  The Prodikeys PC-MIDI acts as a USB Audio device, with one MIDI
172	  input and one MIDI output. These MIDI jacks appear as
173	  a sound "card" in the ALSA sound system.
174	  Note: if you say N here, this device will still function as a basic
175	  multimedia keyboard, but will lack support for the musical keyboard
176	  and some additional multimedia keys.
177
178config HID_CYPRESS
179	tristate "Cypress mouse and barcode readers" if EXPERT
180	depends on HID
181	default !EXPERT
182	---help---
183	Support for cypress mouse and barcode readers.
184
185config HID_DRAGONRISE
186	tristate "DragonRise Inc. game controller"
187	depends on HID
188	---help---
189	Say Y here if you have DragonRise Inc. game controllers.
190	These might be branded as:
191	- Tesun USB-703
192	- Media-tech MT1504 "Rogue"
193	- DVTech JS19 "Gear"
194	- Defender Game Master
195
196config DRAGONRISE_FF
197	bool "DragonRise Inc. force feedback"
198	depends on HID_DRAGONRISE
199	select INPUT_FF_MEMLESS
200	---help---
201	Say Y here if you want to enable force feedback support for DragonRise Inc.
202	game controllers.
203
204config HID_EMS_FF
205	tristate "EMS Production Inc. force feedback support"
206	depends on HID
207	select INPUT_FF_MEMLESS
208	---help---
209	Say Y here if you want to enable force feedback support for devices by
210	EMS Production Ltd.
211	Currently the following devices are known to be supported:
212	 - Trio Linker Plus II
213
214config HID_ELECOM
215	tristate "ELECOM BM084 bluetooth mouse"
216	depends on HID
217	---help---
218	Support for the ELECOM BM084 (bluetooth mouse).
219
220config HID_ELO
221	tristate "ELO USB 4000/4500 touchscreen"
222	depends on USB_HID
223	---help---
224	Support for the ELO USB 4000/4500 touchscreens. Note that this is for
225	different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
226
227config HID_EZKEY
228	tristate "Ezkey BTC 8193 keyboard" if EXPERT
229	depends on HID
230	default !EXPERT
231	---help---
232	Support for Ezkey BTC 8193 keyboard.
233
234config HID_HOLTEK
235	tristate "Holtek HID devices"
236	depends on USB_HID
237	---help---
238	Support for Holtek based devices:
239	  - Holtek On Line Grip based game controller
240	  - Trust GXT 18 Gaming Keyboard
241	  - Sharkoon Drakonia / Perixx MX-2000 gaming mice
242	  - Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
243	    Zalman ZM-GM1
244	  - SHARKOON DarkGlider Gaming mouse
245
246config HOLTEK_FF
247	bool "Holtek On Line Grip force feedback support"
248	depends on HID_HOLTEK
249	select INPUT_FF_MEMLESS
250	---help---
251	  Say Y here if you have a Holtek On Line Grip based game controller
252	  and want to have force feedback support for it.
253
254config HID_HUION
255	tristate "Huion tablets"
256	depends on USB_HID
257	---help---
258	Support for Huion 580 tablet.
259
260config HID_KEYTOUCH
261	tristate "Keytouch HID devices"
262	depends on HID
263	---help---
264	Support for Keytouch HID devices not fully compliant with
265	the specification. Currently supported:
266		- Keytouch IEC 60945
267
268config HID_KYE
269	tristate "KYE/Genius devices"
270	depends on HID
271	---help---
272	Support for KYE/Genius devices not fully compliant with HID standard:
273	- Ergo Mouse
274	- EasyPen i405X tablet
275	- MousePen i608X tablet
276	- EasyPen M610X tablet
277
278config HID_UCLOGIC
279	tristate "UC-Logic"
280	depends on HID
281	---help---
282	Support for UC-Logic tablets.
283
284config HID_WALTOP
285	tristate "Waltop"
286	depends on HID
287	---help---
288	Support for Waltop tablets.
289
290config HID_GYRATION
291	tristate "Gyration remote control"
292	depends on HID
293	---help---
294	Support for Gyration remote control.
295
296config HID_ICADE
297	tristate "ION iCade arcade controller"
298	depends on HID
299	---help---
300	Support for the ION iCade arcade controller to work as a joystick.
301
302	To compile this driver as a module, choose M here: the
303	module will be called hid-icade.
304
305config HID_TWINHAN
306	tristate "Twinhan IR remote control"
307	depends on HID
308	---help---
309	Support for Twinhan IR remote control.
310
311config HID_KENSINGTON
312	tristate "Kensington Slimblade Trackball" if EXPERT
313	depends on HID
314	default !EXPERT
315	---help---
316	Support for Kensington Slimblade Trackball.
317
318config HID_LCPOWER
319	tristate "LC-Power"
320	depends on HID
321	---help---
322	Support for LC-Power RC1000MCE RF remote control.
323
324config HID_LENOVO_TPKBD
325	tristate "Lenovo ThinkPad USB Keyboard with TrackPoint"
326	depends on USB_HID
327	select NEW_LEDS
328	select LEDS_CLASS
329	---help---
330	Support for the Lenovo ThinkPad USB Keyboard with TrackPoint.
331
332	Say Y here if you have a Lenovo ThinkPad USB Keyboard with TrackPoint
333	and would like to use device-specific features like changing the
334	sensitivity of the trackpoint, using the microphone mute button or
335	controlling the mute and microphone mute LEDs.
336
337config HID_LOGITECH
338	tristate "Logitech devices" if EXPERT
339	depends on HID
340	default !EXPERT
341	---help---
342	Support for Logitech devices that are not fully compliant with HID standard.
343
344config HID_LOGITECH_DJ
345	tristate "Logitech Unifying receivers full support"
346	depends on HID_LOGITECH
347	---help---
348	Say Y if you want support for Logitech Unifying receivers and devices.
349	Unifying receivers are capable of pairing up to 6 Logitech compliant
350	devices to the same receiver. Without this driver it will be handled by
351	generic USB_HID driver and all incoming events will be multiplexed
352	into a single mouse and a single keyboard device.
353
354config LOGITECH_FF
355	bool "Logitech force feedback support"
356	depends on HID_LOGITECH
357	select INPUT_FF_MEMLESS
358	help
359	  Say Y here if you have one of these devices:
360	  - Logitech WingMan Cordless RumblePad
361	  - Logitech WingMan Cordless RumblePad 2
362	  - Logitech WingMan Force 3D
363	  - Logitech Formula Force EX
364	  - Logitech WingMan Formula Force GP
365	  - Logitech MOMO Force wheel
366
367	  and if you want to enable force feedback for them.
368	  Note: if you say N here, this device will still be supported, but without
369	  force feedback.
370
371config LOGIRUMBLEPAD2_FF
372	bool "Logitech RumblePad/Rumblepad 2 force feedback support"
373	depends on HID_LOGITECH
374	select INPUT_FF_MEMLESS
375	help
376	  Say Y here if you want to enable force feedback support for Logitech
377	  RumblePad and Rumblepad 2 devices.
378
379config LOGIG940_FF
380	bool "Logitech Flight System G940 force feedback support"
381	depends on HID_LOGITECH
382	select INPUT_FF_MEMLESS
383	help
384	  Say Y here if you want to enable force feedback support for Logitech
385	  Flight System G940 devices.
386
387config LOGIWHEELS_FF
388	bool "Logitech wheels configuration and force feedback support"
389	depends on HID_LOGITECH
390	select INPUT_FF_MEMLESS
391	default LOGITECH_FF
392	help
393	  Say Y here if you want to enable force feedback and range setting
394	  support for following Logitech wheels:
395	  - Logitech Driving Force
396	  - Logitech Driving Force Pro
397	  - Logitech Driving Force GT
398	  - Logitech G25
399	  - Logitech G27
400	  - Logitech MOMO/MOMO 2
401	  - Logitech Formula Force EX
402
403config HID_MAGICMOUSE
404	tristate "Apple Magic Mouse/Trackpad multi-touch support"
405	depends on HID
406	---help---
407	Support for the Apple Magic Mouse/Trackpad multi-touch.
408
409	Say Y here if you want support for the multi-touch features of the
410	Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
411
412config HID_MICROSOFT
413	tristate "Microsoft non-fully HID-compliant devices" if EXPERT
414	depends on HID
415	default !EXPERT
416	---help---
417	Support for Microsoft devices that are not fully compliant with HID standard.
418
419config HID_MONTEREY
420	tristate "Monterey Genius KB29E keyboard" if EXPERT
421	depends on HID
422	default !EXPERT
423	---help---
424	Support for Monterey Genius KB29E.
425
426config HID_MULTITOUCH
427	tristate "HID Multitouch panels"
428	depends on HID
429	---help---
430	  Generic support for HID multitouch panels.
431
432	  Say Y here if you have one of the following devices:
433	  - 3M PCT touch screens
434	  - ActionStar dual touch panels
435	  - Atmel panels
436	  - Cando dual touch panels
437	  - Chunghwa panels
438	  - CVTouch panels
439	  - Cypress TrueTouch panels
440	  - Elo TouchSystems IntelliTouch Plus panels
441	  - GeneralTouch 'Sensing Win7-TwoFinger' panels
442	  - GoodTouch panels
443	  - Hanvon dual touch panels
444	  - Ilitek dual touch panels
445	  - IrTouch Infrared USB panels
446	  - LG Display panels (Dell ST2220Tc)
447	  - Lumio CrystalTouch panels
448	  - MosArt dual-touch panels
449	  - Panasonic multitouch panels
450	  - PenMount dual touch panels
451	  - Perixx Peripad 701 touchpad
452	  - PixArt optical touch screen
453	  - Pixcir dual touch panels
454	  - Quanta panels
455	  - eGalax dual-touch panels, including the Joojoo and Wetab tablets
456	  - Stantum multitouch panels
457	  - Touch International Panels
458	  - Unitec Panels
459	  - XAT optical touch panels
460	  - Xiroku optical touch panels
461	  - Zytronic touch panels
462
463	  If unsure, say N.
464
465	  To compile this driver as a module, choose M here: the
466	  module will be called hid-multitouch.
467
468config HID_NTRIG
469	tristate "N-Trig touch screen"
470	depends on USB_HID
471	---help---
472	Support for N-Trig touch screen.
473
474config HID_ORTEK
475	tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
476	depends on HID
477	---help---
478	There are certain devices which have LogicalMaximum wrong in the keyboard
479	usage page of their report descriptor. The most prevailing ones so far
480	are manufactured by Ortek, thus the name of the driver. Currently
481	supported devices by this driver are
482
483	   - Ortek PKB-1700
484	   - Ortek WKB-2000
485	   - Skycable wireless presenter
486
487config HID_PANTHERLORD
488	tristate "Pantherlord/GreenAsia game controller"
489	depends on HID
490	---help---
491	  Say Y here if you have a PantherLord/GreenAsia based game controller
492	  or adapter.
493
494config PANTHERLORD_FF
495	bool "Pantherlord force feedback support"
496	depends on HID_PANTHERLORD
497	select INPUT_FF_MEMLESS
498	---help---
499	  Say Y here if you have a PantherLord/GreenAsia based game controller
500	  or adapter and want to enable force feedback support for it.
501
502config HID_PETALYNX
503	tristate "Petalynx Maxter remote control"
504	depends on HID
505	---help---
506	Support for Petalynx Maxter remote control.
507
508config HID_PICOLCD
509	tristate "PicoLCD (graphic version)"
510	depends on HID
511	---help---
512	  This provides support for Minibox PicoLCD devices, currently
513	  only the graphical ones are supported.
514
515	  This includes support for the following device features:
516	  - Keypad
517	  - Switching between Firmware and Flash mode
518	  - EEProm / Flash access     (via debugfs)
519	  Features selectively enabled:
520	  - Framebuffer for monochrome 256x64 display
521	  - Backlight control
522	  - Contrast control
523	  - General purpose outputs
524	  Features that are not (yet) supported:
525	  - IR
526
527config HID_PICOLCD_FB
528	bool "Framebuffer support" if EXPERT
529	default !EXPERT
530	depends on HID_PICOLCD
531	depends on HID_PICOLCD=FB || FB=y
532	select FB_DEFERRED_IO
533	select FB_SYS_FILLRECT
534	select FB_SYS_COPYAREA
535	select FB_SYS_IMAGEBLIT
536	select FB_SYS_FOPS
537	---help---
538	  Provide access to PicoLCD's 256x64 monochrome display via a
539	  framebuffer device.
540
541config HID_PICOLCD_BACKLIGHT
542	bool "Backlight control" if EXPERT
543	default !EXPERT
544	depends on HID_PICOLCD
545	depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
546	---help---
547	  Provide access to PicoLCD's backlight control via backlight
548	  class.
549
550config HID_PICOLCD_LCD
551	bool "Contrast control" if EXPERT
552	default !EXPERT
553	depends on HID_PICOLCD
554	depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
555	---help---
556	  Provide access to PicoLCD's LCD contrast via lcd class.
557
558config HID_PICOLCD_LEDS
559	bool "GPO via leds class" if EXPERT
560	default !EXPERT
561	depends on HID_PICOLCD
562	depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
563	---help---
564	  Provide access to PicoLCD's GPO pins via leds class.
565
566config HID_PICOLCD_CIR
567	bool "CIR via RC class" if EXPERT
568	default !EXPERT
569	depends on HID_PICOLCD
570	depends on HID_PICOLCD=RC_CORE || RC_CORE=y
571	---help---
572	  Provide access to PicoLCD's CIR interface via remote control (LIRC).
573
574config HID_PRIMAX
575	tristate "Primax non-fully HID-compliant devices"
576	depends on HID
577	---help---
578	Support for Primax devices that are not fully compliant with the
579	HID standard.
580
581config HID_ROCCAT
582	tristate "Roccat device support"
583	depends on USB_HID
584	---help---
585	Support for Roccat devices.
586	Say Y here if you have a Roccat mouse or keyboard and want
587	support for its special functionalities.
588
589config HID_SAITEK
590	tristate "Saitek non-fully HID-compliant devices"
591	depends on HID
592	---help---
593	Support for Saitek devices that are not fully compliant with the
594	HID standard.
595
596	Currently only supports the PS1000 controller.
597
598config HID_SAMSUNG
599	tristate "Samsung InfraRed remote control or keyboards"
600	depends on HID
601	---help---
602	Support for Samsung InfraRed remote control or keyboards.
603
604config HID_SONY
605	tristate "Sony PS2/3 accessories"
606	depends on USB_HID
607	depends on NEW_LEDS
608	depends on LEDS_CLASS
609	---help---
610	Support for
611
612	  * Sony PS3 6-axis controllers
613	  * Buzz controllers
614	  * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
615	  * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
616
617config HID_SPEEDLINK
618	tristate "Speedlink VAD Cezanne mouse support"
619	depends on HID
620	---help---
621	Support for Speedlink Vicious and Divine Cezanne mouse.
622
623config HID_STEELSERIES
624	tristate "Steelseries SRW-S1 steering wheel support"
625	depends on HID
626	---help---
627	Support for Steelseries SRW-S1 steering wheel
628
629config HID_SUNPLUS
630	tristate "Sunplus wireless desktop"
631	depends on HID
632	---help---
633	Support for Sunplus wireless desktop.
634
635config HID_GREENASIA
636	tristate "GreenAsia (Product ID 0x12) game controller support"
637	depends on HID
638	---help---
639	  Say Y here if you have a GreenAsia (Product ID 0x12) based game
640	  controller or adapter.
641
642config GREENASIA_FF
643	bool "GreenAsia (Product ID 0x12) force feedback support"
644	depends on HID_GREENASIA
645	select INPUT_FF_MEMLESS
646	---help---
647	Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
648	(like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
649	and want to enable force feedback support for it.
650
651config HID_HYPERV_MOUSE
652	tristate "Microsoft Hyper-V mouse driver"
653	depends on HYPERV
654	---help---
655	Select this option to enable the Hyper-V mouse driver.
656
657config HID_SMARTJOYPLUS
658	tristate "SmartJoy PLUS PS2/USB adapter support"
659	depends on HID
660	---help---
661	Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
662	Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
663
664	Note that DDR (Dance Dance Revolution) mode is not supported, nor
665	is pressure sensitive buttons on the pro models.
666
667config SMARTJOYPLUS_FF
668	bool "SmartJoy PLUS PS2/USB adapter force feedback support"
669	depends on HID_SMARTJOYPLUS
670	select INPUT_FF_MEMLESS
671	---help---
672	Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
673	enable force feedback support for it.
674
675config HID_TIVO
676	tristate "TiVo Slide Bluetooth remote control support"
677	depends on HID
678	---help---
679	Say Y if you have a TiVo Slide Bluetooth remote control.
680
681config HID_TOPSEED
682	tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
683	depends on HID
684	---help---
685	Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
686	CLLRCMCE remote control.
687
688config HID_THINGM
689	tristate "ThingM blink(1) USB RGB LED"
690	depends on HID
691	depends on LEDS_CLASS
692	---help---
693	Support for the ThingM blink(1) USB RGB LED. This driver registers a
694	Linux LED class instance, plus additional sysfs attributes to control
695	RGB colors, fade time and playing. The device is exposed through hidraw
696	to access other functions.
697
698config HID_THRUSTMASTER
699	tristate "ThrustMaster devices support"
700	depends on HID
701	---help---
702	  Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
703	  a THRUSTMASTER Ferrari GT Rumble Wheel.
704
705config THRUSTMASTER_FF
706	bool "ThrustMaster devices force feedback support"
707	depends on HID_THRUSTMASTER
708	select INPUT_FF_MEMLESS
709	---help---
710	  Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
711	  a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
712	  Rumble Force or Force Feedback Wheel.
713
714config HID_WACOM
715	tristate "Wacom Bluetooth devices support"
716	depends on HID
717	depends on LEDS_CLASS
718	select POWER_SUPPLY
719	---help---
720	Support for Wacom Graphire Bluetooth and Intuos4 WL tablets.
721
722config HID_WIIMOTE
723	tristate "Nintendo Wii / Wii U peripherals"
724	depends on HID
725	depends on LEDS_CLASS
726	select POWER_SUPPLY
727	select INPUT_FF_MEMLESS
728	---help---
729	Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
730	devices are the Wii Remote and its extension devices, but also devices
731	based on the Wii Remote like the Wii U Pro Controller or the
732	Wii Balance Board.
733
734	Support for all official Nintendo extensions is available, however, 3rd
735	party extensions might not be supported. Please report these devices to:
736	  http://github.com/dvdhrm/xwiimote/issues
737
738	Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
739	the Wii U Gamepad) might be supported in the future. But currently
740	support is limited to Bluetooth based devices.
741
742	If unsure, say N.
743
744	To compile this driver as a module, choose M here: the
745	module will be called hid-wiimote.
746
747config HID_XINMO
748	tristate "Xin-Mo non-fully compliant devices"
749	depends on HID
750	---help---
751	Support for Xin-Mo devices that are not fully compliant with the HID
752	standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
753	if you have a Xin-Mo Dual Arcade controller.
754
755config HID_ZEROPLUS
756	tristate "Zeroplus based game controller support"
757	depends on HID
758	---help---
759	  Say Y here if you have a Zeroplus based game controller.
760
761config ZEROPLUS_FF
762	bool "Zeroplus based game controller force feedback support"
763	depends on HID_ZEROPLUS
764	select INPUT_FF_MEMLESS
765	---help---
766	  Say Y here if you have a Zeroplus based game controller and want
767	  to have force feedback support for it.
768
769config HID_ZYDACRON
770	tristate "Zydacron remote control support"
771	depends on HID
772	---help---
773	Support for Zydacron remote control.
774
775config HID_SENSOR_HUB
776	tristate "HID Sensors framework support"
777	depends on HID
778	select MFD_CORE
779	default n
780	---help---
781	  Support for HID Sensor framework. This creates a MFD instance
782	  for a sensor hub and identifies all the sensors connected to it.
783	  Each sensor is registered as a MFD cell, so that sensor specific
784	  processing can be done in a separate driver. Each sensor
785	  drivers can use the service provided by this driver to register
786	  for events and handle data streams. Each sensor driver can format
787	  data and present to user mode using input or IIO interface.
788
789endmenu
790
791endif # HID
792
793source "drivers/hid/usbhid/Kconfig"
794
795source "drivers/hid/i2c-hid/Kconfig"
796
797endmenu
798