1comment "USB Input Devices" 2 depends on USB 3 4config USB_HID 5 tristate "USB Human Interface Device (full HID) support" 6 default y 7 depends on USB && INPUT 8 select HID 9 ---help--- 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. 14 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>. 18 19 If unsure, say Y. 20 21 To compile this driver as a module, choose M here: the 22 module will be called usbhid. 23 24comment "Input core support is needed for USB HID input layer or HIDBP support" 25 depends on USB_HID && INPUT=n 26 27config HID_FF 28 bool "Force feedback support (EXPERIMENTAL)" 29 depends on USB_HID && EXPERIMENTAL 30 help 31 Say Y here is you want force feedback support for a few HID devices. 32 See below for a list of supported devices. 33 34 See <file:Documentation/input/ff.txt> for a description of the force 35 feedback API. 36 37 If unsure, say N. 38 39config HID_PID 40 bool "PID device support" 41 depends on HID_FF 42 help 43 Say Y here if you have a PID-compliant device and wish to enable force 44 feedback for it. Microsoft Sidewinder Force Feedback 2 is one of such 45 devices. 46 47config THRUSTMASTER_FF 48 bool "ThrustMaster devices support" 49 depends on HID_FF 50 select INPUT_FF_MEMLESS if USB_HID 51 help 52 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 53 a THRUSTMASTER Ferrari GT Rumble Force or Force Feedback Wheel, 54 and want to enable force feedback support for it. 55 Note: if you say N here, this device will still be supported, but without 56 force feedback. 57 58config ZEROPLUS_FF 59 bool "Zeroplus based game controller support" 60 depends on HID_FF 61 select INPUT_FF_MEMLESS if USB_HID 62 help 63 Say Y here if you have a Zeroplus based game controller and want to 64 enable force feedback for it. 65 66config USB_HIDDEV 67 bool "/dev/hiddev raw HID device support" 68 depends on USB_HID 69 help 70 Say Y here if you want to support HID devices (from the USB 71 specification standpoint) that aren't strictly user interface 72 devices, like monitor controls and Uninterruptable Power Supplies. 73 74 This module supports these devices separately using a separate 75 event interface on /dev/usb/hiddevX (char 180:96 to 180:111). 76 77 If unsure, say Y. 78 79menu "USB HID Boot Protocol drivers" 80 depends on USB!=n && USB_HID!=y 81 82config USB_KBD 83 tristate "USB HIDBP Keyboard (simple Boot) support" 84 depends on USB && INPUT 85 ---help--- 86 Say Y here only if you are absolutely sure that you don't want 87 to use the generic HID driver for your USB keyboard and prefer 88 to use the keyboard in its limited Boot Protocol mode instead. 89 90 This is almost certainly not what you want. This is mostly 91 useful for embedded applications or simple keyboards. 92 93 To compile this driver as a module, choose M here: the 94 module will be called usbkbd. 95 96 If even remotely unsure, say N. 97 98config USB_MOUSE 99 tristate "USB HIDBP Mouse (simple Boot) support" 100 depends on USB && INPUT 101 ---help--- 102 Say Y here only if you are absolutely sure that you don't want 103 to use the generic HID driver for your USB mouse and prefer 104 to use the mouse in its limited Boot Protocol mode instead. 105 106 This is almost certainly not what you want. This is mostly 107 useful for embedded applications or simple mice. 108 109 To compile this driver as a module, choose M here: the 110 module will be called usbmouse. 111 112 If even remotely unsure, say N. 113 114endmenu 115 116 117