3 depends on MEDIA_RC_SUPPORT
7 source "drivers/media/rc/keymaps/Kconfig"
10 bool "Remote controller decoders"
16 tristate "LIRC interface driver"
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").
27 tristate "Enable IR to LIRC bridge"
33 Enable this option to pass raw IR to and from userspace via
38 tristate "Enable IR raw decoder for the NEC protocol"
44 Enable this option if you have IR with NEC protocol, and
45 if the IR is decoded in software
48 tristate "Enable IR raw decoder for the RC-5 protocol"
54 Enable this option if you have IR with RC-5 protocol, and
55 if the IR is decoded in software
58 tristate "Enable IR raw decoder for the RC6 protocol"
64 Enable this option if you have an infrared remote control which
65 uses the RC6 protocol, and you need software decoding support.
68 tristate "Enable IR raw decoder for the JVC protocol"
74 Enable this option if you have an infrared remote control which
75 uses the JVC protocol, and you need software decoding support.
77 config IR_SONY_DECODER
78 tristate "Enable IR raw decoder for the Sony protocol"
84 Enable this option if you have an infrared remote control which
85 uses the Sony protocol, and you need software decoding support.
87 config IR_SANYO_DECODER
88 tristate "Enable IR raw decoder for the Sanyo protocol"
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.
97 config IR_SHARP_DECODER
98 tristate "Enable IR raw decoder for the Sharp protocol"
103 Enable this option if you have an infrared remote control which
104 uses the Sharp protocol, and you need software decoding support.
106 config IR_MCE_KBD_DECODER
107 tristate "Enable IR raw decoder for the MCE keyboard/mouse protocol"
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.
117 config IR_XMP_DECODER
118 tristate "Enable IR raw decoder for the XMP protocol"
124 Enable this option if you have IR with XMP protocol, and
125 if the IR is decoded in software
128 menuconfig RC_DEVICES
129 bool "Remote Controller devices"
135 tristate "ATI / X10 based USB RF remote controls"
136 depends on USB_ARCH_HAS_HCD
140 Say Y here if you want to use an X10 based USB remote control.
141 These are RF remotes with USB receivers.
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.
147 This driver provides mouse pointer, left and right mouse buttons,
148 and maps all the other remote buttons to keypress events.
150 To compile this driver as a module, choose M here: the module will be
154 tristate "ENE eHome Receiver/Transceiver (pnp id: ENE0100/ENE02xxx)"
158 Say Y here to enable support for integrated infrared receiver
159 /transceiver made by ENE.
161 You can see if you have it by looking at lspnp output.
162 Output should include ENE0100 ENE0200 or something similar.
164 To compile this driver as a module, choose M here: the
165 module will be called ene_ir.
168 tristate "SoundGraph iMON Receiver and Display"
169 depends on USB_ARCH_HAS_HCD
173 Say Y here if you want to use a SoundGraph iMON (aka Antec Veris)
174 IR Receiver and/or LCD/VFD/VGA display.
176 To compile this driver as a module, choose M here: the
177 module will be called imon.
180 tristate "Windows Media Center Ed. eHome Infrared Transceiver"
181 depends on USB_ARCH_HAS_HCD
185 Say Y here if you want to use a Windows Media Center Edition
186 eHome Infrared Transceiver.
188 To compile this driver as a module, choose M here: the
189 module will be called mceusb.
192 tristate "ITE Tech Inc. IT8712/IT8512 Consumer Infrared Transceiver"
196 Say Y here to enable support for integrated infrared receivers
197 /transceivers made by ITE Tech Inc. These are found in
198 several ASUS devices, like the ASUS Digimatrix or the ASUS
201 To compile this driver as a module, choose M here: the
202 module will be called ite-cir.
205 tristate "Fintek Consumer Infrared Transceiver"
209 Say Y here to enable support for integrated infrared receiver
210 /transciever made by Fintek. This chip is found on assorted
211 Jetway motherboards (and of course, possibly others).
213 To compile this driver as a module, choose M here: the
214 module will be called fintek-cir.
217 tristate "Nuvoton w836x7hg Consumer Infrared Transceiver"
221 Say Y here to enable support for integrated infrared receiver
222 /transciever made by Nuvoton (formerly Winbond). This chip is
223 found in the ASRock ION 330HT, as well as assorted Intel
224 DP55-series motherboards (and of course, possibly others).
226 To compile this driver as a module, choose M here: the
227 module will be called nuvoton-cir.
230 tristate "RedRat3 IR Transceiver"
231 depends on USB_ARCH_HAS_HCD
237 Say Y here if you want to use a RedRat3 Infrared Transceiver.
239 To compile this driver as a module, choose M here: the
240 module will be called redrat3.
243 tristate "Streamzap PC Remote IR Receiver"
244 depends on USB_ARCH_HAS_HCD
248 Say Y here if you want to use a Streamzap PC Remote
251 To compile this driver as a module, choose M here: the
252 module will be called streamzap.
254 config IR_WINBOND_CIR
255 tristate "Winbond IR remote control"
256 depends on X86 && PNP
262 Say Y here if you want to use the IR remote functionality found
263 in some Winbond SuperI/O chips. Currently only the WPCD376I
264 chip is supported (included in some Intel Media series
267 To compile this driver as a module, choose M here: the module will
268 be called winbond_cir.
271 tristate "IguanaWorks USB IR Transceiver"
272 depends on USB_ARCH_HAS_HCD
276 Say Y here if you want to use the IguanaWorks USB IR Transceiver.
277 Both infrared receive and send are supported. If you want to
278 change the ID or the pin config, use the user space driver from
281 Only firmware 0x0205 and later is supported.
283 To compile this driver as a module, choose M here: the module will
287 tristate "TechnoTrend USB IR Receiver"
288 depends on USB_ARCH_HAS_HCD
294 Say Y here if you want to use the TechnoTrend USB IR Receiver. The
295 driver can control the led.
297 To compile this driver as a module, choose M here: the module will
301 tristate "Nokia N900 IR transmitter diode"
302 depends on OMAP_DM_TIMER && ARCH_OMAP2PLUS && LIRC && !ARCH_MULTIPLATFORM
304 Say Y or M here if you want to enable support for the IR
305 transmitter diode built in the Nokia N900 (RX51) device.
307 The driver uses omap DM timers for generating the carrier
310 source "drivers/media/rc/img-ir/Kconfig"
313 tristate "Remote Control Loopback Driver"
316 Say Y here if you want support for the remote control loopback
317 driver which allows TX data to be sent back as RX data.
318 This is mostly useful for debugging purposes.
320 If you're not sure, select N here.
322 To compile this driver as a module, choose M here: the module will
323 be called rc_loopback.
326 tristate "GPIO IR remote control"
329 Say Y if you want to use GPIO based IR Receiver.
331 To compile this driver as a module, choose M here: the module will
332 be called gpio-ir-recv.
335 tristate "ST remote control receiver"
336 depends on ARCH_STI && RC_CORE
338 Say Y here if you want support for ST remote control driver
339 which allows both IR and UHF RX.
340 The driver passes raw pulse and space information to the LIRC decoder.
342 If you're not sure, select N here.
345 tristate "SUNXI IR remote control"
347 depends on ARCH_SUNXI
349 Say Y if you want to use sunXi internal IR Controller
351 To compile this driver as a module, choose M here: the module will