3 tristate "Remote Controller support"
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.
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.
14 Say Y when you have a TV or an IR device.
17 source "drivers/media/rc/keymaps/Kconfig"
20 bool "LIRC user interface"
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.
28 menuconfig RC_DECODERS
29 bool "Remote controller decoders"
34 tristate "Enable IR raw decoder for the NEC protocol"
39 Enable this option if you have IR with NEC protocol, and
40 if the IR is decoded in software
43 tristate "Enable IR raw decoder for the RC-5 protocol"
48 Enable this option if you have IR with RC-5 protocol, and
49 if the IR is decoded in software
52 tristate "Enable IR raw decoder for the RC6 protocol"
57 Enable this option if you have an infrared remote control which
58 uses the RC6 protocol, and you need software decoding support.
61 tristate "Enable IR raw decoder for the JVC protocol"
66 Enable this option if you have an infrared remote control which
67 uses the JVC protocol, and you need software decoding support.
69 config IR_SONY_DECODER
70 tristate "Enable IR raw decoder for the Sony protocol"
75 Enable this option if you have an infrared remote control which
76 uses the Sony protocol, and you need software decoding support.
78 config IR_SANYO_DECODER
79 tristate "Enable IR raw decoder for the Sanyo protocol"
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.
87 config IR_SHARP_DECODER
88 tristate "Enable IR raw decoder for the Sharp protocol"
92 Enable this option if you have an infrared remote control which
93 uses the Sharp protocol (Sharp, Denon), and you need software
96 config IR_MCE_KBD_DECODER
97 tristate "Enable IR raw decoder for the MCE keyboard/mouse protocol"
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.
106 config IR_XMP_DECODER
107 tristate "Enable IR raw decoder for the XMP protocol"
112 Enable this option if you have IR with XMP protocol, and
113 if the IR is decoded in software
115 config IR_IMON_DECODER
116 tristate "Enable IR raw decoder for the iMON protocol"
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.
125 menuconfig RC_DEVICES
126 bool "Remote Controller devices"
132 tristate "ATI / X10 based USB RF remote controls"
133 depends on USB_ARCH_HAS_HCD
137 Say Y here if you want to use an X10 based USB remote control.
138 These are RF remotes with USB receivers.
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.
144 This driver provides mouse pointer, left and right mouse buttons,
145 and maps all the other remote buttons to keypress events.
147 To compile this driver as a module, choose M here: the module will be
151 tristate "ENE eHome Receiver/Transceiver (pnp id: ENE0100/ENE02xxx)"
155 Say Y here to enable support for integrated infrared receiver
156 /transceiver made by ENE.
158 You can see if you have it by looking at lspnp output.
159 Output should include ENE0100 ENE0200 or something similar.
161 To compile this driver as a module, choose M here: the
162 module will be called ene_ir.
165 tristate "Hisilicon hix5hd2 IR remote control"
167 depends on OF || COMPILE_TEST
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
173 If you're not sure, select N here
176 tristate "SoundGraph iMON Receiver and Display"
177 depends on USB_ARCH_HAS_HCD
181 Say Y here if you want to use a SoundGraph iMON (aka Antec Veris)
182 IR Receiver and/or LCD/VFD/VGA display.
184 To compile this driver as a module, choose M here: the
185 module will be called imon.
188 tristate "SoundGraph iMON Receiver (early raw IR models)"
189 depends on USB_ARCH_HAS_HCD
193 Say Y here if you want to use a SoundGraph iMON IR Receiver,
196 To compile this driver as a module, choose M here: the
197 module will be called imon_raw.
200 tristate "Windows Media Center Ed. eHome Infrared Transceiver"
201 depends on USB_ARCH_HAS_HCD
205 Say Y here if you want to use a Windows Media Center Edition
206 eHome Infrared Transceiver.
208 To compile this driver as a module, choose M here: the
209 module will be called mceusb.
212 tristate "ITE Tech Inc. IT8712/IT8512 Consumer Infrared Transceiver"
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
221 To compile this driver as a module, choose M here: the
222 module will be called ite-cir.
225 tristate "Fintek Consumer Infrared Transceiver"
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).
233 To compile this driver as a module, choose M here: the
234 module will be called fintek-cir.
237 tristate "Amlogic Meson IR remote receiver"
239 depends on ARCH_MESON || COMPILE_TEST
241 Say Y if you want to use the IR remote receiver available
242 on Amlogic Meson SoCs.
244 To compile this driver as a module, choose M here: the
245 module will be called meson-ir.
248 tristate "Mediatek IR remote receiver"
250 depends on ARCH_MEDIATEK || COMPILE_TEST
252 Say Y if you want to use the IR remote receiver available
255 To compile this driver as a module, choose M here: the
256 module will be called mtk-cir.
259 tristate "Nuvoton w836x7hg Consumer Infrared Transceiver"
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).
268 To compile this driver as a module, choose M here: the
269 module will be called nuvoton-cir.
272 tristate "RedRat3 IR Transceiver"
273 depends on USB_ARCH_HAS_HCD
279 Say Y here if you want to use a RedRat3 Infrared Transceiver.
281 To compile this driver as a module, choose M here: the
282 module will be called redrat3.
285 tristate "SPI connected IR LED"
286 depends on SPI && LIRC
287 depends on OF || COMPILE_TEST
289 Say Y if you want to use an IR LED connected through SPI bus.
291 To compile this driver as a module, choose M here: the module will be
295 tristate "Streamzap PC Remote IR Receiver"
296 depends on USB_ARCH_HAS_HCD
300 Say Y here if you want to use a Streamzap PC Remote
303 To compile this driver as a module, choose M here: the
304 module will be called streamzap.
306 config IR_WINBOND_CIR
307 tristate "Winbond IR remote control"
308 depends on X86 && PNP
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
319 To compile this driver as a module, choose M here: the module will
320 be called winbond_cir.
322 config IR_IGORPLUGUSB
323 tristate "IgorPlug-USB IR Receiver"
324 depends on USB_ARCH_HAS_HCD
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.
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.
334 To compile this driver as a module, choose M here: the module will
335 be called igorplugusb.
338 tristate "IguanaWorks USB IR Transceiver"
339 depends on USB_ARCH_HAS_HCD
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
348 Only firmware 0x0205 and later is supported.
350 To compile this driver as a module, choose M here: the module will
354 tristate "TechnoTrend USB IR Receiver"
355 depends on USB_ARCH_HAS_HCD
361 Say Y here if you want to use the TechnoTrend USB IR Receiver. The
362 driver can control the led.
364 To compile this driver as a module, choose M here: the module will
368 tristate "Nokia N900 IR transmitter diode"
369 depends on (OMAP_DM_TIMER && PWM_OMAP_DMTIMER && ARCH_OMAP2PLUS || COMPILE_TEST) && RC_CORE
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.
374 The driver uses omap DM timers for generating the carrier
377 source "drivers/media/rc/img-ir/Kconfig"
380 tristate "Remote Control Loopback Driver"
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.
387 If you're not sure, select N here.
389 To compile this driver as a module, choose M here: the module will
390 be called rc_loopback.
393 tristate "GPIO IR remote control"
395 depends on (OF && GPIOLIB) || COMPILE_TEST
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"
406 depends on (OF && GPIOLIB) || COMPILE_TEST
408 Say Y if you want to a GPIO based IR transmitter. This is a
411 To compile this driver as a module, choose M here: the module will
412 be called gpio-ir-tx.
415 tristate "PWM IR transmitter"
419 depends on OF || COMPILE_TEST
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.
424 To compile this driver as a module, choose M here: the module will
428 tristate "ST remote control receiver"
430 depends on ARCH_STI || COMPILE_TEST
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.
436 If you're not sure, select N here.
439 tristate "SUNXI IR remote control"
441 depends on ARCH_SUNXI || COMPILE_TEST
443 Say Y if you want to use sunXi internal IR Controller
445 To compile this driver as a module, choose M here: the module will
449 tristate "Homebrew Serial Port Receiver"
452 Say Y if you want to use Homebrew Serial Port Receivers and
455 To compile this driver as a module, choose M here: the module will
458 config IR_SERIAL_TRANSMITTER
459 bool "Serial Port Transmitter"
462 Serial Port Transmitter support
465 tristate "Built-in SIR IrDA port"
468 Say Y if you want to use a IrDA SIR port Transceivers.
470 To compile this driver as a module, choose M here: the module will
474 tristate "Sigma Designs SMP86xx IR decoder"
476 depends on ARCH_TANGO || COMPILE_TEST
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.
484 tristate "ZTE ZX IR remote control"
486 depends on ARCH_ZX || COMPILE_TEST
488 Say Y if you want to use the IR remote control available
489 on ZTE ZX family SoCs.
491 To compile this driver as a module, choose M here: the
492 module will be called zx-irdec.