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