diff options
-rw-r--r-- | drivers/input/misc/Kconfig | 88 | ||||
-rw-r--r-- | drivers/input/misc/Makefile | 9 | ||||
-rw-r--r-- | drivers/input/misc/ati_remote.c (renamed from drivers/usb/input/ati_remote.c) | 0 | ||||
-rw-r--r-- | drivers/input/misc/ati_remote2.c (renamed from drivers/usb/input/ati_remote2.c) | 0 | ||||
-rw-r--r-- | drivers/input/misc/keyspan_remote.c (renamed from drivers/usb/input/keyspan_remote.c) | 0 | ||||
-rw-r--r-- | drivers/input/misc/map_to_7segment.h (renamed from drivers/usb/input/map_to_7segment.h) | 0 | ||||
-rw-r--r-- | drivers/input/misc/powermate.c (renamed from drivers/usb/input/powermate.c) | 0 | ||||
-rw-r--r-- | drivers/input/misc/yealink.c (renamed from drivers/usb/input/yealink.c) | 2 | ||||
-rw-r--r-- | drivers/input/misc/yealink.h (renamed from drivers/usb/input/yealink.h) | 0 | ||||
-rw-r--r-- | drivers/usb/Kconfig | 2 | ||||
-rw-r--r-- | drivers/usb/Makefile | 3 | ||||
-rw-r--r-- | drivers/usb/input/Kconfig | 77 | ||||
-rw-r--r-- | drivers/usb/input/Makefile | 13 |
13 files changed, 89 insertions, 105 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" |
diff --git a/drivers/input/misc/Makefile b/drivers/input/misc/Makefile index 21e3cca0d33e..8b2f7799e25c 100644 --- a/drivers/input/misc/Makefile +++ b/drivers/input/misc/Makefile | |||
@@ -8,9 +8,14 @@ obj-$(CONFIG_INPUT_POLLDEV) += input-polldev.o | |||
8 | obj-$(CONFIG_INPUT_SPARCSPKR) += sparcspkr.o | 8 | obj-$(CONFIG_INPUT_SPARCSPKR) += sparcspkr.o |
9 | obj-$(CONFIG_INPUT_PCSPKR) += pcspkr.o | 9 | obj-$(CONFIG_INPUT_PCSPKR) += pcspkr.o |
10 | obj-$(CONFIG_INPUT_M68K_BEEP) += m68kspkr.o | 10 | obj-$(CONFIG_INPUT_M68K_BEEP) += m68kspkr.o |
11 | obj-$(CONFIG_INPUT_UINPUT) += uinput.o | 11 | obj-$(CONFIG_INPUT_IXP4XX_BEEPER) += ixp4xx-beeper.o |
12 | obj-$(CONFIG_INPUT_COBALT_BTNS) += cobalt_btns.o | 12 | obj-$(CONFIG_INPUT_COBALT_BTNS) += cobalt_btns.o |
13 | obj-$(CONFIG_INPUT_WISTRON_BTNS) += wistron_btns.o | 13 | obj-$(CONFIG_INPUT_WISTRON_BTNS) += wistron_btns.o |
14 | obj-$(CONFIG_INPUT_ATLAS_BTNS) += atlas_btns.o | 14 | obj-$(CONFIG_INPUT_ATLAS_BTNS) += atlas_btns.o |
15 | obj-$(CONFIG_INPUT_ATI_REMOTE) += ati_remote.o | ||
16 | obj-$(CONFIG_INPUT_ATI_REMOTE2) += ati_remote2.o | ||
17 | obj-$(CONFIG_INPUT_KEYSPAN_REMOTE) += keyspan_remote.o | ||
18 | obj-$(CONFIG_INPUT_POWERMATE) += powermate.o | ||
19 | obj-$(CONFIG_INPUT_YEALINK) += yealink.o | ||
15 | obj-$(CONFIG_HP_SDC_RTC) += hp_sdc_rtc.o | 20 | obj-$(CONFIG_HP_SDC_RTC) += hp_sdc_rtc.o |
16 | obj-$(CONFIG_INPUT_IXP4XX_BEEPER) += ixp4xx-beeper.o | 21 | obj-$(CONFIG_INPUT_UINPUT) += uinput.o |
diff --git a/drivers/usb/input/ati_remote.c b/drivers/input/misc/ati_remote.c index 471aab206443..471aab206443 100644 --- a/drivers/usb/input/ati_remote.c +++ b/drivers/input/misc/ati_remote.c | |||
diff --git a/drivers/usb/input/ati_remote2.c b/drivers/input/misc/ati_remote2.c index 1031543e5c3f..1031543e5c3f 100644 --- a/drivers/usb/input/ati_remote2.c +++ b/drivers/input/misc/ati_remote2.c | |||
diff --git a/drivers/usb/input/keyspan_remote.c b/drivers/input/misc/keyspan_remote.c index 1bffc9fa98c2..1bffc9fa98c2 100644 --- a/drivers/usb/input/keyspan_remote.c +++ b/drivers/input/misc/keyspan_remote.c | |||
diff --git a/drivers/usb/input/map_to_7segment.h b/drivers/input/misc/map_to_7segment.h index a424094d9fe2..a424094d9fe2 100644 --- a/drivers/usb/input/map_to_7segment.h +++ b/drivers/input/misc/map_to_7segment.h | |||
diff --git a/drivers/usb/input/powermate.c b/drivers/input/misc/powermate.c index 448a470d28f2..448a470d28f2 100644 --- a/drivers/usb/input/powermate.c +++ b/drivers/input/misc/powermate.c | |||
diff --git a/drivers/usb/input/yealink.c b/drivers/input/misc/yealink.c index fc645b299189..ab15880fd566 100644 --- a/drivers/usb/input/yealink.c +++ b/drivers/input/misc/yealink.c | |||
@@ -29,7 +29,7 @@ | |||
29 | * This driver is based on: | 29 | * This driver is based on: |
30 | * - the usbb2k-api http://savannah.nongnu.org/projects/usbb2k-api/ | 30 | * - the usbb2k-api http://savannah.nongnu.org/projects/usbb2k-api/ |
31 | * - information from http://memeteau.free.fr/usbb2k | 31 | * - information from http://memeteau.free.fr/usbb2k |
32 | * - the xpad-driver drivers/usb/input/xpad.c | 32 | * - the xpad-driver drivers/input/joystick/xpad.c |
33 | * | 33 | * |
34 | * Thanks to: | 34 | * Thanks to: |
35 | * - Olivier Vandorpe, for providing the usbb2k-api. | 35 | * - Olivier Vandorpe, for providing the usbb2k-api. |
diff --git a/drivers/usb/input/yealink.h b/drivers/input/misc/yealink.h index 48af0be9cbdf..48af0be9cbdf 100644 --- a/drivers/usb/input/yealink.h +++ b/drivers/input/misc/yealink.h | |||
diff --git a/drivers/usb/Kconfig b/drivers/usb/Kconfig index 9980a4ddfed9..b847bbc8b0e1 100644 --- a/drivers/usb/Kconfig +++ b/drivers/usb/Kconfig | |||
@@ -85,8 +85,6 @@ source "drivers/usb/class/Kconfig" | |||
85 | 85 | ||
86 | source "drivers/usb/storage/Kconfig" | 86 | source "drivers/usb/storage/Kconfig" |
87 | 87 | ||
88 | source "drivers/usb/input/Kconfig" | ||
89 | |||
90 | source "drivers/usb/image/Kconfig" | 88 | source "drivers/usb/image/Kconfig" |
91 | 89 | ||
92 | source "drivers/usb/net/Kconfig" | 90 | source "drivers/usb/net/Kconfig" |
diff --git a/drivers/usb/Makefile b/drivers/usb/Makefile index 7059a64637a8..0ef090b1b37c 100644 --- a/drivers/usb/Makefile +++ b/drivers/usb/Makefile | |||
@@ -23,9 +23,6 @@ obj-$(CONFIG_USB_PRINTER) += class/ | |||
23 | obj-$(CONFIG_USB_STORAGE) += storage/ | 23 | obj-$(CONFIG_USB_STORAGE) += storage/ |
24 | obj-$(CONFIG_USB) += storage/ | 24 | obj-$(CONFIG_USB) += storage/ |
25 | 25 | ||
26 | obj-$(CONFIG_USB_ATI_REMOTE) += input/ | ||
27 | obj-$(CONFIG_USB_POWERMATE) += input/ | ||
28 | |||
29 | obj-$(CONFIG_USB_CATC) += net/ | 26 | obj-$(CONFIG_USB_CATC) += net/ |
30 | obj-$(CONFIG_USB_KAWETH) += net/ | 27 | obj-$(CONFIG_USB_KAWETH) += net/ |
31 | obj-$(CONFIG_USB_PEGASUS) += net/ | 28 | obj-$(CONFIG_USB_PEGASUS) += net/ |
diff --git a/drivers/usb/input/Kconfig b/drivers/usb/input/Kconfig deleted file mode 100644 index 4959dcf3cb4d..000000000000 --- a/drivers/usb/input/Kconfig +++ /dev/null | |||
@@ -1,77 +0,0 @@ | |||
1 | # | ||
2 | # USB Input driver configuration | ||
3 | # | ||
4 | comment "USB Input Devices" | ||
5 | depends on USB | ||
6 | |||
7 | config USB_POWERMATE | ||
8 | tristate "Griffin PowerMate and Contour Jog support" | ||
9 | depends on USB && INPUT | ||
10 | ---help--- | ||
11 | Say Y here if you want to use Griffin PowerMate or Contour Jog devices. | ||
12 | These are aluminum dials which can measure clockwise and anticlockwise | ||
13 | rotation. The dial also acts as a pushbutton. The base contains an LED | ||
14 | which can be instructed to pulse or to switch to a particular intensity. | ||
15 | |||
16 | You can download userspace tools from | ||
17 | <http://sowerbutts.com/powermate/>. | ||
18 | |||
19 | To compile this driver as a module, choose M here: the | ||
20 | module will be called powermate. | ||
21 | |||
22 | config USB_YEALINK | ||
23 | tristate "Yealink usb-p1k voip phone" | ||
24 | depends on USB && INPUT && EXPERIMENTAL | ||
25 | ---help--- | ||
26 | Say Y here if you want to enable keyboard and LCD functions of the | ||
27 | Yealink usb-p1k usb phones. The audio part is enabled by the generic | ||
28 | usb sound driver, so you might want to enable that as well. | ||
29 | |||
30 | For information about how to use these additional functions, see | ||
31 | <file:Documentation/input/yealink.txt>. | ||
32 | |||
33 | To compile this driver as a module, choose M here: the module will be | ||
34 | called yealink. | ||
35 | |||
36 | config USB_ATI_REMOTE | ||
37 | tristate "ATI / X10 USB RF remote control" | ||
38 | depends on USB && INPUT | ||
39 | ---help--- | ||
40 | Say Y here if you want to use an ATI or X10 "Lola" USB remote control. | ||
41 | These are RF remotes with USB receivers. | ||
42 | The ATI remote comes with many of ATI's All-In-Wonder video cards. | ||
43 | The X10 "Lola" remote is available at: | ||
44 | <http://www.x10.com/products/lola_sg1.htm> | ||
45 | This driver provides mouse pointer, left and right mouse buttons, | ||
46 | and maps all the other remote buttons to keypress events. | ||
47 | |||
48 | To compile this driver as a module, choose M here: the module will be | ||
49 | called ati_remote. | ||
50 | |||
51 | config USB_ATI_REMOTE2 | ||
52 | tristate "ATI / Philips USB RF remote control" | ||
53 | depends on USB && INPUT | ||
54 | ---help--- | ||
55 | Say Y here if you want to use an ATI or Philips USB RF remote control. | ||
56 | These are RF remotes with USB receivers. | ||
57 | ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards | ||
58 | and is also available as a separate product. | ||
59 | This driver provides mouse pointer, left and right mouse buttons, | ||
60 | and maps all the other remote buttons to keypress events. | ||
61 | |||
62 | To compile this driver as a module, choose M here: the module will be | ||
63 | called ati_remote2. | ||
64 | |||
65 | config USB_KEYSPAN_REMOTE | ||
66 | tristate "Keyspan DMR USB remote control (EXPERIMENTAL)" | ||
67 | depends on USB && INPUT && EXPERIMENTAL | ||
68 | ---help--- | ||
69 | Say Y here if you want to use a Keyspan DMR USB remote control. | ||
70 | Currently only the UIA-11 type of receiver has been tested. The tag | ||
71 | on the receiver that connects to the USB port should have a P/N that | ||
72 | will tell you what type of DMR you have. The UIA-10 type is not | ||
73 | supported at this time. This driver maps all buttons to keypress | ||
74 | events. | ||
75 | |||
76 | To compile this driver as a module, choose M here: the module will | ||
77 | be called keyspan_remote. | ||
diff --git a/drivers/usb/input/Makefile b/drivers/usb/input/Makefile deleted file mode 100644 index 91df130909e6..000000000000 --- a/drivers/usb/input/Makefile +++ /dev/null | |||
@@ -1,13 +0,0 @@ | |||
1 | # | ||
2 | # Makefile for the USB input drivers | ||
3 | # | ||
4 | |||
5 | obj-$(CONFIG_USB_ATI_REMOTE) += ati_remote.o | ||
6 | obj-$(CONFIG_USB_ATI_REMOTE2) += ati_remote2.o | ||
7 | obj-$(CONFIG_USB_KEYSPAN_REMOTE) += keyspan_remote.o | ||
8 | obj-$(CONFIG_USB_POWERMATE) += powermate.o | ||
9 | obj-$(CONFIG_USB_YEALINK) += yealink.o | ||
10 | |||
11 | ifeq ($(CONFIG_USB_DEBUG),y) | ||
12 | EXTRA_CFLAGS += -DDEBUG | ||
13 | endif | ||