#
# [31mCONFIG_HID[0m driver configuration
#
menu "HID support"
depends on [31mCONFIG_INPUT[0m
config [31mCONFIG_HID[0m
tristate "HID bus support"
depends on [31mCONFIG_INPUT[0m
default y
---help---
[31mCONFIG_A[0m human interface device ([31mCONFIG_HID[0m) is a type of computer device that
interacts directly with and takes input from humans. The term "HID"
most commonly used to refer to the [31mCONFIG_USB[0m-[31mCONFIG_HID[0m specification, but other
devices (such as, but not strictly limited to, Bluetooth) are
designed using [31mCONFIG_HID[0m specification (this involves certain keyboards,
mice, tablets, etc). This option adds the [31mCONFIG_HID[0m bus to the kernel,
together with generic [31mCONFIG_HID[0m layer code. The [31mCONFIG_HID[0m devices are added and
removed from the [31mCONFIG_HID[0m bus by the transport-layer drivers, such as
usbhid ([31mCONFIG_USB_HID[0m) and hidp ([31mCONFIG_BT_HIDP[0m).
For docs and specs, see http://www.usb.org/developers/hidpage/
If unsure, say Y.
if [31mCONFIG_HID[0m
config [31mCONFIG_HID_BATTERY_STRENGTH[0m
bool "Battery level reporting for HID devices"
depends on [31mCONFIG_HID[0m
select [31mCONFIG_POWER_SUPPLY[0m
default n
---help---
This option adds support of reporting battery strength (for [31mCONFIG_HID[0m devices
that support this feature) through power_supply class so that userspace
tools, such as upower, can display it.
config [31mCONFIG_HIDRAW[0m
bool "/dev/hidraw raw HID device support"
depends on [31mCONFIG_HID[0m
---help---
Say Y here if you want to support [31mCONFIG_HID[0m devices (from the [31mCONFIG_USB[0m
specification standpoint) that aren't strictly user interface
devices, like monitor controls and Uninterruptable Power Supplies.
This module supports these devices separately using a separate
event interface on /dev/hidraw.
There is also a /dev/hiddev configuration option in the [31mCONFIG_USB[0m [31mCONFIG_HID[0m
configuration menu. In comparison to hiddev, this device does not process
the hid events at all (no parsing, no lookups). This lets applications
to work on raw hid events when they want to, and avoid using transport-specific
userspace libhid/libusb libraries.
If unsure, say Y.
config [31mCONFIG_UHID[0m
tristate "User-space I/O driver support for HID subsystem"
depends on [31mCONFIG_HID[0m
default n
---help---
Say Y here if you want to provide [31mCONFIG_HID[0m I/O Drivers from user-space.
This allows to write I/O drivers in user-space and feed the data from
the device into the kernel. The kernel parses the [31mCONFIG_HID[0m reports, loads the
corresponding [31mCONFIG_HID[0m Device Driver or provides input devices on top of your
user-space device.
This driver cannot be used to parse [31mCONFIG_HID[0m-reports in user-space and write
special [31mCONFIG_HID[0m-drivers. You should use hidraw for that.
Instead, this driver allows to write the transport-layer driver in
user-space like [31mCONFIG_USB[0m-[31mCONFIG_HID[0m and Bluetooth-[31mCONFIG_HID[0m do in kernel-space.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called uhid.
config [31mCONFIG_HID_GENERIC[0m
tristate "Generic HID driver"
depends on [31mCONFIG_HID[0m
default [31mCONFIG_HID[0m
---help---
Support for generic devices on the [31mCONFIG_HID[0m bus. This includes most
keyboards and mice, joysticks, tablets and digitizers.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called hid-generic.
If unsure, say Y.
menu "Special HID drivers"
depends on [31mCONFIG_HID[0m
config [31mCONFIG_HID_A4TECH[0m
tristate "A4 tech mice"
depends on [31mCONFIG_HID[0m
default ![31mCONFIG_EXPERT[0m
---help---
Support for A4 tech X5 and WOP-35 / Trust 450L mice.
config [31mCONFIG_HID_ACRUX[0m
tristate "ACRUX game controller support"
depends on [31mCONFIG_HID[0m
---help---
Say Y here if you want to enable support for ACRUX game controllers.
config [31mCONFIG_HID_ACRUX_FF[0m
bool "ACRUX force feedback support"
depends on [31mCONFIG_HID_ACRUX[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
---help---
Say Y here if you want to enable force feedback support for ACRUX
game controllers.
config [31mCONFIG_HID_APPLE[0m
tristate "Apple {i,Power,Mac}Books"
depends on [31mCONFIG_HID[0m
default ![31mCONFIG_EXPERT[0m
---help---
Support for some Apple devices which less or more break
[31mCONFIG_HID[0m specification.
Say Y here if you want support for keyboards of Apple iBooks, PowerBooks,
MacBooks, MacBook Pros and Apple Aluminum.
config [31mCONFIG_HID_APPLEIR[0m
tristate "Apple infrared receiver"
depends on ([31mCONFIG_USB_HID[0m)
---help---
Support for Apple infrared remote control. All the Apple computers from
2005 onwards include such a port, except the unibody Macbook (2009),
and Mac Pros. This receiver is also used in the Apple TV set-top box
prior to the 2010 model.
Say Y here if you want support for Apple infrared remote control.
config [31mCONFIG_HID_ASUS[0m
tristate "Asus"
depends on [31mCONFIG_I2C_HID[0m
---help---
Support for Asus notebook built-in keyboard and touchpad via i2c.
Supported devices:
- EeeBook X205TA
- VivoBook E200HA
config [31mCONFIG_HID_AUREAL[0m
tristate "Aureal"
depends on [31mCONFIG_HID[0m
---help---
Support for Aureal Cy se W-01RN Remote Controller and other Aureal derived remotes.
config [31mCONFIG_HID_BELKIN[0m
tristate "Belkin Flip KVM and Wireless keyboard"
depends on [31mCONFIG_HID[0m
default ![31mCONFIG_EXPERT[0m
---help---
Support for Belkin Flip [31mCONFIG_KVM[0m and Wireless keyboard.
config [31mCONFIG_HID_BETOP_FF[0m
tristate "Betop Production Inc. force feedback support"
depends on [31mCONFIG_USB_HID[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
---help---
Say Y here if you want to enable force feedback support for devices by
BETOP Production Ltd.
Currently the following devices are known to be supported:
- BETOP 2185 PC & BFM MODE
config [31mCONFIG_HID_CHERRY[0m
tristate "Cherry Cymotion keyboard"
depends on [31mCONFIG_HID[0m
default ![31mCONFIG_EXPERT[0m
---help---
Support for Cherry Cymotion keyboard.
config [31mCONFIG_HID_CHICONY[0m
tristate "Chicony Tactical pad"
depends on [31mCONFIG_HID[0m
default ![31mCONFIG_EXPERT[0m
---help---
Support for Chicony Tactical pad.
config [31mCONFIG_HID_CORSAIR[0m
tristate "Corsair devices"
depends on [31mCONFIG_HID[0m && [31mCONFIG_USB[0m && [31mCONFIG_LEDS_CLASS[0m
---help---
Support for Corsair devices that are not fully compliant with the
[31mCONFIG_HID[0m standard.
Supported devices:
- Vengeance K90
config [31mCONFIG_HID_PRODIKEYS[0m
tristate "Prodikeys PC-MIDI Keyboard support"
depends on [31mCONFIG_HID[0m && [31mCONFIG_SND[0m
select [31mCONFIG_SND_RAWMIDI[0m
---help---
Support for Prodikeys PC-MIDI Keyboard device support.
Say Y here to enable support for this device.
- Prodikeys PC-MIDI keyboard.
The Prodikeys PC-MIDI acts as a [31mCONFIG_USB[0m Audio device, with one MIDI
input and one MIDI output. These MIDI jacks appear as
a sound "card" in the ALSA sound system.
Note: if you say N here, this device will still function as a basic
multimedia keyboard, but will lack support for the musical keyboard
and some additional multimedia keys.
config [31mCONFIG_HID_CMEDIA[0m
tristate "CMedia CM6533 HID audio jack controls"
depends on [31mCONFIG_HID[0m
---help---
Support for CMedia CM6533 [31mCONFIG_HID[0m audio jack controls.
config [31mCONFIG_HID_CP2112[0m
tristate "Silicon Labs CP2112 HID USB-to-SMBus Bridge support"
depends on [31mCONFIG_USB_HID[0m && [31mCONFIG_I2C[0m && [31mCONFIG_GPIOLIB[0m && [31mCONFIG_GPIOLIB_IRQCHIP[0m
---help---
Support for Silicon Labs CP2112 [31mCONFIG_HID[0m [31mCONFIG_USB[0m to SMBus Master Bridge.
This is a [31mCONFIG_HID[0m device driver which registers as an i2c adapter
and gpiochip to expose these functions of the CP2112. The
customizable [31mCONFIG_USB[0m descriptor fields are exposed as sysfs attributes.
config [31mCONFIG_HID_CYPRESS[0m
tristate "Cypress mouse and barcode readers"
depends on [31mCONFIG_HID[0m
default ![31mCONFIG_EXPERT[0m
---help---
Support for cypress mouse and barcode readers.
config [31mCONFIG_HID_DRAGONRISE[0m
tristate "DragonRise Inc. game controller"
depends on [31mCONFIG_HID[0m
---help---
Say Y here if you have DragonRise Inc. game controllers.
These might be branded as:
- Tesun [31mCONFIG_USB[0m-703
- Media-tech MT1504 "Rogue"
- DVTech JS19 "Gear"
- Defender Game Master
config [31mCONFIG_DRAGONRISE_FF[0m
bool "DragonRise Inc. force feedback"
depends on [31mCONFIG_HID_DRAGONRISE[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
---help---
Say Y here if you want to enable force feedback support for DragonRise Inc.
game controllers.
config [31mCONFIG_HID_EMS_FF[0m
tristate "EMS Production Inc. force feedback support"
depends on [31mCONFIG_HID[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
---help---
Say Y here if you want to enable force feedback support for devices by
EMS Production Ltd.
Currently the following devices are known to be supported:
- Trio Linker Plus II
config [31mCONFIG_HID_ELECOM[0m
tristate "ELECOM BM084 bluetooth mouse"
depends on [31mCONFIG_HID[0m
---help---
Support for the ELECOM BM084 (bluetooth mouse).
config [31mCONFIG_HID_ELO[0m
tristate "ELO USB 4000/4500 touchscreen"
depends on [31mCONFIG_USB_HID[0m
---help---
Support for the ELO [31mCONFIG_USB[0m 4000/4500 touchscreens. Note that this is for
different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
config [31mCONFIG_HID_EZKEY[0m
tristate "Ezkey BTC 8193 keyboard"
depends on [31mCONFIG_HID[0m
default ![31mCONFIG_EXPERT[0m
---help---
Support for Ezkey BTC 8193 keyboard.
config [31mCONFIG_HID_GEMBIRD[0m
tristate "Gembird Joypad"
depends on [31mCONFIG_HID[0m
---help---
Support for Gembird JPD-DualForce 2.
config [31mCONFIG_HID_GFRM[0m
tristate "Google Fiber TV Box remote control support"
depends on [31mCONFIG_HID[0m
---help---
Support for Google Fiber TV Box remote controls
config [31mCONFIG_HID_HOLTEK[0m
tristate "Holtek HID devices"
depends on [31mCONFIG_USB_HID[0m
---help---
Support for Holtek based devices:
- Holtek On Line Grip based game controller
- Trust GXT 18 Gaming Keyboard
- Sharkoon Drakonia / Perixx MX-2000 gaming mice
- Tracer Sniper TRM-503 / NOVA Gaming Slider X200 /
Zalman ZM-GM1
- SHARKOON DarkGlider Gaming mouse
- LEETGION Hellion Gaming Mouse
config [31mCONFIG_HOLTEK_FF[0m
bool "Holtek On Line Grip force feedback support"
depends on [31mCONFIG_HID_HOLTEK[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
---help---
Say Y here if you have a Holtek On Line Grip based game controller
and want to have force feedback support for it.
config [31mCONFIG_HID_GT683R[0m
tristate "MSI GT68xR LED support"
depends on [31mCONFIG_LEDS_CLASS[0m && [31mCONFIG_USB_HID[0m
---help---
Say Y here if you want to enable support for the three MSI GT68xR LEDs
This driver support following modes:
- Normal: LEDs are fully on when enabled
- Audio: LEDs brightness depends on sound level
- Breathing: LEDs brightness varies at human breathing rate
Currently the following devices are know to be supported:
- MSI GT683R
config [31mCONFIG_HID_KEYTOUCH[0m
tristate "Keytouch HID devices"
depends on [31mCONFIG_HID[0m
---help---
Support for Keytouch [31mCONFIG_HID[0m devices not fully compliant with
the specification. Currently supported:
- Keytouch IEC 60945
config [31mCONFIG_HID_KYE[0m
tristate "KYE/Genius devices"
depends on [31mCONFIG_HID[0m
---help---
Support for KYE/Genius devices not fully compliant with [31mCONFIG_HID[0m standard:
- Ergo Mouse
- EasyPen i405X tablet
- MousePen i608X tablet
- EasyPen M610X tablet
config [31mCONFIG_HID_UCLOGIC[0m
tristate "UC-Logic"
depends on [31mCONFIG_USB_HID[0m
---help---
Support for UC-Logic and Huion tablets.
config [31mCONFIG_HID_WALTOP[0m
tristate "Waltop"
depends on [31mCONFIG_HID[0m
---help---
Support for Waltop tablets.
config [31mCONFIG_HID_GYRATION[0m
tristate "Gyration remote control"
depends on [31mCONFIG_HID[0m
---help---
Support for Gyration remote control.
config [31mCONFIG_HID_ICADE[0m
tristate "ION iCade arcade controller"
depends on [31mCONFIG_HID[0m
---help---
Support for the [31mCONFIG_ION[0m iCade arcade controller to work as a joystick.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called hid-icade.
config [31mCONFIG_HID_TWINHAN[0m
tristate "Twinhan IR remote control"
depends on [31mCONFIG_HID[0m
---help---
Support for Twinhan IR remote control.
config [31mCONFIG_HID_KENSINGTON[0m
tristate "Kensington Slimblade Trackball"
depends on [31mCONFIG_HID[0m
default ![31mCONFIG_EXPERT[0m
---help---
Support for Kensington Slimblade Trackball.
config [31mCONFIG_HID_LCPOWER[0m
tristate "LC-Power"
depends on [31mCONFIG_HID[0m
---help---
Support for LC-Power RC1000MCE RF remote control.
config [31mCONFIG_HID_LED[0m
tristate "Simple RGB LED support"
depends on [31mCONFIG_HID[0m
depends on [31mCONFIG_LEDS_CLASS[0m
---help---
Support for simple RGB LED devices. Currently supported are:
- Riso Kagaku Webmail Notifier
- Dream Cheeky Webmail Notifier and Friends Alert
- ThingM blink(1)
- Delcom Visual Signal Indicator Generation 2
- Greynut Luxafor
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called hid-led.
config [31mCONFIG_HID_LENOVO[0m
tristate "Lenovo / Thinkpad devices"
depends on [31mCONFIG_HID[0m
select [31mCONFIG_NEW_LEDS[0m
select [31mCONFIG_LEDS_CLASS[0m
---help---
Support for Lenovo devices that are not fully compliant with [31mCONFIG_HID[0m standard.
Say Y if you want support for the non-compliant features of the Lenovo
Thinkpad standalone keyboards, e.g:
- ThinkPad [31mCONFIG_USB[0m Keyboard with TrackPoint (supports extra LEDs and trackpoint
configuration)
- ThinkPad Compact Bluetooth Keyboard with TrackPoint (supports Fn keys)
- ThinkPad Compact [31mCONFIG_USB[0m Keyboard with TrackPoint (supports Fn keys)
config [31mCONFIG_HID_LOGITECH[0m
tristate "Logitech devices"
depends on [31mCONFIG_HID[0m
default ![31mCONFIG_EXPERT[0m
---help---
Support for Logitech devices that are not fully compliant with [31mCONFIG_HID[0m standard.
config [31mCONFIG_HID_LOGITECH_DJ[0m
tristate "Logitech Unifying receivers full support"
depends on [31mCONFIG_HIDRAW[0m
depends on [31mCONFIG_HID_LOGITECH[0m
select [31mCONFIG_HID_LOGITECH_HIDPP[0m
---help---
Say Y if you want support for Logitech Unifying receivers and devices.
Unifying receivers are capable of pairing up to 6 Logitech compliant
devices to the same receiver. Without this driver it will be handled by
generic [31mCONFIG_USB_HID[0m driver and all incoming events will be multiplexed
into a single mouse and a single keyboard device.
config [31mCONFIG_HID_LOGITECH_HIDPP[0m
tristate "Logitech HID++ devices support"
depends on [31mCONFIG_HID_LOGITECH[0m
---help---
Support for Logitech devices relyingon the [31mCONFIG_HID[0m++ Logitech specification
Say Y if you want support for Logitech devices relying on the [31mCONFIG_HID[0m++
specification. Such devices are the various Logitech Touchpads (T650,
T651, TK820), some mice (Zone Touch mouse), or even keyboards (Solar
Keyboard).
config [31mCONFIG_LOGITECH_FF[0m
bool "Logitech force feedback support"
depends on [31mCONFIG_HID_LOGITECH[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
help
Say Y here if you have one of these devices:
- Logitech WingMan Cordless RumblePad
- Logitech WingMan Cordless RumblePad 2
- Logitech WingMan Force 3D
and if you want to enable force feedback for them.
Note: if you say N here, this device will still be supported, but without
force feedback.
config [31mCONFIG_LOGIRUMBLEPAD2_FF[0m
bool "Logitech force feedback support (variant 2)"
depends on [31mCONFIG_HID_LOGITECH[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
help
Say Y here if you want to enable force feedback support for:
- Logitech RumblePad
- Logitech Rumblepad 2
- Logitech Formula Vibration Feedback Wheel
config [31mCONFIG_LOGIG940_FF[0m
bool "Logitech Flight System G940 force feedback support"
depends on [31mCONFIG_HID_LOGITECH[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
help
Say Y here if you want to enable force feedback support for Logitech
Flight System G940 devices.
config [31mCONFIG_LOGIWHEELS_FF[0m
bool "Logitech wheels configuration and force feedback support"
depends on [31mCONFIG_HID_LOGITECH[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
default [31mCONFIG_LOGITECH_FF[0m
help
Say Y here if you want to enable force feedback and range setting(*)
support for following Logitech wheels:
- Logitech G25 (*)
- Logitech G27 (*)
- Logitech G29 (*)
- Logitech Driving Force
- Logitech Driving Force Pro (*)
- Logitech Driving Force GT (*)
- Logitech Driving Force EX/RX
- Logitech Driving Force Wireless
- Logitech Speed Force Wireless
- Logitech MOMO Force
- Logitech MOMO Racing Force
- Logitech Formula Force GP
- Logitech Formula Force EX/RX
- Logitech Wingman Formula Force GP
config [31mCONFIG_HID_MAGICMOUSE[0m
tristate "Apple Magic Mouse/Trackpad multi-touch support"
depends on [31mCONFIG_HID[0m
---help---
Support for the Apple Magic Mouse/Trackpad multi-touch.
Say Y here if you want support for the multi-touch features of the
Apple Wireless "Magic" Mouse and the Apple Wireless "Magic" Trackpad.
config [31mCONFIG_HID_MAYFLASH[0m
tristate "Mayflash game controller adapter force feedback"
depends on [31mCONFIG_HID[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
---help---
Say Y here if you have HJZ Mayflash PS3 game controller adapters
and want to enable force feedback support.
config [31mCONFIG_HID_MICROSOFT[0m
tristate "Microsoft non-fully HID-compliant devices"
depends on [31mCONFIG_HID[0m
default ![31mCONFIG_EXPERT[0m
---help---
Support for Microsoft devices that are not fully compliant with [31mCONFIG_HID[0m standard.
config [31mCONFIG_HID_MONTEREY[0m
tristate "Monterey Genius KB29E keyboard"
depends on [31mCONFIG_HID[0m
default ![31mCONFIG_EXPERT[0m
---help---
Support for Monterey Genius KB29E.
config [31mCONFIG_HID_MULTITOUCH[0m
tristate "HID Multitouch panels"
depends on [31mCONFIG_HID[0m
---help---
Generic support for [31mCONFIG_HID[0m multitouch panels.
Say Y here if you have one of the following devices:
- 3M PCT touch screens
- ActionStar dual touch panels
- Atmel panels
- Cando dual touch panels
- Chunghwa panels
- CJTouch panels
- CVTouch panels
- Cypress TrueTouch panels
- Elan Microelectronics touch panels
- Elo TouchSystems IntelliTouch Plus panels
- GeneralTouch 'Sensing Win7-TwoFinger' panels
- GoodTouch panels
- Hanvon dual touch panels
- Ilitek dual touch panels
- IrTouch Infrared [31mCONFIG_USB[0m panels
- LG Display panels (Dell ST2220Tc)
- Lumio CrystalTouch panels
- MosArt dual-touch panels
- Panasonic multitouch panels
- PenMount dual touch panels
- Perixx Peripad 701 touchpad
- PixArt optical touch screen
- Pixcir dual touch panels
- Quanta panels
- eGalax dual-touch panels, including the Joojoo and Wetab tablets
- SiS multitouch panels
- Stantum multitouch panels
- Touch International Panels
- Unitec Panels
- Wistron optical touch panels
- XAT optical touch panels
- Xiroku optical touch panels
- Zytronic touch panels
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called hid-multitouch.
config [31mCONFIG_HID_NTRIG[0m
tristate "N-Trig touch screen"
depends on [31mCONFIG_USB_HID[0m
---help---
Support for N-Trig touch screen.
config [31mCONFIG_HID_ORTEK[0m
tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
depends on [31mCONFIG_HID[0m
---help---
There are certain devices which have LogicalMaximum wrong in the keyboard
usage page of their report descriptor. The most prevailing ones so far
are manufactured by Ortek, thus the name of the driver. Currently
supported devices by this driver are
- Ortek PKB-1700
- Ortek WKB-2000
- Skycable wireless presenter
config [31mCONFIG_HID_PANTHERLORD[0m
tristate "Pantherlord/GreenAsia game controller"
depends on [31mCONFIG_HID[0m
---help---
Say Y here if you have a PantherLord/GreenAsia based game controller
or adapter.
config [31mCONFIG_PANTHERLORD_FF[0m
bool "Pantherlord force feedback support"
depends on [31mCONFIG_HID_PANTHERLORD[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
---help---
Say Y here if you have a PantherLord/GreenAsia based game controller
or adapter and want to enable force feedback support for it.
config [31mCONFIG_HID_PENMOUNT[0m
tristate "Penmount touch device"
depends on [31mCONFIG_USB_HID[0m
---help---
This selects a driver for the PenMount 6000 touch controller.
The driver works around a problem in the report descript allowing
the userspace to touch events instead of mouse events.
Say Y here if you have a Penmount based touch controller.
config [31mCONFIG_HID_PETALYNX[0m
tristate "Petalynx Maxter remote control"
depends on [31mCONFIG_HID[0m
---help---
Support for Petalynx Maxter remote control.
config [31mCONFIG_HID_PICOLCD[0m
tristate "PicoLCD (graphic version)"
depends on [31mCONFIG_HID[0m
---help---
This provides support for Minibox PicoLCD devices, currently
only the graphical ones are supported.
This includes support for the following device features:
- Keypad
- Switching between Firmware and Flash mode
- EEProm / Flash access (via debugfs)
Features selectively enabled:
- Framebuffer for monochrome 256x64 display
- Backlight control
- Contrast control
- General purpose outputs
Features that are not (yet) supported:
- IR
config [31mCONFIG_HID_PICOLCD_FB[0m
bool "Framebuffer support" if [31mCONFIG_EXPERT[0m
default ![31mCONFIG_EXPERT[0m
depends on [31mCONFIG_HID_PICOLCD[0m
depends on [31mCONFIG_HID_PICOLCD[0m=[31mCONFIG_FB[0m || [31mCONFIG_FB[0m=y
select [31mCONFIG_FB_DEFERRED_IO[0m
select [31mCONFIG_FB_SYS_FILLRECT[0m
select [31mCONFIG_FB_SYS_COPYAREA[0m
select [31mCONFIG_FB_SYS_IMAGEBLIT[0m
select [31mCONFIG_FB_SYS_FOPS[0m
---help---
Provide access to PicoLCD's 256x64 monochrome display via a
framebuffer device.
config [31mCONFIG_HID_PICOLCD_BACKLIGHT[0m
bool "Backlight control" if [31mCONFIG_EXPERT[0m
default ![31mCONFIG_EXPERT[0m
depends on [31mCONFIG_HID_PICOLCD[0m
depends on [31mCONFIG_HID_PICOLCD[0m=[31mCONFIG_BACKLIGHT_CLASS_DEVICE[0m || [31mCONFIG_BACKLIGHT_CLASS_DEVICE[0m=y
---help---
Provide access to PicoLCD's backlight control via backlight
class.
config [31mCONFIG_HID_PICOLCD_LCD[0m
bool "Contrast control" if [31mCONFIG_EXPERT[0m
default ![31mCONFIG_EXPERT[0m
depends on [31mCONFIG_HID_PICOLCD[0m
depends on [31mCONFIG_HID_PICOLCD[0m=[31mCONFIG_LCD_CLASS_DEVICE[0m || [31mCONFIG_LCD_CLASS_DEVICE[0m=y
---help---
Provide access to PicoLCD's LCD contrast via lcd class.
config [31mCONFIG_HID_PICOLCD_LEDS[0m
bool "GPO via leds class" if [31mCONFIG_EXPERT[0m
default ![31mCONFIG_EXPERT[0m
depends on [31mCONFIG_HID_PICOLCD[0m
depends on [31mCONFIG_HID_PICOLCD[0m=[31mCONFIG_LEDS_CLASS[0m || [31mCONFIG_LEDS_CLASS[0m=y
---help---
Provide access to PicoLCD's GPO pins via leds class.
config [31mCONFIG_HID_PICOLCD_CIR[0m
bool "CIR via RC class" if [31mCONFIG_EXPERT[0m
default ![31mCONFIG_EXPERT[0m
depends on [31mCONFIG_HID_PICOLCD[0m
depends on [31mCONFIG_HID_PICOLCD[0m=[31mCONFIG_RC_CORE[0m || [31mCONFIG_RC_CORE[0m=y
---help---
Provide access to PicoLCD's CIR interface via remote control ([31mCONFIG_LIRC[0m).
config [31mCONFIG_HID_PLANTRONICS[0m
tristate "Plantronics USB HID Driver"
depends on [31mCONFIG_HID[0m
---help---
Provides [31mCONFIG_HID[0m support for Plantronics [31mCONFIG_USB[0m audio devices.
Correctly maps vendor unique volume up/down [31mCONFIG_HID[0m usages to
KEY_VOLUMEUP and KEY_VOLUMEDOWN events and prevents core mapping
of other vendor unique [31mCONFIG_HID[0m usages to random mouse events.
Say [31mCONFIG_M[0m here if you may ever plug in a Plantronics [31mCONFIG_USB[0m audio device.
config [31mCONFIG_HID_PRIMAX[0m
tristate "Primax non-fully HID-compliant devices"
depends on [31mCONFIG_HID[0m
---help---
Support for Primax devices that are not fully compliant with the
[31mCONFIG_HID[0m standard.
config [31mCONFIG_HID_ROCCAT[0m
tristate "Roccat device support"
depends on [31mCONFIG_USB_HID[0m
---help---
Support for Roccat devices.
Say Y here if you have a Roccat mouse or keyboard and want
support for its special functionalities.
config [31mCONFIG_HID_SAITEK[0m
tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
depends on [31mCONFIG_HID[0m
---help---
Support for Saitek devices that are not fully compliant with the
[31mCONFIG_HID[0m standard.
Supported devices:
- PS1000 Dual Analog Pad
- Saitek R.[31mCONFIG_A[0m.T.7, R.[31mCONFIG_A[0m.T.9, [31mCONFIG_M[0m.[31mCONFIG_M[0m.O.7 Gaming Mice
- Mad Catz R.[31mCONFIG_A[0m.T.5, R.[31mCONFIG_A[0m.T.9 Gaming Mice
config [31mCONFIG_HID_SAMSUNG[0m
tristate "Samsung InfraRed remote control or keyboards"
depends on [31mCONFIG_HID[0m
---help---
Support for Samsung InfraRed remote control or keyboards.
config [31mCONFIG_HID_SONY[0m
tristate "Sony PS2/3/4 accessories"
depends on [31mCONFIG_USB_HID[0m
depends on [31mCONFIG_NEW_LEDS[0m
depends on [31mCONFIG_LEDS_CLASS[0m
select [31mCONFIG_POWER_SUPPLY[0m
---help---
Support for
* Sony PS3 6-axis controllers
* Sony PS4 DualShock 4 controllers
* Buzz controllers
* Sony PS3 Blue-ray Disk Remote Control (Bluetooth)
* Logitech Harmony adapter for Sony Playstation 3 (Bluetooth)
config [31mCONFIG_SONY_FF[0m
bool "Sony PS2/3/4 accessories force feedback support"
depends on [31mCONFIG_HID_SONY[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
---help---
Say Y here if you have a Sony PS2/3/4 accessory and want to enable
force feedback support for it.
config [31mCONFIG_HID_SPEEDLINK[0m
tristate "Speedlink VAD Cezanne mouse support"
depends on [31mCONFIG_HID[0m
---help---
Support for Speedlink Vicious and Divine Cezanne mouse.
config [31mCONFIG_HID_STEELSERIES[0m
tristate "Steelseries SRW-S1 steering wheel support"
depends on [31mCONFIG_HID[0m
---help---
Support for Steelseries SRW-S1 steering wheel
config [31mCONFIG_HID_SUNPLUS[0m
tristate "Sunplus wireless desktop"
depends on [31mCONFIG_HID[0m
---help---
Support for Sunplus wireless desktop.
config [31mCONFIG_HID_RMI[0m
tristate "Synaptics RMI4 device support"
depends on [31mCONFIG_HID[0m
---help---
Support for Synaptics RMI4 touchpads.
Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
and want support for its special functionalities.
config [31mCONFIG_HID_GREENASIA[0m
tristate "GreenAsia (Product ID 0x12) game controller support"
depends on [31mCONFIG_HID[0m
---help---
Say Y here if you have a GreenAsia (Product ID 0x12) based game
controller or adapter.
config [31mCONFIG_GREENASIA_FF[0m
bool "GreenAsia (Product ID 0x12) force feedback support"
depends on [31mCONFIG_HID_GREENASIA[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
---help---
Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
(like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
and want to enable force feedback support for it.
config [31mCONFIG_HID_HYPERV_MOUSE[0m
tristate "Microsoft Hyper-V mouse driver"
depends on [31mCONFIG_HYPERV[0m
---help---
Select this option to enable the Hyper-V mouse driver.
config [31mCONFIG_HID_SMARTJOYPLUS[0m
tristate "SmartJoy PLUS PS2/USB adapter support"
depends on [31mCONFIG_HID[0m
---help---
Support for SmartJoy PLUS PS2/[31mCONFIG_USB[0m adapter, Super Dual Box,
Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
Note that [31mCONFIG_DDR[0m (Dance Dance Revolution) mode is not supported, nor
is pressure sensitive buttons on the pro models.
config [31mCONFIG_SMARTJOYPLUS_FF[0m
bool "SmartJoy PLUS PS2/USB adapter force feedback support"
depends on [31mCONFIG_HID_SMARTJOYPLUS[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
---help---
Say Y here if you have a SmartJoy PLUS PS2/[31mCONFIG_USB[0m adapter and want to
enable force feedback support for it.
config [31mCONFIG_HID_TIVO[0m
tristate "TiVo Slide Bluetooth remote control support"
depends on [31mCONFIG_HID[0m
---help---
Say Y if you have a TiVo Slide Bluetooth remote control.
config [31mCONFIG_HID_TOPSEED[0m
tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
depends on [31mCONFIG_HID[0m
---help---
Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
CLLRCMCE remote control.
config [31mCONFIG_HID_THINGM[0m
tristate "ThingM blink(1) USB RGB LED"
depends on [31mCONFIG_HID[0m
depends on [31mCONFIG_LEDS_CLASS[0m
select [31mCONFIG_HID_LED[0m
---help---
Support for the ThingM blink(1) [31mCONFIG_USB[0m RGB LED. This driver has been
merged into the generic hid led driver. Config symbol [31mCONFIG_HID_THINGM[0m
just selects [31mCONFIG_HID_LED[0m and will be removed soon.
config [31mCONFIG_HID_THRUSTMASTER[0m
tristate "ThrustMaster devices support"
depends on [31mCONFIG_HID[0m
---help---
Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
a THRUSTMASTER Ferrari GT Rumble Wheel.
config [31mCONFIG_THRUSTMASTER_FF[0m
bool "ThrustMaster devices force feedback support"
depends on [31mCONFIG_HID_THRUSTMASTER[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
---help---
Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
Rumble Force or Force Feedback Wheel.
config [31mCONFIG_HID_UDRAW_PS3[0m
tristate "THQ PS3 uDraw tablet"
depends on [31mCONFIG_HID[0m
---help---
Say Y here if you want to use the THQ uDraw gaming tablet for
the PS3.
config [31mCONFIG_HID_WACOM[0m
tristate "Wacom Intuos/Graphire tablet support (USB)"
depends on [31mCONFIG_HID[0m
select [31mCONFIG_POWER_SUPPLY[0m
select [31mCONFIG_NEW_LEDS[0m
select [31mCONFIG_LEDS_CLASS[0m
select [31mCONFIG_LEDS_TRIGGERS[0m
help
Say Y here if you want to use the [31mCONFIG_USB[0m or [31mCONFIG_BT[0m version of the Wacom Intuos
or Graphire tablet.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called wacom.
config [31mCONFIG_HID_WIIMOTE[0m
tristate "Nintendo Wii / Wii U peripherals"
depends on [31mCONFIG_HID[0m
depends on [31mCONFIG_LEDS_CLASS[0m
select [31mCONFIG_POWER_SUPPLY[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
---help---
Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
devices are the Wii Remote and its extension devices, but also devices
based on the Wii Remote like the Wii U Pro Controller or the
Wii Balance Board.
Support for all official Nintendo extensions is available, however, 3rd
party extensions might not be supported. Please report these devices to:
http://github.com/dvdhrm/xwiimote/issues
Other Nintendo Wii U peripherals that are IEEE 802.11 based (including
the Wii U Gamepad) might be supported in the future. But currently
support is limited to Bluetooth based devices.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called hid-wiimote.
config [31mCONFIG_HID_XINMO[0m
tristate "Xin-Mo non-fully compliant devices"
depends on [31mCONFIG_HID[0m
---help---
Support for Xin-Mo devices that are not fully compliant with the [31mCONFIG_HID[0m
standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
if you have a Xin-Mo Dual Arcade controller.
config [31mCONFIG_HID_ZEROPLUS[0m
tristate "Zeroplus based game controller support"
depends on [31mCONFIG_HID[0m
---help---
Say Y here if you have a Zeroplus based game controller.
config [31mCONFIG_ZEROPLUS_FF[0m
bool "Zeroplus based game controller force feedback support"
depends on [31mCONFIG_HID_ZEROPLUS[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
---help---
Say Y here if you have a Zeroplus based game controller and want
to have force feedback support for it.
config [31mCONFIG_HID_ZYDACRON[0m
tristate "Zydacron remote control support"
depends on [31mCONFIG_HID[0m
---help---
Support for Zydacron remote control.
config [31mCONFIG_HID_SENSOR_HUB[0m
tristate "HID Sensors framework support"
depends on [31mCONFIG_HID[0m && [31mCONFIG_HAS_IOMEM[0m
select [31mCONFIG_MFD_CORE[0m
default n
---help---
Support for [31mCONFIG_HID[0m Sensor framework. This creates a MFD instance
for a sensor hub and identifies all the sensors connected to it.
Each sensor is registered as a MFD cell, so that sensor specific
processing can be done in a separate driver. Each sensor
drivers can use the service provided by this driver to register
for events and handle data streams. Each sensor driver can format
data and present to user mode using input or [31mCONFIG_IIO[0m interface.
config [31mCONFIG_HID_SENSOR_CUSTOM_SENSOR[0m
tristate "HID Sensors hub custom sensor support"
depends on [31mCONFIG_HID_SENSOR_HUB[0m
default n
---help---
[31mCONFIG_HID[0m Sensor hub specification allows definition of some custom and
generic sensors. Unlike other [31mCONFIG_HID[0m sensors, they can't be exported
via Linux [31mCONFIG_IIO[0m because of custom fields. This is up to the manufacturer
to decide how to interpret these special sensor ids and process in
the user space. Currently some manufacturers are using these ids for
sensor calibration and debugging other sensors. Manufacturers
should't use these special custom sensor ids to export any of the
standard sensors.
Select this config option for custom/generic sensor support.
config [31mCONFIG_HID_ALPS[0m
tristate "Alps HID device support"
depends on [31mCONFIG_HID[0m
---help---
Support for Alps [31mCONFIG_I2C[0m [31mCONFIG_HID[0m touchpads and StickPointer.
Say Y here if you have a Alps touchpads over i2c-hid or usbhid
and want support for its special functionalities.
endmenu
endif # [31mCONFIG_HID[0m
source "drivers/hid/usbhid/Kconfig"
source "drivers/hid/i2c-hid/Kconfig"
source "drivers/hid/intel-ish-hid/Kconfig"
endmenu