1 comment "USB Input Devices"
5 tristate "USB Human Interface Device (full HID) support"
7 depends on USB && INPUT
10 Say Y here if you want full HID support to connect USB keyboards,
11 mice, joysticks, graphic tablets, or any other HID based devices
12 to your computer via USB, as well as Uninterruptible Power Supply
13 (UPS) and monitor control devices.
15 You can't use this driver and the HIDBP (Boot Protocol) keyboard
16 and mouse drivers at the same time. More information is available:
17 <file:Documentation/input/input.txt>.
21 To compile this driver as a module, choose M here: the
22 module will be called usbhid.
24 config USB_HID_MOUSE_POLLING
25 bool "USB HID Mouse Interrupt Polling"
29 This option enables USB HID mouse polling instead of an event
30 based system. This option is only recommended for badly designed
35 config USB_HID_MOUSE_POLLING_INTERVAL
36 int "USB HID Mouse Interrupt Polling Interval"
38 depends on USB_HID_MOUSE_POLLING
40 The "USB HID Mouse Interrupt Polling Interval" is the interval, at
41 which your USB HID mouse is to be polled at. The interval is
42 specified in milliseconds.
44 Decreasing the interval will, of course, give you a much more
47 Generally speaking, a polling interval of 2 ms should be more than
48 enough for most people, and is great for gaming and other things
49 that require high precision.
51 An interval lower than 10ms is not guaranteed work on your
52 specific piece of hardware. If you want to play it safe, don't
55 Now, if you indeed want to feel the joy of a precise mouse, the
56 following mice are known to work without problems, when the interval
57 is set to at least 2 ms:
59 * Logitech's MX-family
60 * Logitech Mouse Man Dual Optical
62 * Microsoft Intellimouse Explorer
63 * Microsoft Intellimouse Optical 1.1
65 If unsure, keep it at 10 ms.
67 comment "Input core support is needed for USB HID input layer or HIDBP support"
68 depends on USB_HID && INPUT=n
71 bool "PID device support"
73 Say Y here if you have a PID-compliant device and wish to enable force
74 feedback for it. Microsoft Sidewinder Force Feedback 2 is one of such
78 bool "/dev/hiddev raw HID device support"
81 Say Y here if you want to support HID devices (from the USB
82 specification standpoint) that aren't strictly user interface
83 devices, like monitor controls and Uninterruptable Power Supplies.
85 This module supports these devices separately using a separate
86 event interface on /dev/usb/hiddevX (char 180:96 to 180:111).
90 menu "USB HID Boot Protocol drivers"
91 depends on USB!=n && USB_HID!=y && EXPERT
94 tristate "USB HIDBP Keyboard (simple Boot) support"
95 depends on USB && INPUT
97 Say Y here only if you are absolutely sure that you don't want
98 to use the generic HID driver for your USB keyboard and prefer
99 to use the keyboard in its limited Boot Protocol mode instead.
101 This is almost certainly not what you want. This is mostly
102 useful for embedded applications or simple keyboards.
104 To compile this driver as a module, choose M here: the
105 module will be called usbkbd.
107 If even remotely unsure, say N.
110 tristate "USB HIDBP Mouse (simple Boot) support"
111 depends on USB && INPUT
113 Say Y here only if you are absolutely sure that you don't want
114 to use the generic HID driver for your USB mouse and prefer
115 to use the mouse in its limited Boot Protocol mode instead.
117 This is almost certainly not what you want. This is mostly
118 useful for embedded applications or simple mice.
120 To compile this driver as a module, choose M here: the
121 module will be called usbmouse.
123 If even remotely unsure, say N.