drivers/hid/Kconfig

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