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_RC5_SZ_DECODER
88 tristate "Enable IR raw decoder for the RC-5 (streamzap) protocol"
94 Enable this option if you have IR with RC-5 (streamzap) protocol,
95 and if the IR is decoded in software. (The Streamzap PC Remote
96 uses an IR protocol that is almost standard RC-5, but not quite,
97 as it uses an additional bit).
99 config IR_SANYO_DECODER
100 tristate "Enable IR raw decoder for the Sanyo protocol"
105 Enable this option if you have an infrared remote control which
106 uses the Sanyo protocol (Sanyo, Aiwa, Chinon remotes),
107 and you need software decoding support.
109 config IR_MCE_KBD_DECODER
110 tristate "Enable IR raw decoder for the MCE keyboard/mouse protocol"
116 Enable this option if you have a Microsoft Remote Keyboard for
117 Windows Media Center Edition, which you would like to use with
118 a raw IR receiver in your system.
121 menuconfig RC_DEVICES
122 bool "Remote Controller devices"
128 tristate "ATI / X10 based USB RF remote controls"
129 depends on USB_ARCH_HAS_HCD
133 Say Y here if you want to use an X10 based USB remote control.
134 These are RF remotes with USB receivers.
136 Such devices include the ATI remote that comes with many of ATI's
137 All-In-Wonder video cards, the X10 "Lola" remote, NVIDIA RF remote,
138 Medion RF remote, and SnapStream FireFly remote.
140 This driver provides mouse pointer, left and right mouse buttons,
141 and maps all the other remote buttons to keypress events.
143 To compile this driver as a module, choose M here: the module will be
147 tristate "ENE eHome Receiver/Transceiver (pnp id: ENE0100/ENE02xxx)"
151 Say Y here to enable support for integrated infrared receiver
152 /transceiver made by ENE.
154 You can see if you have it by looking at lspnp output.
155 Output should include ENE0100 ENE0200 or something similar.
157 To compile this driver as a module, choose M here: the
158 module will be called ene_ir.
161 tristate "SoundGraph iMON Receiver and Display"
162 depends on USB_ARCH_HAS_HCD
166 Say Y here if you want to use a SoundGraph iMON (aka Antec Veris)
167 IR Receiver and/or LCD/VFD/VGA display.
169 To compile this driver as a module, choose M here: the
170 module will be called imon.
173 tristate "Windows Media Center Ed. eHome Infrared Transceiver"
174 depends on USB_ARCH_HAS_HCD
178 Say Y here if you want to use a Windows Media Center Edition
179 eHome Infrared Transceiver.
181 To compile this driver as a module, choose M here: the
182 module will be called mceusb.
185 tristate "ITE Tech Inc. IT8712/IT8512 Consumer Infrared Transceiver"
189 Say Y here to enable support for integrated infrared receivers
190 /transceivers made by ITE Tech Inc. These are found in
191 several ASUS devices, like the ASUS Digimatrix or the ASUS
194 To compile this driver as a module, choose M here: the
195 module will be called ite-cir.
198 tristate "Fintek Consumer Infrared Transceiver"
202 Say Y here to enable support for integrated infrared receiver
203 /transciever made by Fintek. This chip is found on assorted
204 Jetway motherboards (and of course, possibly others).
206 To compile this driver as a module, choose M here: the
207 module will be called fintek-cir.
210 tristate "Nuvoton w836x7hg Consumer Infrared Transceiver"
214 Say Y here to enable support for integrated infrared receiver
215 /transciever made by Nuvoton (formerly Winbond). This chip is
216 found in the ASRock ION 330HT, as well as assorted Intel
217 DP55-series motherboards (and of course, possibly others).
219 To compile this driver as a module, choose M here: the
220 module will be called nuvoton-cir.
223 tristate "RedRat3 IR Transceiver"
224 depends on USB_ARCH_HAS_HCD
230 Say Y here if you want to use a RedRat3 Infrared Transceiver.
232 To compile this driver as a module, choose M here: the
233 module will be called redrat3.
236 tristate "Streamzap PC Remote IR Receiver"
237 depends on USB_ARCH_HAS_HCD
241 Say Y here if you want to use a Streamzap PC Remote
244 To compile this driver as a module, choose M here: the
245 module will be called streamzap.
247 config IR_WINBOND_CIR
248 tristate "Winbond IR remote control"
249 depends on X86 && PNP
255 Say Y here if you want to use the IR remote functionality found
256 in some Winbond SuperI/O chips. Currently only the WPCD376I
257 chip is supported (included in some Intel Media series
260 To compile this driver as a module, choose M here: the module will
261 be called winbond_cir.
264 tristate "IguanaWorks USB IR Transceiver"
265 depends on USB_ARCH_HAS_HCD
269 Say Y here if you want to use the IguanaWorks USB IR Transceiver.
270 Both infrared receive and send are supported. If you want to
271 change the ID or the pin config, use the user space driver from
274 Only firmware 0x0205 and later is supported.
276 To compile this driver as a module, choose M here: the module will
280 tristate "TechnoTrend USB IR Receiver"
281 depends on USB_ARCH_HAS_HCD
287 Say Y here if you want to use the TechnoTrend USB IR Receiver. The
288 driver can control the led.
290 To compile this driver as a module, choose M here: the module will
294 tristate "Nokia N900 IR transmitter diode"
295 depends on OMAP_DM_TIMER && ARCH_OMAP2PLUS && LIRC && !ARCH_MULTIPLATFORM
297 Say Y or M here if you want to enable support for the IR
298 transmitter diode built in the Nokia N900 (RX51) device.
300 The driver uses omap DM timers for generating the carrier
304 tristate "Remote Control Loopback Driver"
307 Say Y here if you want support for the remote control loopback
308 driver which allows TX data to be sent back as RX data.
309 This is mostly useful for debugging purposes.
311 If you're not sure, select N here.
313 To compile this driver as a module, choose M here: the module will
314 be called rc_loopback.
317 tristate "GPIO IR remote control"
320 Say Y if you want to use GPIO based IR Receiver.
322 To compile this driver as a module, choose M here: the module will
323 be called gpio-ir-recv.
326 tristate "ST remote control receiver"
327 depends on ARCH_STI && RC_CORE
329 Say Y here if you want support for ST remote control driver
330 which allows both IR and UHF RX.
331 The driver passes raw pulse and space information to the LIRC decoder.
333 If you're not sure, select N here.