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