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 the special keys (Fn, Numlock) on
101 Apple iBooks, PowerBooks, MacBooks, MacBook Pros and aluminum USB
107 tristate "Belkin" if EMBEDDED
111 Support for Belkin Flip KVM and Wireless keyboard.
114 tristate "Bright" if EMBEDDED
118 Support for Bright ABNT-2 keyboard.
121 tristate "Cherry" if EMBEDDED
125 Support for Cherry Cymotion.
128 tristate "Chicony" if EMBEDDED
132 Support for Chicony Tactical pad.
135 tristate "Cypress" if EMBEDDED
139 Support for Cypress mouse and barcodes.
142 tristate "Dell" if EMBEDDED
146 Support for Dell W7658.
149 tristate "Ezkey" if EMBEDDED
153 Support for Ezkey mouse and barcodes.
156 tristate "Gyration" if EMBEDDED
160 Support for Gyration remote.
163 tristate "Logitech" if EMBEDDED
167 Support for some Logitech devices which breaks less or more
171 bool "Logitech force feedback"
172 depends on HID_LOGITECH
173 select INPUT_FF_MEMLESS
175 Say Y here if you have one of these devices:
176 - Logitech WingMan Cordless RumblePad
177 - Logitech WingMan Cordless RumblePad 2
178 - Logitech WingMan Force 3D
179 - Logitech Formula Force EX
180 - Logitech MOMO Force wheel
182 and if you want to enable force feedback for them.
183 Note: if you say N here, this device will still be supported, but without
186 config LOGIRUMBLEPAD2_FF
187 bool "Logitech Rumblepad 2 force feedback"
188 depends on HID_LOGITECH
189 select INPUT_FF_MEMLESS
191 Say Y here if you want to enable force feedback support for Logitech
195 tristate "Microsoft" if EMBEDDED
199 Support for some Microsoft devices which breaks less or more
203 tristate "Monterey" if EMBEDDED
207 Support for Monterey Genius KB29E.
209 config HID_PANTHERLORD
210 tristate "Pantherlord devices support" if EMBEDDED
214 Support for PantherLord/GreenAsia based device support.
217 config PANTHERLORD_FF
218 bool "Pantherlord force feedback support"
219 depends on HID_PANTHERLORD
220 select INPUT_FF_MEMLESS
222 Say Y here if you have a PantherLord/GreenAsia based game controller
223 or adapter and want to enable force feedback support for it.
226 tristate "Petalynx" if EMBEDDED
230 Support for Petalynx Maxter remote.
233 tristate "Samsung" if EMBEDDED
237 Support for Samsung IR remote.
240 tristate "Sony" if EMBEDDED
244 Support for Sony PS3 controller.
247 tristate "Sunplus" if EMBEDDED
251 Support for Sunplus WDesktop input device.
253 config THRUSTMASTER_FF
254 tristate "ThrustMaster devices support"
257 select INPUT_FF_MEMLESS
259 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
260 a THRUSTMASTER Ferrari GT Rumble Force or Force Feedback Wheel.
263 tristate "Zeroplus based game controller support"
266 select INPUT_FF_MEMLESS
268 Say Y here if you have a Zeroplus based game controller.