2 tristate "Remote Controller adapters"
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.
21 Enable this option to build the Linux Infrared Remote
22 Control (LIRC) core device interface driver. The LIRC
23 interface passes raw IR to and from userspace, where the
24 LIRC daemon handles protocol decoding for IR reception and
25 encoding for IR transmitting (aka "blasting").
27 source "drivers/media/rc/keymaps/Kconfig"
30 tristate "Enable IR raw decoder for the NEC protocol"
36 Enable this option if you have IR with NEC protocol, and
37 if the IR is decoded in software
40 tristate "Enable IR raw decoder for the RC-5 protocol"
46 Enable this option if you have IR with RC-5 protocol, and
47 if the IR is decoded in software
50 tristate "Enable IR raw decoder for the RC6 protocol"
56 Enable this option if you have an infrared remote control which
57 uses the RC6 protocol, and you need software decoding support.
60 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"
76 Enable this option if you have an infrared remote control which
77 uses the Sony protocol, and you need software decoding support.
79 config IR_RC5_SZ_DECODER
80 tristate "Enable IR raw decoder for the RC-5 (streamzap) protocol"
86 Enable this option if you have IR with RC-5 (streamzap) protocol,
87 and if the IR is decoded in software. (The Streamzap PC Remote
88 uses an IR protocol that is almost standard RC-5, but not quite,
89 as it uses an additional bit).
91 config IR_SANYO_DECODER
92 tristate "Enable IR raw decoder for the Sanyo protocol"
97 Enable this option if you have an infrared remote control which
98 uses the Sanyo protocol (Sanyo, Aiwa, Chinon remotes),
99 and you need software decoding support.
101 config IR_MCE_KBD_DECODER
102 tristate "Enable IR raw decoder for the MCE keyboard/mouse protocol"
108 Enable this option if you have a Microsoft Remote Keyboard for
109 Windows Media Center Edition, which you would like to use with
110 a raw IR receiver in your system.
113 tristate "Enable IR to LIRC bridge"
119 Enable this option to pass raw IR to and from userspace via
123 tristate "ATI / X10 based USB RF remote controls"
124 depends on USB_ARCH_HAS_HCD
128 Say Y here if you want to use an X10 based USB remote control.
129 These are RF remotes with USB receivers.
131 Such devices include the ATI remote that comes with many of ATI's
132 All-In-Wonder video cards, the X10 "Lola" remote, NVIDIA RF remote,
133 Medion RF remote, and SnapStream FireFly remote.
135 This driver provides mouse pointer, left and right mouse buttons,
136 and maps all the other remote buttons to keypress events.
138 To compile this driver as a module, choose M here: the module will be
142 tristate "ENE eHome Receiver/Transceiver (pnp id: ENE0100/ENE02xxx)"
146 Say Y here to enable support for integrated infrared receiver
147 /transceiver made by ENE.
149 You can see if you have it by looking at lspnp output.
150 Output should include ENE0100 ENE0200 or something similar.
152 To compile this driver as a module, choose M here: the
153 module will be called ene_ir.
156 tristate "SoundGraph iMON Receiver and Display"
157 depends on USB_ARCH_HAS_HCD
161 Say Y here if you want to use a SoundGraph iMON (aka Antec Veris)
162 IR Receiver and/or LCD/VFD/VGA display.
164 To compile this driver as a module, choose M here: the
165 module will be called imon.
168 tristate "Windows Media Center Ed. eHome Infrared Transceiver"
169 depends on USB_ARCH_HAS_HCD
173 Say Y here if you want to use a Windows Media Center Edition
174 eHome Infrared Transceiver.
176 To compile this driver as a module, choose M here: the
177 module will be called mceusb.
180 tristate "ITE Tech Inc. IT8712/IT8512 Consumer Infrared Transceiver"
184 Say Y here to enable support for integrated infrared receivers
185 /transceivers made by ITE Tech Inc. These are found in
186 several ASUS devices, like the ASUS Digimatrix or the ASUS
189 To compile this driver as a module, choose M here: the
190 module will be called ite-cir.
193 tristate "Fintek Consumer Infrared Transceiver"
197 Say Y here to enable support for integrated infrared receiver
198 /transciever made by Fintek. This chip is found on assorted
199 Jetway motherboards (and of course, possibly others).
201 To compile this driver as a module, choose M here: the
202 module will be called fintek-cir.
205 tristate "Nuvoton w836x7hg Consumer Infrared Transceiver"
209 Say Y here to enable support for integrated infrared receiver
210 /transciever made by Nuvoton (formerly Winbond). This chip is
211 found in the ASRock ION 330HT, as well as assorted Intel
212 DP55-series motherboards (and of course, possibly others).
214 To compile this driver as a module, choose M here: the
215 module will be called nuvoton-cir.
218 tristate "RedRat3 IR Transceiver"
219 depends on USB_ARCH_HAS_HCD
223 Say Y here if you want to use a RedRat3 Infrared Transceiver.
225 To compile this driver as a module, choose M here: the
226 module will be called redrat3.
229 tristate "Streamzap PC Remote IR Receiver"
230 depends on USB_ARCH_HAS_HCD
234 Say Y here if you want to use a Streamzap PC Remote
237 To compile this driver as a module, choose M here: the
238 module will be called streamzap.
240 config IR_WINBOND_CIR
241 tristate "Winbond IR remote control"
242 depends on X86 && PNP
249 Say Y here if you want to use the IR remote functionality found
250 in some Winbond SuperI/O chips. Currently only the WPCD376I
251 chip is supported (included in some Intel Media series
254 To compile this driver as a module, choose M here: the module will
255 be called winbond_cir.
258 tristate "Remote Control Loopback Driver"
261 Say Y here if you want support for the remote control loopback
262 driver which allows TX data to be sent back as RX data.
263 This is mostly useful for debugging purposes.
265 If you're not sure, select N here.
267 To compile this driver as a module, choose M here: the module will
268 be called rc_loopback.
271 tristate "GPIO IR remote control"
274 Say Y if you want to use GPIO based IR Receiver.
276 To compile this driver as a module, choose M here: the module will
277 be called gpio-ir-recv.