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