1config RC_CORE
2 tristate
3 depends on MEDIA_RC_SUPPORT
4 depends on INPUT
5 default y
6
7source "drivers/media/rc/keymaps/Kconfig"
8
9menuconfig RC_DECODERS
10 bool "Remote controller decoders"
11 depends on RC_CORE
12 default y
13
14if RC_DECODERS
15config LIRC
16 tristate "LIRC interface driver"
17 depends on RC_CORE
18
19 ---help---
20 Enable this option to build the Linux Infrared Remote
21 Control (LIRC) core device interface driver. The LIRC
22 interface passes raw IR to and from userspace, where the
23 LIRC daemon handles protocol decoding for IR reception and
24 encoding for IR transmitting (aka "blasting").
25
26config IR_LIRC_CODEC
27 tristate "Enable IR to LIRC bridge"
28 depends on RC_CORE
29 depends on LIRC
30 default y
31
32 ---help---
33 Enable this option to pass raw IR to and from userspace via
34 the LIRC interface.
35
36
37config IR_NEC_DECODER
38 tristate "Enable IR raw decoder for the NEC protocol"
39 depends on RC_CORE
40 select BITREVERSE
41 default y
42
43 ---help---
44 Enable this option if you have IR with NEC protocol, and
45 if the IR is decoded in software
46
47config IR_RC5_DECODER
48 tristate "Enable IR raw decoder for the RC-5 protocol"
49 depends on RC_CORE
50 select BITREVERSE
51 default y
52
53 ---help---
54 Enable this option if you have IR with RC-5 protocol, and
55 if the IR is decoded in software
56
57config IR_RC6_DECODER
58 tristate "Enable IR raw decoder for the RC6 protocol"
59 depends on RC_CORE
60 select BITREVERSE
61 default y
62
63 ---help---
64 Enable this option if you have an infrared remote control which
65 uses the RC6 protocol, and you need software decoding support.
66
67config IR_JVC_DECODER
68 tristate "Enable IR raw decoder for the JVC protocol"
69 depends on RC_CORE
70 select BITREVERSE
71 default y
72
73 ---help---
74 Enable this option if you have an infrared remote control which
75 uses the JVC protocol, and you need software decoding support.
76
77config IR_SONY_DECODER
78 tristate "Enable IR raw decoder for the Sony protocol"
79 depends on RC_CORE
80 select BITREVERSE
81 default y
82
83 ---help---
84 Enable this option if you have an infrared remote control which
85 uses the Sony protocol, and you need software decoding support.
86
87config IR_SANYO_DECODER
88 tristate "Enable IR raw decoder for the Sanyo protocol"
89 depends on RC_CORE
90 default y
91
92 ---help---
93 Enable this option if you have an infrared remote control which
94 uses the Sanyo protocol (Sanyo, Aiwa, Chinon remotes),
95 and you need software decoding support.
96
97config IR_SHARP_DECODER
98 tristate "Enable IR raw decoder for the Sharp protocol"
99 depends on RC_CORE
100 default y
101
102 ---help---
103 Enable this option if you have an infrared remote control which
104 uses the Sharp protocol, and you need software decoding support.
105
106config IR_MCE_KBD_DECODER
107 tristate "Enable IR raw decoder for the MCE keyboard/mouse protocol"
108 depends on RC_CORE
109 select BITREVERSE
110 default y
111
112 ---help---
113 Enable this option if you have a Microsoft Remote Keyboard for
114 Windows Media Center Edition, which you would like to use with
115 a raw IR receiver in your system.
116
117config IR_XMP_DECODER
118 tristate "Enable IR raw decoder for the XMP protocol"
119 depends on RC_CORE
120 select BITREVERSE
121 default y
122
123 ---help---
124 Enable this option if you have IR with XMP protocol, and
125 if the IR is decoded in software
126endif
127
128menuconfig RC_DEVICES
129 bool "Remote Controller devices"
130 depends on RC_CORE
131
132if RC_DEVICES
133
134config RC_ATI_REMOTE
135 tristate "ATI / X10 based USB RF remote controls"
136 depends on USB_ARCH_HAS_HCD
137 depends on RC_CORE
138 select USB
139 help
140 Say Y here if you want to use an X10 based USB remote control.
141 These are RF remotes with USB receivers.
142
143 Such devices include the ATI remote that comes with many of ATI's
144 All-In-Wonder video cards, the X10 "Lola" remote, NVIDIA RF remote,
145 Medion RF remote, and SnapStream FireFly remote.
146
147 This driver provides mouse pointer, left and right mouse buttons,
148 and maps all the other remote buttons to keypress events.
149
150 To compile this driver as a module, choose M here: the module will be
151 called ati_remote.
152
153config IR_ENE
154 tristate "ENE eHome Receiver/Transceiver (pnp id: ENE0100/ENE02xxx)"
155 depends on PNP
156 depends on RC_CORE
157 ---help---
158 Say Y here to enable support for integrated infrared receiver
159 /transceiver made by ENE.
160
161 You can see if you have it by looking at lspnp output.
162 Output should include ENE0100 ENE0200 or something similar.
163
164 To compile this driver as a module, choose M here: the
165 module will be called ene_ir.
166
167config IR_HIX5HD2
168 tristate "Hisilicon hix5hd2 IR remote control"
169 depends on RC_CORE
170 help
171 Say Y here if you want to use hisilicon hix5hd2 remote control.
172 To compile this driver as a module, choose M here: the module will be
173 called ir-hix5hd2.
174
175 If you're not sure, select N here
176
177config IR_IMON
178 tristate "SoundGraph iMON Receiver and Display"
179 depends on USB_ARCH_HAS_HCD
180 depends on RC_CORE
181 select USB
182 ---help---
183 Say Y here if you want to use a SoundGraph iMON (aka Antec Veris)
184 IR Receiver and/or LCD/VFD/VGA display.
185
186 To compile this driver as a module, choose M here: the
187 module will be called imon.
188
189config IR_MCEUSB
190 tristate "Windows Media Center Ed. eHome Infrared Transceiver"
191 depends on USB_ARCH_HAS_HCD
192 depends on RC_CORE
193 select USB
194 ---help---
195 Say Y here if you want to use a Windows Media Center Edition
196 eHome Infrared Transceiver.
197
198 To compile this driver as a module, choose M here: the
199 module will be called mceusb.
200
201config IR_ITE_CIR
202 tristate "ITE Tech Inc. IT8712/IT8512 Consumer Infrared Transceiver"
203 depends on PNP
204 depends on RC_CORE
205 ---help---
206 Say Y here to enable support for integrated infrared receivers
207 /transceivers made by ITE Tech Inc. These are found in
208 several ASUS devices, like the ASUS Digimatrix or the ASUS
209 EEEBox 1501U.
210
211 To compile this driver as a module, choose M here: the
212 module will be called ite-cir.
213
214config IR_FINTEK
215 tristate "Fintek Consumer Infrared Transceiver"
216 depends on PNP
217 depends on RC_CORE
218 ---help---
219 Say Y here to enable support for integrated infrared receiver
220 /transciever made by Fintek. This chip is found on assorted
221 Jetway motherboards (and of course, possibly others).
222
223 To compile this driver as a module, choose M here: the
224 module will be called fintek-cir.
225
226config IR_MESON
227 tristate "Amlogic Meson IR remote receiver"
228 depends on RC_CORE
229 depends on ARCH_MESON || COMPILE_TEST
230 ---help---
231 Say Y if you want to use the IR remote receiver available
232 on Amlogic Meson SoCs.
233
234 To compile this driver as a module, choose M here: the
235 module will be called meson-ir.
236
237config IR_NUVOTON
238 tristate "Nuvoton w836x7hg Consumer Infrared Transceiver"
239 depends on PNP
240 depends on RC_CORE
241 ---help---
242 Say Y here to enable support for integrated infrared receiver
243 /transciever made by Nuvoton (formerly Winbond). This chip is
244 found in the ASRock ION 330HT, as well as assorted Intel
245 DP55-series motherboards (and of course, possibly others).
246
247 To compile this driver as a module, choose M here: the
248 module will be called nuvoton-cir.
249
250config IR_REDRAT3
251 tristate "RedRat3 IR Transceiver"
252 depends on USB_ARCH_HAS_HCD
253 depends on RC_CORE
254 select NEW_LEDS
255 select LEDS_CLASS
256 select USB
257 ---help---
258 Say Y here if you want to use a RedRat3 Infrared Transceiver.
259
260 To compile this driver as a module, choose M here: the
261 module will be called redrat3.
262
263config IR_STREAMZAP
264 tristate "Streamzap PC Remote IR Receiver"
265 depends on USB_ARCH_HAS_HCD
266 depends on RC_CORE
267 select USB
268 ---help---
269 Say Y here if you want to use a Streamzap PC Remote
270 Infrared Receiver.
271
272 To compile this driver as a module, choose M here: the
273 module will be called streamzap.
274
275config IR_WINBOND_CIR
276 tristate "Winbond IR remote control"
277 depends on X86 && PNP
278 depends on RC_CORE
279 select NEW_LEDS
280 select LEDS_CLASS
281 select BITREVERSE
282 ---help---
283 Say Y here if you want to use the IR remote functionality found
284 in some Winbond SuperI/O chips. Currently only the WPCD376I
285 chip is supported (included in some Intel Media series
286 motherboards).
287
288 To compile this driver as a module, choose M here: the module will
289 be called winbond_cir.
290
291config IR_IGORPLUGUSB
292 tristate "IgorPlug-USB IR Receiver"
293 depends on USB_ARCH_HAS_HCD
294 depends on RC_CORE
295 select USB
296 ---help---
297 Say Y here if you want to use the IgorPlug-USB IR Receiver by
298 Igor Cesko. This device is included on the Fit-PC2.
299
300 Note that this device can only record bursts of 36 IR pulses and
301 spaces, which is not enough for the NEC, Sanyo and RC-6 protocol.
302
303 To compile this driver as a module, choose M here: the module will
304 be called igorplugusb.
305
306config IR_IGUANA
307 tristate "IguanaWorks USB IR Transceiver"
308 depends on USB_ARCH_HAS_HCD
309 depends on RC_CORE
310 select USB
311 ---help---
312 Say Y here if you want to use the IguanaWorks USB IR Transceiver.
313 Both infrared receive and send are supported. If you want to
314 change the ID or the pin config, use the user space driver from
315 IguanaWorks.
316
317 Only firmware 0x0205 and later is supported.
318
319 To compile this driver as a module, choose M here: the module will
320 be called iguanair.
321
322config IR_TTUSBIR
323 tristate "TechnoTrend USB IR Receiver"
324 depends on USB_ARCH_HAS_HCD
325 depends on RC_CORE
326 select USB
327 select NEW_LEDS
328 select LEDS_CLASS
329 ---help---
330 Say Y here if you want to use the TechnoTrend USB IR Receiver. The
331 driver can control the led.
332
333 To compile this driver as a module, choose M here: the module will
334 be called ttusbir.
335
336config IR_RX51
337 tristate "Nokia N900 IR transmitter diode"
338 depends on OMAP_DM_TIMER && ARCH_OMAP2PLUS && LIRC && !ARCH_MULTIPLATFORM
339 ---help---
340 Say Y or M here if you want to enable support for the IR
341 transmitter diode built in the Nokia N900 (RX51) device.
342
343 The driver uses omap DM timers for generating the carrier
344 wave and pulses.
345
346source "drivers/media/rc/img-ir/Kconfig"
347
348config RC_LOOPBACK
349 tristate "Remote Control Loopback Driver"
350 depends on RC_CORE
351 ---help---
352 Say Y here if you want support for the remote control loopback
353 driver which allows TX data to be sent back as RX data.
354 This is mostly useful for debugging purposes.
355
356 If you're not sure, select N here.
357
358 To compile this driver as a module, choose M here: the module will
359 be called rc_loopback.
360
361config IR_GPIO_CIR
362 tristate "GPIO IR remote control"
363 depends on RC_CORE
364 ---help---
365 Say Y if you want to use GPIO based IR Receiver.
366
367 To compile this driver as a module, choose M here: the module will
368 be called gpio-ir-recv.
369
370config RC_ST
371 tristate "ST remote control receiver"
372 depends on RC_CORE
373 depends on ARCH_STI || COMPILE_TEST
374 ---help---
375 Say Y here if you want support for ST remote control driver
376 which allows both IR and UHF RX.
377 The driver passes raw pulse and space information to the LIRC decoder.
378
379 If you're not sure, select N here.
380
381config IR_SUNXI
382 tristate "SUNXI IR remote control"
383 depends on RC_CORE
384 depends on ARCH_SUNXI || COMPILE_TEST
385 ---help---
386 Say Y if you want to use sunXi internal IR Controller
387
388 To compile this driver as a module, choose M here: the module will
389 be called sunxi-ir.
390
391endif
392
