PCI quirks: add quirk to disable boot interrupt generation on broadcom HT1000
[deliverable/linux.git] / drivers / hid / Kconfig
1 #
2 # HID driver configuration
3 #
4 menuconfig HID_SUPPORT
5 bool "HID Devices"
6 depends on INPUT
7 default y
8 ---help---
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.
11
12 If you say N, all options in this submenu will be skipped and disabled.
13
14 if HID_SUPPORT
15
16 config HID
17 tristate "Generic HID support"
18 depends on INPUT
19 default y
20 ---help---
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).
29
30 For docs and specs, see http://www.usb.org/developers/hidpage/
31
32 If unsure, say Y
33
34 config HID_DEBUG
35 bool "HID debugging support"
36 default y if !EMBEDDED
37 depends on HID
38 ---help---
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
42 devices, etc.
43
44 This feature is useful for those who are either debugging the HID parser
45 or any HID hardware device.
46
47 If unsure, say N
48
49 config HIDRAW
50 bool "/dev/hidraw raw HID device support"
51 depends on HID
52 ---help---
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.
56
57 This module supports these devices separately using a separate
58 event interface on /dev/hidraw.
59
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.
65
66 If unsure, say Y.
67
68 source "drivers/hid/usbhid/Kconfig"
69
70 endif # HID_SUPPORT
This page took 0.032818 seconds and 5 git commands to generate.