diff options
author | Dmitry Torokhov <dtor@insightbb.com> | 2007-05-07 17:31:32 -0400 |
---|---|---|
committer | Dmitry Torokhov <dtor@insightbb.com> | 2007-05-08 01:41:29 -0400 |
commit | ba0acb5ee318901646f82c134cca2e4de0c43934 (patch) | |
tree | 862d0d2b5d06332dce642571f625431c313d04ea /drivers/input/misc/Kconfig | |
parent | b5da20f8f7652e7a9648401a1942b7aac3b9ab9d (diff) |
Input: move USB miscellaneous devices under drivers/input/misc
This will allow concentrating all input devices in one place
in {menu|x|q}config.
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/input/misc/Kconfig')
-rw-r--r-- | drivers/input/misc/Kconfig | 88 |
1 files changed, 81 insertions, 7 deletions
diff --git a/drivers/input/misc/Kconfig b/drivers/input/misc/Kconfig index 1d0d3e765db6..6013ace94d98 100644 --- a/drivers/input/misc/Kconfig +++ b/drivers/input/misc/Kconfig | |||
@@ -40,6 +40,18 @@ config INPUT_M68K_BEEP | |||
40 | tristate "M68k Beeper support" | 40 | tristate "M68k Beeper support" |
41 | depends on M68K | 41 | depends on M68K |
42 | 42 | ||
43 | config INPUT_IXP4XX_BEEPER | ||
44 | tristate "IXP4XX Beeper support" | ||
45 | depends on ARCH_IXP4XX | ||
46 | help | ||
47 | If you say yes here, you can connect a beeper to the | ||
48 | ixp4xx gpio pins. This is used by the LinkSys NSLU2. | ||
49 | |||
50 | If unsure, say Y. | ||
51 | |||
52 | To compile this driver as a module, choose M here: the | ||
53 | module will be called ixp4xx-beeper. | ||
54 | |||
43 | config INPUT_COBALT_BTNS | 55 | config INPUT_COBALT_BTNS |
44 | tristate "Cobalt button interface" | 56 | tristate "Cobalt button interface" |
45 | depends on MIPS_COBALT | 57 | depends on MIPS_COBALT |
@@ -70,17 +82,79 @@ config INPUT_ATLAS_BTNS | |||
70 | To compile this driver as a module, choose M here: the module will | 82 | To compile this driver as a module, choose M here: the module will |
71 | be called atlas_btns. | 83 | be called atlas_btns. |
72 | 84 | ||
73 | config INPUT_IXP4XX_BEEPER | 85 | config INPUT_ATI_REMOTE |
74 | tristate "IXP4XX Beeper support" | 86 | tristate "ATI / X10 USB RF remote control" |
75 | depends on ARCH_IXP4XX | 87 | select USB |
76 | help | 88 | help |
77 | If you say yes here, you can connect a beeper to the | 89 | Say Y here if you want to use an ATI or X10 "Lola" USB remote control. |
78 | ixp4xx gpio pins. This is used by the LinkSys NSLU2. | 90 | These are RF remotes with USB receivers. |
91 | The ATI remote comes with many of ATI's All-In-Wonder video cards. | ||
92 | The X10 "Lola" remote is available at: | ||
93 | <http://www.x10.com/products/lola_sg1.htm> | ||
94 | This driver provides mouse pointer, left and right mouse buttons, | ||
95 | and maps all the other remote buttons to keypress events. | ||
96 | |||
97 | To compile this driver as a module, choose M here: the module will be | ||
98 | called ati_remote. | ||
99 | |||
100 | config INPUT_ATI_REMOTE2 | ||
101 | tristate "ATI / Philips USB RF remote control" | ||
102 | select USB | ||
103 | help | ||
104 | Say Y here if you want to use an ATI or Philips USB RF remote control. | ||
105 | These are RF remotes with USB receivers. | ||
106 | ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards | ||
107 | and is also available as a separate product. | ||
108 | This driver provides mouse pointer, left and right mouse buttons, | ||
109 | and maps all the other remote buttons to keypress events. | ||
110 | |||
111 | To compile this driver as a module, choose M here: the module will be | ||
112 | called ati_remote2. | ||
113 | |||
114 | config INPUT_KEYSPAN_REMOTE | ||
115 | tristate "Keyspan DMR USB remote control (EXPERIMENTAL)" | ||
116 | depends on EXPERIMENTAL | ||
117 | select USB | ||
118 | help | ||
119 | Say Y here if you want to use a Keyspan DMR USB remote control. | ||
120 | Currently only the UIA-11 type of receiver has been tested. The tag | ||
121 | on the receiver that connects to the USB port should have a P/N that | ||
122 | will tell you what type of DMR you have. The UIA-10 type is not | ||
123 | supported at this time. This driver maps all buttons to keypress | ||
124 | events. | ||
79 | 125 | ||
80 | If unsure, say Y. | 126 | To compile this driver as a module, choose M here: the module will |
127 | be called keyspan_remote. | ||
128 | |||
129 | config INPUT_POWERMATE | ||
130 | tristate "Griffin PowerMate and Contour Jog support" | ||
131 | select USB | ||
132 | help | ||
133 | Say Y here if you want to use Griffin PowerMate or Contour Jog devices. | ||
134 | These are aluminum dials which can measure clockwise and anticlockwise | ||
135 | rotation. The dial also acts as a pushbutton. The base contains an LED | ||
136 | which can be instructed to pulse or to switch to a particular intensity. | ||
137 | |||
138 | You can download userspace tools from | ||
139 | <http://sowerbutts.com/powermate/>. | ||
81 | 140 | ||
82 | To compile this driver as a module, choose M here: the | 141 | To compile this driver as a module, choose M here: the |
83 | module will be called ixp4xx-beeper. | 142 | module will be called powermate. |
143 | |||
144 | config INPUT_YEALINK | ||
145 | tristate "Yealink usb-p1k voip phone" | ||
146 | depends EXPERIMENTAL | ||
147 | select USB | ||
148 | help | ||
149 | Say Y here if you want to enable keyboard and LCD functions of the | ||
150 | Yealink usb-p1k usb phones. The audio part is enabled by the generic | ||
151 | usb sound driver, so you might want to enable that as well. | ||
152 | |||
153 | For information about how to use these additional functions, see | ||
154 | <file:Documentation/input/yealink.txt>. | ||
155 | |||
156 | To compile this driver as a module, choose M here: the module will be | ||
157 | called yealink. | ||
84 | 158 | ||
85 | config INPUT_UINPUT | 159 | config INPUT_UINPUT |
86 | tristate "User level driver support" | 160 | tristate "User level driver support" |