blob: 066e8c08c268624144c0f7c930247334581be35b [file] [log] [blame]
Jiri Kosina63f38612006-12-08 18:41:30 +01001#
2# HID driver configuration
3#
Jan Engelhardt3cd70982007-04-30 13:27:48 +02004menuconfig HID_SUPPORT
5 bool "HID Devices"
Jiri Kosina63f38612006-12-08 18:41:30 +01006 depends on INPUT
Jan Engelhardt3cd70982007-04-30 13:27:48 +02007 default y
Jan Engelhardt06bfb7e2007-08-18 12:56:21 +02008 ---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.
Jan Engelhardt3cd70982007-04-30 13:27:48 +020013
14if HID_SUPPORT
Jiri Kosina63f38612006-12-08 18:41:30 +010015
16config HID
17 tristate "Generic HID support"
Russell Kingc96c9d72006-12-22 17:09:16 +000018 depends on INPUT
Jiri Kosina63f38612006-12-08 18:41:30 +010019 default y
20 ---help---
Jiri Kosina69e4d942007-01-03 23:03:14 +010021 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
Jiri Kosina63f38612006-12-08 18:41:30 +010033
Jiri Kosinac080d892007-01-25 11:43:31 +010034config HID_DEBUG
35 bool "HID debugging support"
Jiri Kosina58037eb2007-05-30 15:07:13 +020036 default y if !EMBEDDED
Jiri Kosinac080d892007-01-25 11:43:31 +010037 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
Jiri Kosina86166b72007-05-14 09:57:40 +020049config 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
Jiri Kosina6db3dfe2007-03-08 16:47:49 +010068source "drivers/hid/usbhid/Kconfig"
69
Jiri Slaby5f22a792008-05-16 11:49:19 +020070menu "Special HID drivers"
71 depends on HID
72
73config HID_LOGITECH
74 tristate "Logitech"
75 default m
76 depends on USB_HID
77 ---help---
78 Support for some Logitech devices which breaks less or more
79 HID specification.
80
81endmenu
82
Jan Engelhardt3cd70982007-04-30 13:27:48 +020083endif # HID_SUPPORT