Kconfig 2.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697
  1. comment "USB Input Devices"
  2. depends on USB
  3. config USB_HID
  4. tristate "USB Human Interface Device (full HID) support"
  5. default y
  6. depends on USB && INPUT
  7. select HID
  8. ---help---
  9. Say Y here if you want full HID support to connect USB keyboards,
  10. mice, joysticks, graphic tablets, or any other HID based devices
  11. to your computer via USB, as well as Uninterruptible Power Supply
  12. (UPS) and monitor control devices.
  13. You can't use this driver and the HIDBP (Boot Protocol) keyboard
  14. and mouse drivers at the same time. More information is available:
  15. <file:Documentation/input/input.txt>.
  16. If unsure, say Y.
  17. To compile this driver as a module, choose M here: the
  18. module will be called usbhid.
  19. comment "Input core support is needed for USB HID input layer or HIDBP support"
  20. depends on USB_HID && INPUT=n
  21. config HID_FF
  22. bool "Force feedback support (EXPERIMENTAL)"
  23. depends on USB_HID && EXPERIMENTAL
  24. help
  25. Say Y here is you want force feedback support for a few HID devices.
  26. See below for a list of supported devices.
  27. See <file:Documentation/input/ff.txt> for a description of the force
  28. feedback API.
  29. If unsure, say N.
  30. config HID_PID
  31. bool "PID device support"
  32. depends on HID_FF
  33. help
  34. Say Y here if you have a PID-compliant device and wish to enable force
  35. feedback for it. Microsoft Sidewinder Force Feedback 2 is one of such
  36. devices.
  37. config USB_HIDDEV
  38. bool "/dev/hiddev raw HID device support"
  39. depends on USB_HID
  40. help
  41. Say Y here if you want to support HID devices (from the USB
  42. specification standpoint) that aren't strictly user interface
  43. devices, like monitor controls and Uninterruptable Power Supplies.
  44. This module supports these devices separately using a separate
  45. event interface on /dev/usb/hiddevX (char 180:96 to 180:111).
  46. If unsure, say Y.
  47. menu "USB HID Boot Protocol drivers"
  48. depends on USB!=n && USB_HID!=y
  49. config USB_KBD
  50. tristate "USB HIDBP Keyboard (simple Boot) support"
  51. depends on USB && INPUT
  52. ---help---
  53. Say Y here only if you are absolutely sure that you don't want
  54. to use the generic HID driver for your USB keyboard and prefer
  55. to use the keyboard in its limited Boot Protocol mode instead.
  56. This is almost certainly not what you want. This is mostly
  57. useful for embedded applications or simple keyboards.
  58. To compile this driver as a module, choose M here: the
  59. module will be called usbkbd.
  60. If even remotely unsure, say N.
  61. config USB_MOUSE
  62. tristate "USB HIDBP Mouse (simple Boot) support"
  63. depends on USB && INPUT
  64. ---help---
  65. Say Y here only if you are absolutely sure that you don't want
  66. to use the generic HID driver for your USB mouse and prefer
  67. to use the mouse in its limited Boot Protocol mode instead.
  68. This is almost certainly not what you want. This is mostly
  69. useful for embedded applications or simple mice.
  70. To compile this driver as a module, choose M here: the
  71. module will be called usbmouse.
  72. If even remotely unsure, say N.
  73. endmenu