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 #RC_DECODERS
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_NUVOTON
227	tristate "Nuvoton w836x7hg 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 Nuvoton (formerly Winbond). This chip is
233	   found in the ASRock ION 330HT, as well as assorted Intel
234	   DP55-series motherboards (and of course, possibly others).
235
236	   To compile this driver as a module, choose M here: the
237	   module will be called nuvoton-cir.
238
239config IR_REDRAT3
240	tristate "RedRat3 IR Transceiver"
241	depends on USB_ARCH_HAS_HCD
242	depends on RC_CORE
243	select NEW_LEDS
244	select LEDS_CLASS
245	select USB
246	---help---
247	   Say Y here if you want to use a RedRat3 Infrared Transceiver.
248
249	   To compile this driver as a module, choose M here: the
250	   module will be called redrat3.
251
252config IR_STREAMZAP
253	tristate "Streamzap PC Remote IR Receiver"
254	depends on USB_ARCH_HAS_HCD
255	depends on RC_CORE
256	select USB
257	---help---
258	   Say Y here if you want to use a Streamzap PC Remote
259	   Infrared Receiver.
260
261	   To compile this driver as a module, choose M here: the
262	   module will be called streamzap.
263
264config IR_WINBOND_CIR
265	tristate "Winbond IR remote control"
266	depends on X86 && PNP
267	depends on RC_CORE
268	select NEW_LEDS
269	select LEDS_CLASS
270	select BITREVERSE
271	---help---
272	   Say Y here if you want to use the IR remote functionality found
273	   in some Winbond SuperI/O chips. Currently only the WPCD376I
274	   chip is supported (included in some Intel Media series
275	   motherboards).
276
277	   To compile this driver as a module, choose M here: the module will
278	   be called winbond_cir.
279
280config IR_IGUANA
281	tristate "IguanaWorks USB IR Transceiver"
282	depends on USB_ARCH_HAS_HCD
283	depends on RC_CORE
284	select USB
285	---help---
286	   Say Y here if you want to use the IguanaWorks USB IR Transceiver.
287	   Both infrared receive and send are supported. If you want to
288	   change the ID or the pin config, use the user space driver from
289	   IguanaWorks.
290
291	   Only firmware 0x0205 and later is supported.
292
293	   To compile this driver as a module, choose M here: the module will
294	   be called iguanair.
295
296config IR_TTUSBIR
297	tristate "TechnoTrend USB IR Receiver"
298	depends on USB_ARCH_HAS_HCD
299	depends on RC_CORE
300	select USB
301	select NEW_LEDS
302	select LEDS_CLASS
303	---help---
304	   Say Y here if you want to use the TechnoTrend USB IR Receiver. The
305	   driver can control the led.
306
307	   To compile this driver as a module, choose M here: the module will
308	   be called ttusbir.
309
310config IR_RX51
311	tristate "Nokia N900 IR transmitter diode"
312	depends on OMAP_DM_TIMER && ARCH_OMAP2PLUS && LIRC && !ARCH_MULTIPLATFORM
313	---help---
314	   Say Y or M here if you want to enable support for the IR
315	   transmitter diode built in the Nokia N900 (RX51) device.
316
317	   The driver uses omap DM timers for generating the carrier
318	   wave and pulses.
319
320source "drivers/media/rc/img-ir/Kconfig"
321
322config RC_LOOPBACK
323	tristate "Remote Control Loopback Driver"
324	depends on RC_CORE
325	---help---
326	   Say Y here if you want support for the remote control loopback
327	   driver which allows TX data to be sent back as RX data.
328	   This is mostly useful for debugging purposes.
329
330	   If you're not sure, select N here.
331
332	   To compile this driver as a module, choose M here: the module will
333	   be called rc_loopback.
334
335config IR_GPIO_CIR
336	tristate "GPIO IR remote control"
337	depends on RC_CORE
338	---help---
339	   Say Y if you want to use GPIO based IR Receiver.
340
341	   To compile this driver as a module, choose M here: the module will
342	   be called gpio-ir-recv.
343
344config RC_ST
345	tristate "ST remote control receiver"
346	depends on RC_CORE
347	depends on ARCH_STI || COMPILE_TEST
348	help
349	 Say Y here if you want support for ST remote control driver
350	 which allows both IR and UHF RX.
351	 The driver passes raw pulse and space information to the LIRC decoder.
352
353	 If you're not sure, select N here.
354
355config IR_SUNXI
356    tristate "SUNXI IR remote control"
357    depends on RC_CORE
358    depends on ARCH_SUNXI || COMPILE_TEST
359    ---help---
360      Say Y if you want to use sunXi internal IR Controller
361
362      To compile this driver as a module, choose M here: the module will
363      be called sunxi-ir.
364
365endif #RC_DEVICES
366