xref: /openbmc/linux/drivers/media/rc/Kconfig (revision a72594ca)
1
2menuconfig RC_CORE
3	tristate "Remote Controller support"
4	depends on INPUT
5	---help---
6	  Enable support for Remote Controllers on Linux. This is
7	  needed in order to support several video capture adapters,
8	  standalone IR receivers/transmitters, and RF receivers.
9
10	  Enable this option if you have a video capture board even
11	  if you don't need IR, as otherwise, you may not be able to
12	  compile the driver for your adapter.
13
14	  Say Y when you have a TV or an IR device.
15
16if RC_CORE
17source "drivers/media/rc/keymaps/Kconfig"
18
19menuconfig RC_DECODERS
20        bool "Remote controller decoders"
21	depends on RC_CORE
22	default y
23
24if RC_DECODERS
25config LIRC
26	tristate "LIRC interface driver"
27	depends on RC_CORE
28
29	---help---
30	   Enable this option to build the Linux Infrared Remote
31	   Control (LIRC) core device interface driver. The LIRC
32	   interface passes raw IR to and from userspace, where the
33	   LIRC daemon handles protocol decoding for IR reception and
34	   encoding for IR transmitting (aka "blasting").
35
36config IR_LIRC_CODEC
37	tristate "Enable IR to LIRC bridge"
38	depends on RC_CORE
39	depends on LIRC
40	default y
41
42	---help---
43	   Enable this option to pass raw IR to and from userspace via
44	   the LIRC interface.
45
46
47config IR_NEC_DECODER
48	tristate "Enable IR raw decoder for the NEC protocol"
49	depends on RC_CORE
50	select BITREVERSE
51	default y
52
53	---help---
54	   Enable this option if you have IR with NEC protocol, and
55	   if the IR is decoded in software
56
57config IR_RC5_DECODER
58	tristate "Enable IR raw decoder for the RC-5 protocol"
59	depends on RC_CORE
60	select BITREVERSE
61	default y
62
63	---help---
64	   Enable this option if you have IR with RC-5 protocol, and
65	   if the IR is decoded in software
66
67config IR_RC6_DECODER
68	tristate "Enable IR raw decoder for the RC6 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 RC6 protocol, and you need software decoding support.
76
77config IR_JVC_DECODER
78	tristate "Enable IR raw decoder for the JVC 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 JVC protocol, and you need software decoding support.
86
87config IR_SONY_DECODER
88	tristate "Enable IR raw decoder for the Sony protocol"
89	depends on RC_CORE
90	select BITREVERSE
91	default y
92
93	---help---
94	   Enable this option if you have an infrared remote control which
95	   uses the Sony protocol, and you need software decoding support.
96
97config IR_SANYO_DECODER
98	tristate "Enable IR raw decoder for the Sanyo 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 Sanyo protocol (Sanyo, Aiwa, Chinon remotes),
105	   and you need software decoding support.
106
107config IR_SHARP_DECODER
108	tristate "Enable IR raw decoder for the Sharp protocol"
109	depends on RC_CORE
110	default y
111
112	---help---
113	   Enable this option if you have an infrared remote control which
114	   uses the Sharp protocol (Sharp, Denon), and you need software
115	   decoding support.
116
117config IR_MCE_KBD_DECODER
118	tristate "Enable IR raw decoder for the MCE keyboard/mouse protocol"
119	depends on RC_CORE
120	select BITREVERSE
121	default y
122
123	---help---
124	   Enable this option if you have a Microsoft Remote Keyboard for
125	   Windows Media Center Edition, which you would like to use with
126	   a raw IR receiver in your system.
127
128config IR_XMP_DECODER
129	tristate "Enable IR raw decoder for the XMP protocol"
130	depends on RC_CORE
131	select BITREVERSE
132	default y
133
134	---help---
135	   Enable this option if you have IR with XMP protocol, and
136	   if the IR is decoded in software
137endif #RC_DECODERS
138
139menuconfig RC_DEVICES
140	bool "Remote Controller devices"
141	depends on RC_CORE
142
143if RC_DEVICES
144
145config RC_ATI_REMOTE
146	tristate "ATI / X10 based USB RF remote controls"
147	depends on USB_ARCH_HAS_HCD
148	depends on RC_CORE
149	select USB
150	help
151	   Say Y here if you want to use an X10 based USB remote control.
152	   These are RF remotes with USB receivers.
153
154	   Such devices include the ATI remote that comes with many of ATI's
155	   All-In-Wonder video cards, the X10 "Lola" remote, NVIDIA RF remote,
156	   Medion RF remote, and SnapStream FireFly remote.
157
158	   This driver provides mouse pointer, left and right mouse buttons,
159	   and maps all the other remote buttons to keypress events.
160
161	   To compile this driver as a module, choose M here: the module will be
162	   called ati_remote.
163
164config IR_ENE
165	tristate "ENE eHome Receiver/Transceiver (pnp id: ENE0100/ENE02xxx)"
166	depends on PNP
167	depends on RC_CORE
168	---help---
169	   Say Y here to enable support for integrated infrared receiver
170	   /transceiver made by ENE.
171
172	   You can see if you have it by looking at lspnp output.
173	   Output should include ENE0100 ENE0200 or something similar.
174
175	   To compile this driver as a module, choose M here: the
176	   module will be called ene_ir.
177
178config IR_HIX5HD2
179	tristate "Hisilicon hix5hd2 IR remote control"
180	depends on RC_CORE
181	depends on OF || COMPILE_TEST
182	help
183	   Say Y here if you want to use hisilicon hix5hd2 remote control.
184	   To compile this driver as a module, choose M here: the module will be
185	   called ir-hix5hd2.
186
187	   If you're not sure, select N here
188
189config IR_IMON
190	tristate "SoundGraph iMON Receiver and Display"
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 SoundGraph iMON (aka Antec Veris)
196	   IR Receiver and/or LCD/VFD/VGA display.
197
198	   To compile this driver as a module, choose M here: the
199	   module will be called imon.
200
201config IR_MCEUSB
202	tristate "Windows Media Center Ed. eHome Infrared Transceiver"
203	depends on USB_ARCH_HAS_HCD
204	depends on RC_CORE
205	select USB
206	---help---
207	   Say Y here if you want to use a Windows Media Center Edition
208	   eHome Infrared Transceiver.
209
210	   To compile this driver as a module, choose M here: the
211	   module will be called mceusb.
212
213config IR_ITE_CIR
214	tristate "ITE Tech Inc. IT8712/IT8512 Consumer Infrared Transceiver"
215	depends on PNP
216	depends on RC_CORE
217	---help---
218	   Say Y here to enable support for integrated infrared receivers
219	   /transceivers made by ITE Tech Inc. These are found in
220	   several ASUS devices, like the ASUS Digimatrix or the ASUS
221	   EEEBox 1501U.
222
223	   To compile this driver as a module, choose M here: the
224	   module will be called ite-cir.
225
226config IR_FINTEK
227	tristate "Fintek Consumer Infrared Transceiver"
228	depends on PNP
229	depends on RC_CORE
230	---help---
231	   Say Y here to enable support for integrated infrared receiver
232	   /transciever made by Fintek. This chip is found on assorted
233	   Jetway motherboards (and of course, possibly others).
234
235	   To compile this driver as a module, choose M here: the
236	   module will be called fintek-cir.
237
238config IR_MESON
239	tristate "Amlogic Meson IR remote receiver"
240	depends on RC_CORE
241	depends on ARCH_MESON || COMPILE_TEST
242	---help---
243	   Say Y if you want to use the IR remote receiver available
244	   on Amlogic Meson SoCs.
245
246	   To compile this driver as a module, choose M here: the
247	   module will be called meson-ir.
248
249config IR_MTK
250	tristate "Mediatek IR remote receiver"
251	depends on RC_CORE
252	depends on ARCH_MEDIATEK || COMPILE_TEST
253	---help---
254	   Say Y if you want to use the IR remote receiver available
255	   on Mediatek SoCs.
256
257	   To compile this driver as a module, choose M here: the
258	   module will be called mtk-cir.
259
260config IR_NUVOTON
261	tristate "Nuvoton w836x7hg Consumer Infrared Transceiver"
262	depends on PNP
263	depends on RC_CORE
264	---help---
265	   Say Y here to enable support for integrated infrared receiver
266	   /transciever made by Nuvoton (formerly Winbond). This chip is
267	   found in the ASRock ION 330HT, as well as assorted Intel
268	   DP55-series motherboards (and of course, possibly others).
269
270	   To compile this driver as a module, choose M here: the
271	   module will be called nuvoton-cir.
272
273config IR_REDRAT3
274	tristate "RedRat3 IR Transceiver"
275	depends on USB_ARCH_HAS_HCD
276	depends on RC_CORE
277	select NEW_LEDS
278	select LEDS_CLASS
279	select USB
280	---help---
281	   Say Y here if you want to use a RedRat3 Infrared Transceiver.
282
283	   To compile this driver as a module, choose M here: the
284	   module will be called redrat3.
285
286config IR_SPI
287	tristate "SPI connected IR LED"
288	depends on SPI && LIRC
289	depends on OF || COMPILE_TEST
290	---help---
291	  Say Y if you want to use an IR LED connected through SPI bus.
292
293	  To compile this driver as a module, choose M here: the module will be
294	  called ir-spi.
295
296config IR_STREAMZAP
297	tristate "Streamzap PC Remote IR Receiver"
298	depends on USB_ARCH_HAS_HCD
299	depends on RC_CORE
300	select USB
301	---help---
302	   Say Y here if you want to use a Streamzap PC Remote
303	   Infrared Receiver.
304
305	   To compile this driver as a module, choose M here: the
306	   module will be called streamzap.
307
308config IR_WINBOND_CIR
309	tristate "Winbond IR remote control"
310	depends on X86 && PNP
311	depends on RC_CORE
312	select NEW_LEDS
313	select LEDS_CLASS
314	select BITREVERSE
315	---help---
316	   Say Y here if you want to use the IR remote functionality found
317	   in some Winbond SuperI/O chips. Currently only the WPCD376I
318	   chip is supported (included in some Intel Media series
319	   motherboards).
320
321	   To compile this driver as a module, choose M here: the module will
322	   be called winbond_cir.
323
324config IR_IGORPLUGUSB
325	tristate "IgorPlug-USB IR Receiver"
326	depends on USB_ARCH_HAS_HCD
327	depends on RC_CORE
328	select USB
329	---help---
330	   Say Y here if you want to use the IgorPlug-USB IR Receiver by
331	   Igor Cesko. This device is included on the Fit-PC2.
332
333	   Note that this device can only record bursts of 36 IR pulses and
334	   spaces, which is not enough for the NEC, Sanyo and RC-6 protocol.
335
336	   To compile this driver as a module, choose M here: the module will
337	   be called igorplugusb.
338
339config IR_IGUANA
340	tristate "IguanaWorks USB IR Transceiver"
341	depends on USB_ARCH_HAS_HCD
342	depends on RC_CORE
343	select USB
344	---help---
345	   Say Y here if you want to use the IguanaWorks USB IR Transceiver.
346	   Both infrared receive and send are supported. If you want to
347	   change the ID or the pin config, use the user space driver from
348	   IguanaWorks.
349
350	   Only firmware 0x0205 and later is supported.
351
352	   To compile this driver as a module, choose M here: the module will
353	   be called iguanair.
354
355config IR_TTUSBIR
356	tristate "TechnoTrend USB IR Receiver"
357	depends on USB_ARCH_HAS_HCD
358	depends on RC_CORE
359	select USB
360	select NEW_LEDS
361	select LEDS_CLASS
362	---help---
363	   Say Y here if you want to use the TechnoTrend USB IR Receiver. The
364	   driver can control the led.
365
366	   To compile this driver as a module, choose M here: the module will
367	   be called ttusbir.
368
369config IR_RX51
370	tristate "Nokia N900 IR transmitter diode"
371	depends on (OMAP_DM_TIMER && PWM_OMAP_DMTIMER && ARCH_OMAP2PLUS || COMPILE_TEST) && RC_CORE
372	---help---
373	   Say Y or M here if you want to enable support for the IR
374	   transmitter diode built in the Nokia N900 (RX51) device.
375
376	   The driver uses omap DM timers for generating the carrier
377	   wave and pulses.
378
379source "drivers/media/rc/img-ir/Kconfig"
380
381config RC_LOOPBACK
382	tristate "Remote Control Loopback Driver"
383	depends on RC_CORE
384	---help---
385	   Say Y here if you want support for the remote control loopback
386	   driver which allows TX data to be sent back as RX data.
387	   This is mostly useful for debugging purposes.
388
389	   If you're not sure, select N here.
390
391	   To compile this driver as a module, choose M here: the module will
392	   be called rc_loopback.
393
394config IR_GPIO_CIR
395	tristate "GPIO IR remote control"
396	depends on RC_CORE
397	depends on (OF && GPIOLIB) || COMPILE_TEST
398	---help---
399	   Say Y if you want to use GPIO based IR Receiver.
400
401	   To compile this driver as a module, choose M here: the module will
402	   be called gpio-ir-recv.
403
404config IR_GPIO_TX
405	tristate "GPIO IR Bit Banging Transmitter"
406	depends on RC_CORE
407	depends on LIRC
408	depends on (OF && GPIOLIB) || COMPILE_TEST
409	---help---
410	   Say Y if you want to a GPIO based IR transmitter. This is a
411	   bit banging driver.
412
413	   To compile this driver as a module, choose M here: the module will
414	   be called gpio-ir-tx.
415
416config IR_PWM_TX
417	tristate "PWM IR transmitter"
418	depends on RC_CORE
419	depends on LIRC
420	depends on PWM
421	depends on OF || COMPILE_TEST
422	---help---
423	   Say Y if you want to use a PWM based IR transmitter. This is
424	   more power efficient than the bit banging gpio driver.
425
426	   To compile this driver as a module, choose M here: the module will
427	   be called pwm-ir-tx.
428
429config RC_ST
430	tristate "ST remote control receiver"
431	depends on RC_CORE
432	depends on ARCH_STI || COMPILE_TEST
433	---help---
434	   Say Y here if you want support for ST remote control driver
435	   which allows both IR and UHF RX.
436	   The driver passes raw pulse and space information to the LIRC decoder.
437
438	   If you're not sure, select N here.
439
440config IR_SUNXI
441	tristate "SUNXI IR remote control"
442	depends on RC_CORE
443	depends on ARCH_SUNXI || COMPILE_TEST
444	---help---
445	   Say Y if you want to use sunXi internal IR Controller
446
447	   To compile this driver as a module, choose M here: the module will
448	   be called sunxi-ir.
449
450config IR_SERIAL
451	tristate "Homebrew Serial Port Receiver"
452	depends on RC_CORE
453	---help---
454	   Say Y if you want to use Homebrew Serial Port Receivers and
455	   Transceivers.
456
457	   To compile this driver as a module, choose M here: the module will
458	   be called serial-ir.
459
460config IR_SERIAL_TRANSMITTER
461	bool "Serial Port Transmitter"
462	default y
463	depends on IR_SERIAL
464	---help---
465	   Serial Port Transmitter support
466
467config IR_SIR
468        tristate "Built-in SIR IrDA port"
469        depends on RC_CORE
470        ---help---
471	   Say Y if you want to use a IrDA SIR port Transceivers.
472
473	   To compile this driver as a module, choose M here: the module will
474	   be called sir-ir.
475
476config IR_TANGO
477	tristate "Sigma Designs SMP86xx IR decoder"
478	depends on RC_CORE
479	depends on ARCH_TANGO || COMPILE_TEST
480	---help---
481	   Adds support for the HW IR decoder embedded on Sigma Designs
482	   Tango-based systems (SMP86xx, SMP87xx).
483	   The HW decoder supports NEC, RC-5, RC-6 IR protocols.
484	   When compiled as a module, look for tango-ir.
485
486config IR_ZX
487	tristate "ZTE ZX IR remote control"
488	depends on RC_CORE
489	depends on ARCH_ZX || COMPILE_TEST
490	---help---
491	   Say Y if you want to use the IR remote control available
492	   on ZTE ZX family SoCs.
493
494	   To compile this driver as a module, choose M here: the
495	   module will be called zx-irdec.
496
497endif #RC_DEVICES
498
499endif #RC_CORE
500