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_SHARP_DECODER
110 tristate "Enable IR raw decoder for the Sharp protocol"
115 Enable this option if you have an infrared remote control which
116 uses the Sharp protocol, and you need software decoding support.
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.
130 menuconfig RC_DEVICES
131 bool "Remote Controller devices"
137 tristate "ATI / X10 based USB RF remote controls"
138 depends on USB_ARCH_HAS_HCD
142 Say Y here if you want to use an X10 based USB remote control.
143 These are RF remotes with USB receivers.
145 Such devices include the ATI remote that comes with many of ATI's
146 All-In-Wonder video cards, the X10 "Lola" remote, NVIDIA RF remote,
147 Medion RF remote, and SnapStream FireFly remote.
149 This driver provides mouse pointer, left and right mouse buttons,
150 and maps all the other remote buttons to keypress events.
152 To compile this driver as a module, choose M here: the module will be
156 tristate "ENE eHome Receiver/Transceiver (pnp id: ENE0100/ENE02xxx)"
160 Say Y here to enable support for integrated infrared receiver
161 /transceiver made by ENE.
163 You can see if you have it by looking at lspnp output.
164 Output should include ENE0100 ENE0200 or something similar.
166 To compile this driver as a module, choose M here: the
167 module will be called ene_ir.
170 tristate "SoundGraph iMON Receiver and Display"
171 depends on USB_ARCH_HAS_HCD
175 Say Y here if you want to use a SoundGraph iMON (aka Antec Veris)
176 IR Receiver and/or LCD/VFD/VGA display.
178 To compile this driver as a module, choose M here: the
179 module will be called imon.
182 tristate "Windows Media Center Ed. eHome Infrared Transceiver"
183 depends on USB_ARCH_HAS_HCD
187 Say Y here if you want to use a Windows Media Center Edition
188 eHome Infrared Transceiver.
190 To compile this driver as a module, choose M here: the
191 module will be called mceusb.
194 tristate "ITE Tech Inc. IT8712/IT8512 Consumer Infrared Transceiver"
198 Say Y here to enable support for integrated infrared receivers
199 /transceivers made by ITE Tech Inc. These are found in
200 several ASUS devices, like the ASUS Digimatrix or the ASUS
203 To compile this driver as a module, choose M here: the
204 module will be called ite-cir.
207 tristate "Fintek Consumer Infrared Transceiver"
211 Say Y here to enable support for integrated infrared receiver
212 /transciever made by Fintek. This chip is found on assorted
213 Jetway motherboards (and of course, possibly others).
215 To compile this driver as a module, choose M here: the
216 module will be called fintek-cir.
219 tristate "Nuvoton w836x7hg Consumer Infrared Transceiver"
223 Say Y here to enable support for integrated infrared receiver
224 /transciever made by Nuvoton (formerly Winbond). This chip is
225 found in the ASRock ION 330HT, as well as assorted Intel
226 DP55-series motherboards (and of course, possibly others).
228 To compile this driver as a module, choose M here: the
229 module will be called nuvoton-cir.
232 tristate "RedRat3 IR Transceiver"
233 depends on USB_ARCH_HAS_HCD
239 Say Y here if you want to use a RedRat3 Infrared Transceiver.
241 To compile this driver as a module, choose M here: the
242 module will be called redrat3.
245 tristate "Streamzap PC Remote IR Receiver"
246 depends on USB_ARCH_HAS_HCD
250 Say Y here if you want to use a Streamzap PC Remote
253 To compile this driver as a module, choose M here: the
254 module will be called streamzap.
256 config IR_WINBOND_CIR
257 tristate "Winbond IR remote control"
258 depends on X86 && PNP
264 Say Y here if you want to use the IR remote functionality found
265 in some Winbond SuperI/O chips. Currently only the WPCD376I
266 chip is supported (included in some Intel Media series
269 To compile this driver as a module, choose M here: the module will
270 be called winbond_cir.
273 tristate "IguanaWorks USB IR Transceiver"
274 depends on USB_ARCH_HAS_HCD
278 Say Y here if you want to use the IguanaWorks USB IR Transceiver.
279 Both infrared receive and send are supported. If you want to
280 change the ID or the pin config, use the user space driver from
283 Only firmware 0x0205 and later is supported.
285 To compile this driver as a module, choose M here: the module will
289 tristate "TechnoTrend USB IR Receiver"
290 depends on USB_ARCH_HAS_HCD
296 Say Y here if you want to use the TechnoTrend USB IR Receiver. The
297 driver can control the led.
299 To compile this driver as a module, choose M here: the module will
303 tristate "Nokia N900 IR transmitter diode"
304 depends on OMAP_DM_TIMER && ARCH_OMAP2PLUS && LIRC && !ARCH_MULTIPLATFORM
306 Say Y or M here if you want to enable support for the IR
307 transmitter diode built in the Nokia N900 (RX51) device.
309 The driver uses omap DM timers for generating the carrier
312 source "drivers/media/rc/img-ir/Kconfig"
315 tristate "Remote Control Loopback Driver"
318 Say Y here if you want support for the remote control loopback
319 driver which allows TX data to be sent back as RX data.
320 This is mostly useful for debugging purposes.
322 If you're not sure, select N here.
324 To compile this driver as a module, choose M here: the module will
325 be called rc_loopback.
328 tristate "GPIO IR remote control"
331 Say Y if you want to use GPIO based IR Receiver.
333 To compile this driver as a module, choose M here: the module will
334 be called gpio-ir-recv.
337 tristate "ST remote control receiver"
338 depends on ARCH_STI && RC_CORE
340 Say Y here if you want support for ST remote control driver
341 which allows both IR and UHF RX.
342 The driver passes raw pulse and space information to the LIRC decoder.
344 If you're not sure, select N here.