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