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