2 # HID driver configuration
9 Say Y here to get to see options for various computer-human interface
10 device drivers. This option alone does not add any kernel code.
12 If you say N, all options in this submenu will be skipped and disabled.
17 tristate "Generic HID support"
21 A human interface device (HID) is a type of computer device that
22 interacts directly with and takes input from humans. The term "HID"
23 most commonly used to refer to the USB-HID specification, but other
24 devices (such as, but not strictly limited to, Bluetooth) are
25 designed using HID specification (this involves certain keyboards,
26 mice, tablets, etc). This option compiles into kernel the generic
27 HID layer code (parser, usages, etc.), which can then be used by
28 transport-specific HID implementation (like USB or Bluetooth).
30 For docs and specs, see http://www.usb.org/developers/hidpage/
35 bool "HID debugging support"
36 default y if !EMBEDDED
39 This option lets the HID layer output diagnostics about its internal
40 state, resolve HID usages, dump HID fields, etc. Individual HID drivers
41 use this debugging facility to output information about individual HID
44 This feature is useful for those who are either debugging the HID parser
45 or any HID hardware device.
50 bool "/dev/hidraw raw HID device support"
53 Say Y here if you want to support HID devices (from the USB
54 specification standpoint) that aren't strictly user interface
55 devices, like monitor controls and Uninterruptable Power Supplies.
57 This module supports these devices separately using a separate
58 event interface on /dev/hidraw.
60 There is also a /dev/hiddev configuration option in the USB HID
61 configuration menu. In comparison to hiddev, this device does not process
62 the hid events at all (no parsing, no lookups). This lets applications
63 to work on raw hid events when they want to, and avoid using transport-specific
64 userspace libhid/libusb libraries.
68 source "drivers/hid/usbhid/Kconfig"
70 menu "Special HID drivers"
74 bool "Load all HID drivers on hid core load"
77 Compatible option for older userspace. If you have system without udev
78 support of module loading through aliases and also old
79 module-init-tools which can't handle hid bus, choose Y here. Otherwise
80 say N. If you say N and your userspace is old enough, the only
81 functionality you lose is modules autoloading.
86 tristate "A4 tech" if EMBEDDED
90 Support for A4 tech X5 and WOP-35 / Trust 450L mice.
93 tristate "Apple" if EMBEDDED
94 depends on (USB_HID || BT_HIDP)
97 Support for some Apple devices which less or more break
100 Say Y here if you want support for keyboards of Apple iBooks, PowerBooks,
101 MacBooks, MacBook Pros and Apple Aluminum.
104 tristate "Belkin" if EMBEDDED
108 Support for Belkin Flip KVM and Wireless keyboard.
111 tristate "Bright" if EMBEDDED
115 Support for Bright ABNT-2 keyboard.
118 tristate "Cherry" if EMBEDDED
122 Support for Cherry Cymotion keyboard.
125 tristate "Chicony" if EMBEDDED
129 Support for Chicony Tactical pad.
132 tristate "Cypress" if EMBEDDED
136 Support for cypress mouse and barcode readers.
139 tristate "Dell" if EMBEDDED
143 Support for quirky Dell HID hardware that require
144 special LED handling (W7658 and SK8115 models)
147 tristate "Ezkey" if EMBEDDED
151 Support for Ezkey BTC 8193 keyboard.
154 tristate "Gyration" if EMBEDDED
158 Support for Gyration remote control.
161 tristate "Logitech" if EMBEDDED
165 Support for Logitech devices that are not fully compliant with HID standard.
168 bool "Logitech force feedback"
169 depends on HID_LOGITECH
170 select INPUT_FF_MEMLESS
172 Say Y here if you have one of these devices:
173 - Logitech WingMan Cordless RumblePad
174 - Logitech WingMan Cordless RumblePad 2
175 - Logitech WingMan Force 3D
176 - Logitech Formula Force EX
177 - Logitech MOMO Force wheel
179 and if you want to enable force feedback for them.
180 Note: if you say N here, this device will still be supported, but without
183 config LOGIRUMBLEPAD2_FF
184 bool "Logitech Rumblepad 2 force feedback"
185 depends on HID_LOGITECH
186 select INPUT_FF_MEMLESS
188 Say Y here if you want to enable force feedback support for Logitech
192 tristate "Microsoft" if EMBEDDED
196 Support for Microsoft devices that are not fully compliant with HID standard.
199 tristate "Monterey" if EMBEDDED
203 Support for Monterey Genius KB29E.
205 config HID_PANTHERLORD
206 tristate "Pantherlord devices support" if EMBEDDED
210 Support for PantherLord/GreenAsia based device support.
212 config PANTHERLORD_FF
213 bool "Pantherlord force feedback support"
214 depends on HID_PANTHERLORD
215 select INPUT_FF_MEMLESS
217 Say Y here if you have a PantherLord/GreenAsia based game controller
218 or adapter and want to enable force feedback support for it.
221 tristate "Petalynx" if EMBEDDED
225 Support for Petalynx Maxter remote control.
228 tristate "Samsung" if EMBEDDED
232 Support for Samsung InfraRed remote control.
235 tristate "Sony" if EMBEDDED
239 Support for Sony PS3 controller.
242 tristate "Sunplus" if EMBEDDED
246 Support for Sunplus wireless desktop.
248 config THRUSTMASTER_FF
249 tristate "ThrustMaster devices support"
252 select INPUT_FF_MEMLESS
254 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
255 a THRUSTMASTER Ferrari GT Rumble Force or Force Feedback Wheel.
258 tristate "Zeroplus based game controller support"
261 select INPUT_FF_MEMLESS
263 Say Y here if you have a Zeroplus based game controller.