3 tristate "Remote Controller support"
7 Enable support for Remote Controllers on Linux. This is
8 needed in order to support several video capture adapters,
9 standalone IR receivers/transmitters, and RF receivers.
11 Enable this option if you have a video capture board even
12 if you don't need IR, as otherwise, you may not be able to
13 compile the driver for your adapter.
15 Say Y when you have a TV or an IR device.
18 source "drivers/media/rc/keymaps/Kconfig"
20 menuconfig RC_DECODERS
21 bool "Remote controller decoders"
27 tristate "LIRC interface driver"
31 Enable this option to build the Linux Infrared Remote
32 Control (LIRC) core device interface driver. The LIRC
33 interface passes raw IR to and from userspace, where the
34 LIRC daemon handles protocol decoding for IR reception and
35 encoding for IR transmitting (aka "blasting").
38 tristate "Enable IR to LIRC bridge"
44 Enable this option to pass raw IR to and from userspace via
49 tristate "Enable IR raw decoder for the NEC protocol"
55 Enable this option if you have IR with NEC protocol, and
56 if the IR is decoded in software
59 tristate "Enable IR raw decoder for the RC-5 protocol"
65 Enable this option if you have IR with RC-5 protocol, and
66 if the IR is decoded in software
69 tristate "Enable IR raw decoder for the RC6 protocol"
75 Enable this option if you have an infrared remote control which
76 uses the RC6 protocol, and you need software decoding support.
79 tristate "Enable IR raw decoder for the JVC protocol"
85 Enable this option if you have an infrared remote control which
86 uses the JVC protocol, and you need software decoding support.
88 config IR_SONY_DECODER
89 tristate "Enable IR raw decoder for the Sony protocol"
95 Enable this option if you have an infrared remote control which
96 uses the Sony protocol, and you need software decoding support.
98 config IR_SANYO_DECODER
99 tristate "Enable IR raw decoder for the Sanyo protocol"
104 Enable this option if you have an infrared remote control which
105 uses the Sanyo protocol (Sanyo, Aiwa, Chinon remotes),
106 and you need software decoding support.
108 config IR_SHARP_DECODER
109 tristate "Enable IR raw decoder for the Sharp protocol"
114 Enable this option if you have an infrared remote control which
115 uses the Sharp protocol (Sharp, Denon), and you need software
118 config IR_MCE_KBD_DECODER
119 tristate "Enable IR raw decoder for the MCE keyboard/mouse protocol"
125 Enable this option if you have a Microsoft Remote Keyboard for
126 Windows Media Center Edition, which you would like to use with
127 a raw IR receiver in your system.
129 config IR_XMP_DECODER
130 tristate "Enable IR raw decoder for the XMP protocol"
136 Enable this option if you have IR with XMP protocol, and
137 if the IR is decoded in software
140 menuconfig RC_DEVICES
141 bool "Remote Controller devices"
147 tristate "ATI / X10 based USB RF remote controls"
148 depends on USB_ARCH_HAS_HCD
152 Say Y here if you want to use an X10 based USB remote control.
153 These are RF remotes with USB receivers.
155 Such devices include the ATI remote that comes with many of ATI's
156 All-In-Wonder video cards, the X10 "Lola" remote, NVIDIA RF remote,
157 Medion RF remote, and SnapStream FireFly remote.
159 This driver provides mouse pointer, left and right mouse buttons,
160 and maps all the other remote buttons to keypress events.
162 To compile this driver as a module, choose M here: the module will be
166 tristate "ENE eHome Receiver/Transceiver (pnp id: ENE0100/ENE02xxx)"
170 Say Y here to enable support for integrated infrared receiver
171 /transceiver made by ENE.
173 You can see if you have it by looking at lspnp output.
174 Output should include ENE0100 ENE0200 or something similar.
176 To compile this driver as a module, choose M here: the
177 module will be called ene_ir.
180 tristate "Hisilicon hix5hd2 IR remote control"
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
187 If you're not sure, select N here
190 tristate "SoundGraph iMON Receiver and Display"
191 depends on USB_ARCH_HAS_HCD
195 Say Y here if you want to use a SoundGraph iMON (aka Antec Veris)
196 IR Receiver and/or LCD/VFD/VGA display.
198 To compile this driver as a module, choose M here: the
199 module will be called imon.
202 tristate "Windows Media Center Ed. eHome Infrared Transceiver"
203 depends on USB_ARCH_HAS_HCD
207 Say Y here if you want to use a Windows Media Center Edition
208 eHome Infrared Transceiver.
210 To compile this driver as a module, choose M here: the
211 module will be called mceusb.
214 tristate "ITE Tech Inc. IT8712/IT8512 Consumer Infrared Transceiver"
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
223 To compile this driver as a module, choose M here: the
224 module will be called ite-cir.
227 tristate "Fintek Consumer Infrared Transceiver"
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).
235 To compile this driver as a module, choose M here: the
236 module will be called fintek-cir.
239 tristate "Amlogic Meson IR remote receiver"
241 depends on ARCH_MESON || COMPILE_TEST
243 Say Y if you want to use the IR remote receiver available
244 on Amlogic Meson SoCs.
246 To compile this driver as a module, choose M here: the
247 module will be called meson-ir.
250 tristate "Mediatek IR remote receiver"
252 depends on ARCH_MEDIATEK || COMPILE_TEST
254 Say Y if you want to use the IR remote receiver available
257 To compile this driver as a module, choose M here: the
258 module will be called mtk-cir.
261 tristate "Nuvoton w836x7hg Consumer Infrared Transceiver"
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).
270 To compile this driver as a module, choose M here: the
271 module will be called nuvoton-cir.
274 tristate "RedRat3 IR Transceiver"
275 depends on USB_ARCH_HAS_HCD
281 Say Y here if you want to use a RedRat3 Infrared Transceiver.
283 To compile this driver as a module, choose M here: the
284 module will be called redrat3.
287 tristate "SPI connected IR LED"
288 depends on SPI && LIRC
290 Say Y if you want to use an IR LED connected through SPI bus.
292 To compile this driver as a module, choose M here: the module will be
296 tristate "Streamzap PC Remote IR Receiver"
297 depends on USB_ARCH_HAS_HCD
301 Say Y here if you want to use a Streamzap PC Remote
304 To compile this driver as a module, choose M here: the
305 module will be called streamzap.
307 config IR_WINBOND_CIR
308 tristate "Winbond IR remote control"
309 depends on X86 && PNP
315 Say Y here if you want to use the IR remote functionality found
316 in some Winbond SuperI/O chips. Currently only the WPCD376I
317 chip is supported (included in some Intel Media series
320 To compile this driver as a module, choose M here: the module will
321 be called winbond_cir.
323 config IR_IGORPLUGUSB
324 tristate "IgorPlug-USB IR Receiver"
325 depends on USB_ARCH_HAS_HCD
329 Say Y here if you want to use the IgorPlug-USB IR Receiver by
330 Igor Cesko. This device is included on the Fit-PC2.
332 Note that this device can only record bursts of 36 IR pulses and
333 spaces, which is not enough for the NEC, Sanyo and RC-6 protocol.
335 To compile this driver as a module, choose M here: the module will
336 be called igorplugusb.
339 tristate "IguanaWorks USB IR Transceiver"
340 depends on USB_ARCH_HAS_HCD
344 Say Y here if you want to use the IguanaWorks USB IR Transceiver.
345 Both infrared receive and send are supported. If you want to
346 change the ID or the pin config, use the user space driver from
349 Only firmware 0x0205 and later is supported.
351 To compile this driver as a module, choose M here: the module will
355 tristate "TechnoTrend USB IR Receiver"
356 depends on USB_ARCH_HAS_HCD
362 Say Y here if you want to use the TechnoTrend USB IR Receiver. The
363 driver can control the led.
365 To compile this driver as a module, choose M here: the module will
369 tristate "Nokia N900 IR transmitter diode"
370 depends on (OMAP_DM_TIMER && PWM_OMAP_DMTIMER && ARCH_OMAP2PLUS || COMPILE_TEST) && RC_CORE
372 Say Y or M here if you want to enable support for the IR
373 transmitter diode built in the Nokia N900 (RX51) device.
375 The driver uses omap DM timers for generating the carrier
378 source "drivers/media/rc/img-ir/Kconfig"
381 tristate "Remote Control Loopback Driver"
384 Say Y here if you want support for the remote control loopback
385 driver which allows TX data to be sent back as RX data.
386 This is mostly useful for debugging purposes.
388 If you're not sure, select N here.
390 To compile this driver as a module, choose M here: the module will
391 be called rc_loopback.
394 tristate "GPIO IR remote control"
397 Say Y if you want to use GPIO based IR Receiver.
399 To compile this driver as a module, choose M here: the module will
400 be called gpio-ir-recv.
403 tristate "GPIO IR Bit Banging Transmitter"
407 Say Y if you want to a GPIO based IR transmitter. This is a
410 To compile this driver as a module, choose M here: the module will
411 be called gpio-ir-tx.
414 tristate "PWM IR transmitter"
419 Say Y if you want to use a PWM based IR transmitter. This is
420 more power efficient than the bit banging gpio driver.
422 To compile this driver as a module, choose M here: the module will
426 tristate "ST remote control receiver"
428 depends on ARCH_STI || COMPILE_TEST
430 Say Y here if you want support for ST remote control driver
431 which allows both IR and UHF RX.
432 The driver passes raw pulse and space information to the LIRC decoder.
434 If you're not sure, select N here.
437 tristate "SUNXI IR remote control"
439 depends on ARCH_SUNXI || COMPILE_TEST
441 Say Y if you want to use sunXi internal IR Controller
443 To compile this driver as a module, choose M here: the module will
447 tristate "Homebrew Serial Port Receiver"
450 Say Y if you want to use Homebrew Serial Port Receivers and
453 To compile this driver as a module, choose M here: the module will
456 config IR_SERIAL_TRANSMITTER
457 bool "Serial Port Transmitter"
461 Serial Port Transmitter support
464 tristate "Built-in SIR IrDA port"
467 Say Y if you want to use a IrDA SIR port Transceivers.
469 To compile this driver as a module, choose M here: the module will
473 tristate "ZTE ZX IR remote control"
475 depends on ARCH_ZX || COMPILE_TEST
477 Say Y if you want to use the IR remote control available
478 on ZTE ZX family SoCs.
480 To compile this driver as a module, choose M here: the
481 module will be called zx-irdec.