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