HID: replace strict_strtoul() with kstrtoul()
[deliverable/linux.git] / drivers / hid / Kconfig
... / ...
CommitLineData
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
245config HOLTEK_FF
246 bool "Holtek On Line Grip force feedback support"
247 depends on HID_HOLTEK
248 select INPUT_FF_MEMLESS
249 ---help---
250 Say Y here if you have a Holtek On Line Grip based game controller
251 and want to have force feedback support for it.
252
253config HID_HUION
254 tristate "Huion tablets"
255 depends on USB_HID
256 ---help---
257 Support for Huion 580 tablet.
258
259config HID_KEYTOUCH
260 tristate "Keytouch HID devices"
261 depends on HID
262 ---help---
263 Support for Keytouch HID devices not fully compliant with
264 the specification. Currently supported:
265 - Keytouch IEC 60945
266
267config HID_KYE
268 tristate "KYE/Genius devices"
269 depends on HID
270 ---help---
271 Support for KYE/Genius devices not fully compliant with HID standard:
272 - Ergo Mouse
273 - EasyPen i405X tablet
274 - MousePen i608X tablet
275 - EasyPen M610X tablet
276
277config HID_UCLOGIC
278 tristate "UC-Logic"
279 depends on HID
280 ---help---
281 Support for UC-Logic tablets.
282
283config HID_WALTOP
284 tristate "Waltop"
285 depends on HID
286 ---help---
287 Support for Waltop tablets.
288
289config HID_GYRATION
290 tristate "Gyration remote control"
291 depends on HID
292 ---help---
293 Support for Gyration remote control.
294
295config HID_ICADE
296 tristate "ION iCade arcade controller"
297 depends on HID
298 ---help---
299 Support for the ION iCade arcade controller to work as a joystick.
300
301 To compile this driver as a module, choose M here: the
302 module will be called hid-icade.
303
304config HID_TWINHAN
305 tristate "Twinhan IR remote control"
306 depends on HID
307 ---help---
308 Support for Twinhan IR remote control.
309
310config HID_KENSINGTON
311 tristate "Kensington Slimblade Trackball" if EXPERT
312 depends on HID
313 default !EXPERT
314 ---help---
315 Support for Kensington Slimblade Trackball.
316
317config HID_LCPOWER
318 tristate "LC-Power"
319 depends on HID
320 ---help---
321 Support for LC-Power RC1000MCE RF remote control.
322
323config HID_LENOVO_TPKBD
324 tristate "Lenovo ThinkPad USB Keyboard with TrackPoint"
325 depends on USB_HID
326 select NEW_LEDS
327 select LEDS_CLASS
328 ---help---
329 Support for the Lenovo ThinkPad USB Keyboard with TrackPoint.
330
331 Say Y here if you have a Lenovo ThinkPad USB Keyboard with TrackPoint
332 and would like to use device-specific features like changing the
333 sensitivity of the trackpoint, using the microphone mute button or
334 controlling the mute and microphone mute LEDs.
335
336config HID_LOGITECH
337 tristate "Logitech devices" if EXPERT
338 depends on HID
339 default !EXPERT
340 ---help---
341 Support for Logitech devices that are not fully compliant with HID standard.
342
343config HID_LOGITECH_DJ
344 tristate "Logitech Unifying receivers full support"
345 depends on HID_LOGITECH
346 ---help---
347 Say Y if you want support for Logitech Unifying receivers and devices.
348 Unifying receivers are capable of pairing up to 6 Logitech compliant
349 devices to the same receiver. Without this driver it will be handled by
350 generic USB_HID driver and all incoming events will be multiplexed
351 into a single mouse and a single keyboard device.
352
353config LOGITECH_FF
354 bool "Logitech force feedback support"
355 depends on HID_LOGITECH
356 select INPUT_FF_MEMLESS
357 help
358 Say Y here if you have one of these devices:
359 - Logitech WingMan Cordless RumblePad
360 - Logitech WingMan Cordless RumblePad 2
361 - Logitech WingMan Force 3D
362 - Logitech Formula Force EX
363 - Logitech WingMan Formula Force GP
364 - Logitech MOMO Force wheel
365
366 and if you want to enable force feedback for them.
367 Note: if you say N here, this device will still be supported, but without
368 force feedback.
369
370config LOGIRUMBLEPAD2_FF
371 bool "Logitech RumblePad/Rumblepad 2 force feedback support"
372 depends on HID_LOGITECH
373 select INPUT_FF_MEMLESS
374 help
375 Say Y here if you want to enable force feedback support for Logitech
376 RumblePad and Rumblepad 2 devices.
377
378config LOGIG940_FF
379 bool "Logitech Flight System G940 force feedback support"
380 depends on HID_LOGITECH
381 select INPUT_FF_MEMLESS
382 help
383 Say Y here if you want to enable force feedback support for Logitech
384 Flight System G940 devices.
385
386config LOGIWHEELS_FF
387 bool "Logitech wheels configuration and force feedback support"
388 depends on HID_LOGITECH
389 select INPUT_FF_MEMLESS
390 default LOGITECH_FF
391 help
392 Say Y here if you want to enable force feedback and range setting
393 support for following Logitech wheels:
394 - Logitech Driving Force
395 - Logitech Driving Force Pro
396 - Logitech Driving Force GT
397 - Logitech G25
398 - Logitech G27
399 - Logitech MOMO/MOMO 2
400 - Logitech Formula Force EX
401
402config HID_MAGICMOUSE
403 tristate "Apple Magic Mouse/Trackpad multi-touch support"
404 depends on HID
405 ---help---
406 Support for the Apple Magic Mouse/Trackpad multi-touch.
407
408 Say Y here if you want support for the multi-touch features of the
409 Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
410
411config HID_MICROSOFT
412 tristate "Microsoft non-fully HID-compliant devices" if EXPERT
413 depends on HID
414 default !EXPERT
415 ---help---
416 Support for Microsoft devices that are not fully compliant with HID standard.
417
418config HID_MONTEREY
419 tristate "Monterey Genius KB29E keyboard" if EXPERT
420 depends on HID
421 default !EXPERT
422 ---help---
423 Support for Monterey Genius KB29E.
424
425config HID_MULTITOUCH
426 tristate "HID Multitouch panels"
427 depends on HID
428 ---help---
429 Generic support for HID multitouch panels.
430
431 Say Y here if you have one of the following devices:
432 - 3M PCT touch screens
433 - ActionStar dual touch panels
434 - Atmel panels
435 - Cando dual touch panels
436 - Chunghwa panels
437 - CVTouch panels
438 - Cypress TrueTouch panels
439 - Elo TouchSystems IntelliTouch Plus panels
440 - GeneralTouch 'Sensing Win7-TwoFinger' panels
441 - GoodTouch panels
442 - Hanvon dual touch panels
443 - Ilitek dual touch panels
444 - IrTouch Infrared USB panels
445 - LG Display panels (Dell ST2220Tc)
446 - Lumio CrystalTouch panels
447 - MosArt dual-touch panels
448 - Panasonic multitouch panels
449 - PenMount dual touch panels
450 - Perixx Peripad 701 touchpad
451 - PixArt optical touch screen
452 - Pixcir dual touch panels
453 - Quanta panels
454 - eGalax dual-touch panels, including the Joojoo and Wetab tablets
455 - Stantum multitouch panels
456 - Touch International Panels
457 - Unitec Panels
458 - XAT optical touch panels
459 - Xiroku optical touch panels
460 - Zytronic touch panels
461
462 If unsure, say N.
463
464 To compile this driver as a module, choose M here: the
465 module will be called hid-multitouch.
466
467config HID_NTRIG
468 tristate "N-Trig touch screen"
469 depends on USB_HID
470 ---help---
471 Support for N-Trig touch screen.
472
473config HID_ORTEK
474 tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
475 depends on HID
476 ---help---
477 There are certain devices which have LogicalMaximum wrong in the keyboard
478 usage page of their report descriptor. The most prevailing ones so far
479 are manufactured by Ortek, thus the name of the driver. Currently
480 supported devices by this driver are
481
482 - Ortek PKB-1700
483 - Ortek WKB-2000
484 - Skycable wireless presenter
485
486config HID_PANTHERLORD
487 tristate "Pantherlord/GreenAsia game controller"
488 depends on HID
489 ---help---
490 Say Y here if you have a PantherLord/GreenAsia based game controller
491 or adapter.
492
493config PANTHERLORD_FF
494 bool "Pantherlord force feedback support"
495 depends on HID_PANTHERLORD
496 select INPUT_FF_MEMLESS
497 ---help---
498 Say Y here if you have a PantherLord/GreenAsia based game controller
499 or adapter and want to enable force feedback support for it.
500
501config HID_PETALYNX
502 tristate "Petalynx Maxter remote control"
503 depends on HID
504 ---help---
505 Support for Petalynx Maxter remote control.
506
507config HID_PICOLCD
508 tristate "PicoLCD (graphic version)"
509 depends on HID
510 ---help---
511 This provides support for Minibox PicoLCD devices, currently
512 only the graphical ones are supported.
513
514 This includes support for the following device features:
515 - Keypad
516 - Switching between Firmware and Flash mode
517 - EEProm / Flash access (via debugfs)
518 Features selectively enabled:
519 - Framebuffer for monochrome 256x64 display
520 - Backlight control
521 - Contrast control
522 - General purpose outputs
523 Features that are not (yet) supported:
524 - IR
525
526config HID_PICOLCD_FB
527 bool "Framebuffer support" if EXPERT
528 default !EXPERT
529 depends on HID_PICOLCD
530 depends on HID_PICOLCD=FB || FB=y
531 select FB_DEFERRED_IO
532 select FB_SYS_FILLRECT
533 select FB_SYS_COPYAREA
534 select FB_SYS_IMAGEBLIT
535 select FB_SYS_FOPS
536 ---help---
537 Provide access to PicoLCD's 256x64 monochrome display via a
538 framebuffer device.
539
540config HID_PICOLCD_BACKLIGHT
541 bool "Backlight control" if EXPERT
542 default !EXPERT
543 depends on HID_PICOLCD
544 depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
545 ---help---
546 Provide access to PicoLCD's backlight control via backlight
547 class.
548
549config HID_PICOLCD_LCD
550 bool "Contrast control" if EXPERT
551 default !EXPERT
552 depends on HID_PICOLCD
553 depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
554 ---help---
555 Provide access to PicoLCD's LCD contrast via lcd class.
556
557config HID_PICOLCD_LEDS
558 bool "GPO via leds class" if EXPERT
559 default !EXPERT
560 depends on HID_PICOLCD
561 depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
562 ---help---
563 Provide access to PicoLCD's GPO pins via leds class.
564
565config HID_PICOLCD_CIR
566 bool "CIR via RC class" if EXPERT
567 default !EXPERT
568 depends on HID_PICOLCD
569 depends on HID_PICOLCD=RC_CORE || RC_CORE=y
570 ---help---
571 Provide access to PicoLCD's CIR interface via remote control (LIRC).
572
573config HID_PRIMAX
574 tristate "Primax non-fully HID-compliant devices"
575 depends on HID
576 ---help---
577 Support for Primax devices that are not fully compliant with the
578 HID standard.
579
580config HID_ROCCAT
581 tristate "Roccat device support"
582 depends on USB_HID
583 ---help---
584 Support for Roccat devices.
585 Say Y here if you have a Roccat mouse or keyboard and want
586 support for its special functionalities.
587
588config HID_SAITEK
589 tristate "Saitek non-fully HID-compliant devices"
590 depends on HID
591 ---help---
592 Support for Saitek devices that are not fully compliant with the
593 HID standard.
594
595 Currently only supports the PS1000 controller.
596
597config HID_SAMSUNG
598 tristate "Samsung InfraRed remote control or keyboards"
599 depends on HID
600 ---help---
601 Support for Samsung InfraRed remote control or keyboards.
602
603config HID_SONY
604 tristate "Sony PS2/3 accessories"
605 depends on USB_HID
606 depends on NEW_LEDS
607 depends on LEDS_CLASS
608 ---help---
609 Support for
610
611 * Sony PS3 6-axis controllers
612 * Buzz controllers
613 * Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
614 * Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
615
616config HID_SPEEDLINK
617 tristate "Speedlink VAD Cezanne mouse support"
618 depends on HID
619 ---help---
620 Support for Speedlink Vicious and Divine Cezanne mouse.
621
622config HID_STEELSERIES
623 tristate "Steelseries SRW-S1 steering wheel support"
624 depends on HID
625 ---help---
626 Support for Steelseries SRW-S1 steering wheel
627
628config HID_SUNPLUS
629 tristate "Sunplus wireless desktop"
630 depends on HID
631 ---help---
632 Support for Sunplus wireless desktop.
633
634config HID_GREENASIA
635 tristate "GreenAsia (Product ID 0x12) game controller support"
636 depends on HID
637 ---help---
638 Say Y here if you have a GreenAsia (Product ID 0x12) based game
639 controller or adapter.
640
641config GREENASIA_FF
642 bool "GreenAsia (Product ID 0x12) force feedback support"
643 depends on HID_GREENASIA
644 select INPUT_FF_MEMLESS
645 ---help---
646 Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
647 (like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
648 and want to enable force feedback support for it.
649
650config HID_HYPERV_MOUSE
651 tristate "Microsoft Hyper-V mouse driver"
652 depends on HYPERV
653 ---help---
654 Select this option to enable the Hyper-V mouse driver.
655
656config HID_SMARTJOYPLUS
657 tristate "SmartJoy PLUS PS2/USB adapter support"
658 depends on HID
659 ---help---
660 Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
661 Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
662
663 Note that DDR (Dance Dance Revolution) mode is not supported, nor
664 is pressure sensitive buttons on the pro models.
665
666config SMARTJOYPLUS_FF
667 bool "SmartJoy PLUS PS2/USB adapter force feedback support"
668 depends on HID_SMARTJOYPLUS
669 select INPUT_FF_MEMLESS
670 ---help---
671 Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
672 enable force feedback support for it.
673
674config HID_TIVO
675 tristate "TiVo Slide Bluetooth remote control support"
676 depends on HID
677 ---help---
678 Say Y if you have a TiVo Slide Bluetooth remote control.
679
680config HID_TOPSEED
681 tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
682 depends on HID
683 ---help---
684 Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
685 CLLRCMCE remote control.
686
687config HID_THINGM
688 tristate "ThingM blink(1) USB RGB LED"
689 depends on HID
690 depends on LEDS_CLASS
691 ---help---
692 Support for the ThingM blink(1) USB RGB LED. This driver registers a
693 Linux LED class instance, plus additional sysfs attributes to control
694 RGB colors, fade time and playing. The device is exposed through hidraw
695 to access other functions.
696
697config HID_THRUSTMASTER
698 tristate "ThrustMaster devices support"
699 depends on HID
700 ---help---
701 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
702 a THRUSTMASTER Ferrari GT Rumble Wheel.
703
704config THRUSTMASTER_FF
705 bool "ThrustMaster devices force feedback support"
706 depends on HID_THRUSTMASTER
707 select INPUT_FF_MEMLESS
708 ---help---
709 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
710 a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
711 Rumble Force or Force Feedback Wheel.
712
713config HID_WACOM
714 tristate "Wacom Bluetooth devices support"
715 depends on HID
716 depends on LEDS_CLASS
717 select POWER_SUPPLY
718 ---help---
719 Support for Wacom Graphire Bluetooth and Intuos4 WL tablets.
720
721config HID_WIIMOTE
722 tristate "Nintendo Wii / Wii U peripherals"
723 depends on HID
724 depends on LEDS_CLASS
725 select POWER_SUPPLY
726 select INPUT_FF_MEMLESS
727 ---help---
728 Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
729 devices are the Wii Remote and its extension devices, but also devices
730 based on the Wii Remote like the Wii U Pro Controller or the
731 Wii Balance Board.
732
733 Support for all official Nintendo extensions is available, however, 3rd
734 party extensions might not be supported. Please report these devices to:
735 http://github.com/dvdhrm/xwiimote/issues
736
737 Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
738 the Wii U Gamepad) might be supported in the future. But currently
739 support is limited to Bluetooth based devices.
740
741 If unsure, say N.
742
743 To compile this driver as a module, choose M here: the
744 module will be called hid-wiimote.
745
746config HID_ZEROPLUS
747 tristate "Zeroplus based game controller support"
748 depends on HID
749 ---help---
750 Say Y here if you have a Zeroplus based game controller.
751
752config ZEROPLUS_FF
753 bool "Zeroplus based game controller force feedback support"
754 depends on HID_ZEROPLUS
755 select INPUT_FF_MEMLESS
756 ---help---
757 Say Y here if you have a Zeroplus based game controller and want
758 to have force feedback support for it.
759
760config HID_ZYDACRON
761 tristate "Zydacron remote control support"
762 depends on HID
763 ---help---
764 Support for Zydacron remote control.
765
766config HID_SENSOR_HUB
767 tristate "HID Sensors framework support"
768 depends on HID && GENERIC_HARDIRQS
769 select MFD_CORE
770 default n
771 ---help---
772 Support for HID Sensor framework. This creates a MFD instance
773 for a sensor hub and identifies all the sensors connected to it.
774 Each sensor is registered as a MFD cell, so that sensor specific
775 processing can be done in a separate driver. Each sensor
776 drivers can use the service provided by this driver to register
777 for events and handle data streams. Each sensor driver can format
778 data and present to user mode using input or IIO interface.
779
780endmenu
781
782endif # HID
783
784source "drivers/hid/usbhid/Kconfig"
785
786source "drivers/hid/i2c-hid/Kconfig"
787
788endmenu
This page took 0.027204 seconds and 5 git commands to generate.