xref: /openbmc/linux/drivers/media/rc/Kconfig (revision dea54fba)
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 (Sharp, Denon), and you need software
105	   decoding support.
106
107config IR_MCE_KBD_DECODER
108	tristate "Enable IR raw decoder for the MCE keyboard/mouse protocol"
109	depends on RC_CORE
110	select BITREVERSE
111	default y
112
113	---help---
114	   Enable this option if you have a Microsoft Remote Keyboard for
115	   Windows Media Center Edition, which you would like to use with
116	   a raw IR receiver in your system.
117
118config IR_XMP_DECODER
119	tristate "Enable IR raw decoder for the XMP protocol"
120	depends on RC_CORE
121	select BITREVERSE
122	default y
123
124	---help---
125	   Enable this option if you have IR with XMP protocol, and
126	   if the IR is decoded in software
127endif #RC_DECODERS
128
129menuconfig RC_DEVICES
130	bool "Remote Controller devices"
131	depends on RC_CORE
132
133if RC_DEVICES
134
135config RC_ATI_REMOTE
136	tristate "ATI / X10 based USB RF remote controls"
137	depends on USB_ARCH_HAS_HCD
138	depends on RC_CORE
139	select USB
140	help
141	   Say Y here if you want to use an X10 based USB remote control.
142	   These are RF remotes with USB receivers.
143
144	   Such devices include the ATI remote that comes with many of ATI's
145	   All-In-Wonder video cards, the X10 "Lola" remote, NVIDIA RF remote,
146	   Medion RF remote, and SnapStream FireFly remote.
147
148	   This driver provides mouse pointer, left and right mouse buttons,
149	   and maps all the other remote buttons to keypress events.
150
151	   To compile this driver as a module, choose M here: the module will be
152	   called ati_remote.
153
154config IR_ENE
155	tristate "ENE eHome Receiver/Transceiver (pnp id: ENE0100/ENE02xxx)"
156	depends on PNP
157	depends on RC_CORE
158	---help---
159	   Say Y here to enable support for integrated infrared receiver
160	   /transceiver made by ENE.
161
162	   You can see if you have it by looking at lspnp output.
163	   Output should include ENE0100 ENE0200 or something similar.
164
165	   To compile this driver as a module, choose M here: the
166	   module will be called ene_ir.
167
168config IR_HIX5HD2
169	tristate "Hisilicon hix5hd2 IR remote control"
170	depends on RC_CORE
171	help
172	   Say Y here if you want to use hisilicon hix5hd2 remote control.
173	   To compile this driver as a module, choose M here: the module will be
174	   called ir-hix5hd2.
175
176	   If you're not sure, select N here
177
178config IR_IMON
179	tristate "SoundGraph iMON Receiver and Display"
180	depends on USB_ARCH_HAS_HCD
181	depends on RC_CORE
182	select USB
183	---help---
184	   Say Y here if you want to use a SoundGraph iMON (aka Antec Veris)
185	   IR Receiver and/or LCD/VFD/VGA display.
186
187	   To compile this driver as a module, choose M here: the
188	   module will be called imon.
189
190config IR_MCEUSB
191	tristate "Windows Media Center Ed. eHome Infrared Transceiver"
192	depends on USB_ARCH_HAS_HCD
193	depends on RC_CORE
194	select USB
195	---help---
196	   Say Y here if you want to use a Windows Media Center Edition
197	   eHome Infrared Transceiver.
198
199	   To compile this driver as a module, choose M here: the
200	   module will be called mceusb.
201
202config IR_ITE_CIR
203	tristate "ITE Tech Inc. IT8712/IT8512 Consumer Infrared Transceiver"
204	depends on PNP
205	depends on RC_CORE
206	---help---
207	   Say Y here to enable support for integrated infrared receivers
208	   /transceivers made by ITE Tech Inc. These are found in
209	   several ASUS devices, like the ASUS Digimatrix or the ASUS
210	   EEEBox 1501U.
211
212	   To compile this driver as a module, choose M here: the
213	   module will be called ite-cir.
214
215config IR_FINTEK
216	tristate "Fintek Consumer Infrared Transceiver"
217	depends on PNP
218	depends on RC_CORE
219	---help---
220	   Say Y here to enable support for integrated infrared receiver
221	   /transciever made by Fintek. This chip is found on assorted
222	   Jetway motherboards (and of course, possibly others).
223
224	   To compile this driver as a module, choose M here: the
225	   module will be called fintek-cir.
226
227config IR_MESON
228	tristate "Amlogic Meson IR remote receiver"
229	depends on RC_CORE
230	depends on ARCH_MESON || COMPILE_TEST
231	---help---
232	   Say Y if you want to use the IR remote receiver available
233	   on Amlogic Meson SoCs.
234
235	   To compile this driver as a module, choose M here: the
236	   module will be called meson-ir.
237
238config IR_MTK
239	tristate "Mediatek IR remote receiver"
240	depends on RC_CORE
241	depends on ARCH_MEDIATEK || COMPILE_TEST
242	---help---
243	   Say Y if you want to use the IR remote receiver available
244	   on Mediatek SoCs.
245
246	   To compile this driver as a module, choose M here: the
247	   module will be called mtk-cir.
248
249config IR_NUVOTON
250	tristate "Nuvoton w836x7hg Consumer Infrared Transceiver"
251	depends on PNP
252	depends on RC_CORE
253	---help---
254	   Say Y here to enable support for integrated infrared receiver
255	   /transciever made by Nuvoton (formerly Winbond). This chip is
256	   found in the ASRock ION 330HT, as well as assorted Intel
257	   DP55-series motherboards (and of course, possibly others).
258
259	   To compile this driver as a module, choose M here: the
260	   module will be called nuvoton-cir.
261
262config IR_REDRAT3
263	tristate "RedRat3 IR Transceiver"
264	depends on USB_ARCH_HAS_HCD
265	depends on RC_CORE
266	select NEW_LEDS
267	select LEDS_CLASS
268	select USB
269	---help---
270	   Say Y here if you want to use a RedRat3 Infrared Transceiver.
271
272	   To compile this driver as a module, choose M here: the
273	   module will be called redrat3.
274
275config IR_SPI
276	tristate "SPI connected IR LED"
277	depends on SPI && LIRC
278	---help---
279	  Say Y if you want to use an IR LED connected through SPI bus.
280
281	  To compile this driver as a module, choose M here: the module will be
282	  called ir-spi.
283
284config IR_STREAMZAP
285	tristate "Streamzap PC Remote IR Receiver"
286	depends on USB_ARCH_HAS_HCD
287	depends on RC_CORE
288	select USB
289	---help---
290	   Say Y here if you want to use a Streamzap PC Remote
291	   Infrared Receiver.
292
293	   To compile this driver as a module, choose M here: the
294	   module will be called streamzap.
295
296config IR_WINBOND_CIR
297	tristate "Winbond IR remote control"
298	depends on X86 && PNP
299	depends on RC_CORE
300	select NEW_LEDS
301	select LEDS_CLASS
302	select BITREVERSE
303	---help---
304	   Say Y here if you want to use the IR remote functionality found
305	   in some Winbond SuperI/O chips. Currently only the WPCD376I
306	   chip is supported (included in some Intel Media series
307	   motherboards).
308
309	   To compile this driver as a module, choose M here: the module will
310	   be called winbond_cir.
311
312config IR_IGORPLUGUSB
313	tristate "IgorPlug-USB IR Receiver"
314	depends on USB_ARCH_HAS_HCD
315	depends on RC_CORE
316	select USB
317	---help---
318	   Say Y here if you want to use the IgorPlug-USB IR Receiver by
319	   Igor Cesko. This device is included on the Fit-PC2.
320
321	   Note that this device can only record bursts of 36 IR pulses and
322	   spaces, which is not enough for the NEC, Sanyo and RC-6 protocol.
323
324	   To compile this driver as a module, choose M here: the module will
325	   be called igorplugusb.
326
327config IR_IGUANA
328	tristate "IguanaWorks USB IR Transceiver"
329	depends on USB_ARCH_HAS_HCD
330	depends on RC_CORE
331	select USB
332	---help---
333	   Say Y here if you want to use the IguanaWorks USB IR Transceiver.
334	   Both infrared receive and send are supported. If you want to
335	   change the ID or the pin config, use the user space driver from
336	   IguanaWorks.
337
338	   Only firmware 0x0205 and later is supported.
339
340	   To compile this driver as a module, choose M here: the module will
341	   be called iguanair.
342
343config IR_TTUSBIR
344	tristate "TechnoTrend USB IR Receiver"
345	depends on USB_ARCH_HAS_HCD
346	depends on RC_CORE
347	select USB
348	select NEW_LEDS
349	select LEDS_CLASS
350	---help---
351	   Say Y here if you want to use the TechnoTrend USB IR Receiver. The
352	   driver can control the led.
353
354	   To compile this driver as a module, choose M here: the module will
355	   be called ttusbir.
356
357config IR_RX51
358	tristate "Nokia N900 IR transmitter diode"
359	depends on (OMAP_DM_TIMER && PWM_OMAP_DMTIMER && ARCH_OMAP2PLUS || COMPILE_TEST) && RC_CORE
360	---help---
361	   Say Y or M here if you want to enable support for the IR
362	   transmitter diode built in the Nokia N900 (RX51) device.
363
364	   The driver uses omap DM timers for generating the carrier
365	   wave and pulses.
366
367source "drivers/media/rc/img-ir/Kconfig"
368
369config RC_LOOPBACK
370	tristate "Remote Control Loopback Driver"
371	depends on RC_CORE
372	---help---
373	   Say Y here if you want support for the remote control loopback
374	   driver which allows TX data to be sent back as RX data.
375	   This is mostly useful for debugging purposes.
376
377	   If you're not sure, select N here.
378
379	   To compile this driver as a module, choose M here: the module will
380	   be called rc_loopback.
381
382config IR_GPIO_CIR
383	tristate "GPIO IR remote control"
384	depends on RC_CORE
385	---help---
386	   Say Y if you want to use GPIO based IR Receiver.
387
388	   To compile this driver as a module, choose M here: the module will
389	   be called gpio-ir-recv.
390
391config RC_ST
392	tristate "ST remote control receiver"
393	depends on RC_CORE
394	depends on ARCH_STI || COMPILE_TEST
395	---help---
396	   Say Y here if you want support for ST remote control driver
397	   which allows both IR and UHF RX.
398	   The driver passes raw pulse and space information to the LIRC decoder.
399
400	   If you're not sure, select N here.
401
402config IR_SUNXI
403	tristate "SUNXI IR remote control"
404	depends on RC_CORE
405	depends on ARCH_SUNXI || COMPILE_TEST
406	---help---
407	   Say Y if you want to use sunXi internal IR Controller
408
409	   To compile this driver as a module, choose M here: the module will
410	   be called sunxi-ir.
411
412config IR_SERIAL
413	tristate "Homebrew Serial Port Receiver"
414	depends on RC_CORE
415	---help---
416	   Say Y if you want to use Homebrew Serial Port Receivers and
417	   Transceivers.
418
419	   To compile this driver as a module, choose M here: the module will
420	   be called serial-ir.
421
422config IR_SERIAL_TRANSMITTER
423	bool "Serial Port Transmitter"
424	default y
425	depends on IR_SERIAL
426	---help---
427	   Serial Port Transmitter support
428
429config IR_SIR
430        tristate "Built-in SIR IrDA port"
431        depends on RC_CORE
432        ---help---
433	   Say Y if you want to use a IrDA SIR port Transceivers.
434
435	   To compile this driver as a module, choose M here: the module will
436	   be called sir-ir.
437
438endif #RC_DEVICES
439