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, and you need software decoding support.
106 config IR_MCE_KBD_DECODER
107 tristate "Enable IR raw decoder for the MCE keyboard/mouse protocol"
113 Enable this option if you have a Microsoft Remote Keyboard for
114 Windows Media Center Edition, which you would like to use with
115 a raw IR receiver in your system.
117 config IR_XMP_DECODER
118 tristate "Enable IR raw decoder for the XMP protocol"
124 Enable this option if you have IR with XMP protocol, and
125 if the IR is decoded in software
128 menuconfig RC_DEVICES
129 bool "Remote Controller devices"
135 tristate "ATI / X10 based USB RF remote controls"
136 depends on USB_ARCH_HAS_HCD
140 Say Y here if you want to use an X10 based USB remote control.
141 These are RF remotes with USB receivers.
143 Such devices include the ATI remote that comes with many of ATI's
144 All-In-Wonder video cards, the X10 "Lola" remote, NVIDIA RF remote,
145 Medion RF remote, and SnapStream FireFly remote.
147 This driver provides mouse pointer, left and right mouse buttons,
148 and maps all the other remote buttons to keypress events.
150 To compile this driver as a module, choose M here: the module will be
154 tristate "ENE eHome Receiver/Transceiver (pnp id: ENE0100/ENE02xxx)"
158 Say Y here to enable support for integrated infrared receiver
159 /transceiver made by ENE.
161 You can see if you have it by looking at lspnp output.
162 Output should include ENE0100 ENE0200 or something similar.
164 To compile this driver as a module, choose M here: the
165 module will be called ene_ir.
168 tristate "Hisilicon hix5hd2 IR remote control"
171 Say Y here if you want to use hisilicon hix5hd2 remote control.
172 To compile this driver as a module, choose M here: the module will be
175 If you're not sure, select N here
178 tristate "SoundGraph iMON Receiver and Display"
179 depends on USB_ARCH_HAS_HCD
183 Say Y here if you want to use a SoundGraph iMON (aka Antec Veris)
184 IR Receiver and/or LCD/VFD/VGA display.
186 To compile this driver as a module, choose M here: the
187 module will be called imon.
190 tristate "Windows Media Center Ed. eHome Infrared Transceiver"
191 depends on USB_ARCH_HAS_HCD
195 Say Y here if you want to use a Windows Media Center Edition
196 eHome Infrared Transceiver.
198 To compile this driver as a module, choose M here: the
199 module will be called mceusb.
202 tristate "ITE Tech Inc. IT8712/IT8512 Consumer Infrared Transceiver"
206 Say Y here to enable support for integrated infrared receivers
207 /transceivers made by ITE Tech Inc. These are found in
208 several ASUS devices, like the ASUS Digimatrix or the ASUS
211 To compile this driver as a module, choose M here: the
212 module will be called ite-cir.
215 tristate "Fintek Consumer Infrared Transceiver"
219 Say Y here to enable support for integrated infrared receiver
220 /transciever made by Fintek. This chip is found on assorted
221 Jetway motherboards (and of course, possibly others).
223 To compile this driver as a module, choose M here: the
224 module will be called fintek-cir.
227 tristate "Nuvoton w836x7hg Consumer Infrared Transceiver"
231 Say Y here to enable support for integrated infrared receiver
232 /transciever made by Nuvoton (formerly Winbond). This chip is
233 found in the ASRock ION 330HT, as well as assorted Intel
234 DP55-series motherboards (and of course, possibly others).
236 To compile this driver as a module, choose M here: the
237 module will be called nuvoton-cir.
240 tristate "RedRat3 IR Transceiver"
241 depends on USB_ARCH_HAS_HCD
247 Say Y here if you want to use a RedRat3 Infrared Transceiver.
249 To compile this driver as a module, choose M here: the
250 module will be called redrat3.
253 tristate "Streamzap PC Remote IR Receiver"
254 depends on USB_ARCH_HAS_HCD
258 Say Y here if you want to use a Streamzap PC Remote
261 To compile this driver as a module, choose M here: the
262 module will be called streamzap.
264 config IR_WINBOND_CIR
265 tristate "Winbond IR remote control"
266 depends on X86 && PNP
272 Say Y here if you want to use the IR remote functionality found
273 in some Winbond SuperI/O chips. Currently only the WPCD376I
274 chip is supported (included in some Intel Media series
277 To compile this driver as a module, choose M here: the module will
278 be called winbond_cir.
281 tristate "IguanaWorks USB IR Transceiver"
282 depends on USB_ARCH_HAS_HCD
286 Say Y here if you want to use the IguanaWorks USB IR Transceiver.
287 Both infrared receive and send are supported. If you want to
288 change the ID or the pin config, use the user space driver from
291 Only firmware 0x0205 and later is supported.
293 To compile this driver as a module, choose M here: the module will
297 tristate "TechnoTrend USB IR Receiver"
298 depends on USB_ARCH_HAS_HCD
304 Say Y here if you want to use the TechnoTrend USB IR Receiver. The
305 driver can control the led.
307 To compile this driver as a module, choose M here: the module will
311 tristate "Nokia N900 IR transmitter diode"
312 depends on OMAP_DM_TIMER && ARCH_OMAP2PLUS && LIRC && !ARCH_MULTIPLATFORM
314 Say Y or M here if you want to enable support for the IR
315 transmitter diode built in the Nokia N900 (RX51) device.
317 The driver uses omap DM timers for generating the carrier
320 source "drivers/media/rc/img-ir/Kconfig"
323 tristate "Remote Control Loopback Driver"
326 Say Y here if you want support for the remote control loopback
327 driver which allows TX data to be sent back as RX data.
328 This is mostly useful for debugging purposes.
330 If you're not sure, select N here.
332 To compile this driver as a module, choose M here: the module will
333 be called rc_loopback.
336 tristate "GPIO IR remote control"
339 Say Y if you want to use GPIO based IR Receiver.
341 To compile this driver as a module, choose M here: the module will
342 be called gpio-ir-recv.
345 tristate "ST remote control receiver"
347 depends on ARCH_STI || COMPILE_TEST
349 Say Y here if you want support for ST remote control driver
350 which allows both IR and UHF RX.
351 The driver passes raw pulse and space information to the LIRC decoder.
353 If you're not sure, select N here.
356 tristate "SUNXI IR remote control"
358 depends on ARCH_SUNXI || COMPILE_TEST
360 Say Y if you want to use sunXi internal IR Controller
362 To compile this driver as a module, choose M here: the module will