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 (Sharp, Denon), and you need software
107 config IR_MCE_KBD_DECODER
108 tristate "Enable IR raw decoder for the MCE keyboard/mouse protocol"
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.
118 config IR_XMP_DECODER
119 tristate "Enable IR raw decoder for the XMP protocol"
125 Enable this option if you have IR with XMP protocol, and
126 if the IR is decoded in software
129 menuconfig RC_DEVICES
130 bool "Remote Controller devices"
136 tristate "ATI / X10 based USB RF remote controls"
137 depends on USB_ARCH_HAS_HCD
141 Say Y here if you want to use an X10 based USB remote control.
142 These are RF remotes with USB receivers.
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.
148 This driver provides mouse pointer, left and right mouse buttons,
149 and maps all the other remote buttons to keypress events.
151 To compile this driver as a module, choose M here: the module will be
155 tristate "ENE eHome Receiver/Transceiver (pnp id: ENE0100/ENE02xxx)"
159 Say Y here to enable support for integrated infrared receiver
160 /transceiver made by ENE.
162 You can see if you have it by looking at lspnp output.
163 Output should include ENE0100 ENE0200 or something similar.
165 To compile this driver as a module, choose M here: the
166 module will be called ene_ir.
169 tristate "Hisilicon hix5hd2 IR remote control"
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
176 If you're not sure, select N here
179 tristate "SoundGraph iMON Receiver and Display"
180 depends on USB_ARCH_HAS_HCD
184 Say Y here if you want to use a SoundGraph iMON (aka Antec Veris)
185 IR Receiver and/or LCD/VFD/VGA display.
187 To compile this driver as a module, choose M here: the
188 module will be called imon.
191 tristate "Windows Media Center Ed. eHome Infrared Transceiver"
192 depends on USB_ARCH_HAS_HCD
196 Say Y here if you want to use a Windows Media Center Edition
197 eHome Infrared Transceiver.
199 To compile this driver as a module, choose M here: the
200 module will be called mceusb.
203 tristate "ITE Tech Inc. IT8712/IT8512 Consumer Infrared Transceiver"
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
212 To compile this driver as a module, choose M here: the
213 module will be called ite-cir.
216 tristate "Fintek Consumer Infrared Transceiver"
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).
224 To compile this driver as a module, choose M here: the
225 module will be called fintek-cir.
228 tristate "Amlogic Meson IR remote receiver"
230 depends on ARCH_MESON || COMPILE_TEST
232 Say Y if you want to use the IR remote receiver available
233 on Amlogic Meson SoCs.
235 To compile this driver as a module, choose M here: the
236 module will be called meson-ir.
239 tristate "Mediatek IR remote receiver"
241 depends on ARCH_MEDIATEK || COMPILE_TEST
243 Say Y if you want to use the IR remote receiver available
246 To compile this driver as a module, choose M here: the
247 module will be called mtk-cir.
250 tristate "Nuvoton w836x7hg Consumer Infrared Transceiver"
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).
259 To compile this driver as a module, choose M here: the
260 module will be called nuvoton-cir.
263 tristate "RedRat3 IR Transceiver"
264 depends on USB_ARCH_HAS_HCD
270 Say Y here if you want to use a RedRat3 Infrared Transceiver.
272 To compile this driver as a module, choose M here: the
273 module will be called redrat3.
276 tristate "SPI connected IR LED"
277 depends on SPI && LIRC
279 Say Y if you want to use an IR LED connected through SPI bus.
281 To compile this driver as a module, choose M here: the module will be
285 tristate "Streamzap PC Remote IR Receiver"
286 depends on USB_ARCH_HAS_HCD
290 Say Y here if you want to use a Streamzap PC Remote
293 To compile this driver as a module, choose M here: the
294 module will be called streamzap.
296 config IR_WINBOND_CIR
297 tristate "Winbond IR remote control"
298 depends on X86 && PNP
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
309 To compile this driver as a module, choose M here: the module will
310 be called winbond_cir.
312 config IR_IGORPLUGUSB
313 tristate "IgorPlug-USB IR Receiver"
314 depends on USB_ARCH_HAS_HCD
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.
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.
324 To compile this driver as a module, choose M here: the module will
325 be called igorplugusb.
328 tristate "IguanaWorks USB IR Transceiver"
329 depends on USB_ARCH_HAS_HCD
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
338 Only firmware 0x0205 and later is supported.
340 To compile this driver as a module, choose M here: the module will
344 tristate "TechnoTrend USB IR Receiver"
345 depends on USB_ARCH_HAS_HCD
351 Say Y here if you want to use the TechnoTrend USB IR Receiver. The
352 driver can control the led.
354 To compile this driver as a module, choose M here: the module will
358 tristate "Nokia N900 IR transmitter diode"
359 depends on (OMAP_DM_TIMER && PWM_OMAP_DMTIMER && ARCH_OMAP2PLUS || COMPILE_TEST) && RC_CORE
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.
364 The driver uses omap DM timers for generating the carrier
367 source "drivers/media/rc/img-ir/Kconfig"
370 tristate "Remote Control Loopback Driver"
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.
377 If you're not sure, select N here.
379 To compile this driver as a module, choose M here: the module will
380 be called rc_loopback.
383 tristate "GPIO IR remote control"
386 Say Y if you want to use GPIO based IR Receiver.
388 To compile this driver as a module, choose M here: the module will
389 be called gpio-ir-recv.
392 tristate "ST remote control receiver"
394 depends on ARCH_STI || COMPILE_TEST
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.
400 If you're not sure, select N here.
403 tristate "SUNXI IR remote control"
405 depends on ARCH_SUNXI || COMPILE_TEST
407 Say Y if you want to use sunXi internal IR Controller
409 To compile this driver as a module, choose M here: the module will
413 tristate "Homebrew Serial Port Receiver"
416 Say Y if you want to use Homebrew Serial Port Receivers and
419 To compile this driver as a module, choose M here: the module will
422 config IR_SERIAL_TRANSMITTER
423 bool "Serial Port Transmitter"
427 Serial Port Transmitter support
430 tristate "Built-in SIR IrDA port"
433 Say Y if you want to use a IrDA SIR port Transceivers.
435 To compile this driver as a module, choose M here: the module will