1config RC_CORE 2 tristate 3 depends on MEDIA_RC_SUPPORT 4 depends on INPUT 5 default y 6 7source "drivers/media/rc/keymaps/Kconfig" 8 9menuconfig RC_DECODERS 10 bool "Remote controller decoders" 11 depends on RC_CORE 12 default y 13 14if RC_DECODERS 15config LIRC 16 tristate "LIRC interface driver" 17 depends on RC_CORE 18 19 ---help--- 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"). 25 26config IR_LIRC_CODEC 27 tristate "Enable IR to LIRC bridge" 28 depends on RC_CORE 29 depends on LIRC 30 default y 31 32 ---help--- 33 Enable this option to pass raw IR to and from userspace via 34 the LIRC interface. 35 36 37config IR_NEC_DECODER 38 tristate "Enable IR raw decoder for the NEC protocol" 39 depends on RC_CORE 40 select BITREVERSE 41 default y 42 43 ---help--- 44 Enable this option if you have IR with NEC protocol, and 45 if the IR is decoded in software 46 47config IR_RC5_DECODER 48 tristate "Enable IR raw decoder for the RC-5 protocol" 49 depends on RC_CORE 50 select BITREVERSE 51 default y 52 53 ---help--- 54 Enable this option if you have IR with RC-5 protocol, and 55 if the IR is decoded in software 56 57config IR_RC6_DECODER 58 tristate "Enable IR raw decoder for the RC6 protocol" 59 depends on RC_CORE 60 select BITREVERSE 61 default y 62 63 ---help--- 64 Enable this option if you have an infrared remote control which 65 uses the RC6 protocol, and you need software decoding support. 66 67config IR_JVC_DECODER 68 tristate "Enable IR raw decoder for the JVC protocol" 69 depends on RC_CORE 70 select BITREVERSE 71 default y 72 73 ---help--- 74 Enable this option if you have an infrared remote control which 75 uses the JVC protocol, and you need software decoding support. 76 77config IR_SONY_DECODER 78 tristate "Enable IR raw decoder for the Sony protocol" 79 depends on RC_CORE 80 select BITREVERSE 81 default y 82 83 ---help--- 84 Enable this option if you have an infrared remote control which 85 uses the Sony protocol, and you need software decoding support. 86 87config IR_RC5_SZ_DECODER 88 tristate "Enable IR raw decoder for the RC-5 (streamzap) protocol" 89 depends on RC_CORE 90 select BITREVERSE 91 default y 92 93 ---help--- 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). 98 99config IR_SANYO_DECODER 100 tristate "Enable IR raw decoder for the Sanyo protocol" 101 depends on RC_CORE 102 default y 103 104 ---help--- 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. 108 109config IR_MCE_KBD_DECODER 110 tristate "Enable IR raw decoder for the MCE keyboard/mouse protocol" 111 depends on RC_CORE 112 select BITREVERSE 113 default y 114 115 ---help--- 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. 119endif #RC_DECODERS 120 121menuconfig RC_DEVICES 122 bool "Remote Controller devices" 123 depends on RC_CORE 124 125if RC_DEVICES 126 127config RC_ATI_REMOTE 128 tristate "ATI / X10 based USB RF remote controls" 129 depends on USB_ARCH_HAS_HCD 130 depends on RC_CORE 131 select USB 132 help 133 Say Y here if you want to use an X10 based USB remote control. 134 These are RF remotes with USB receivers. 135 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. 139 140 This driver provides mouse pointer, left and right mouse buttons, 141 and maps all the other remote buttons to keypress events. 142 143 To compile this driver as a module, choose M here: the module will be 144 called ati_remote. 145 146config IR_ENE 147 tristate "ENE eHome Receiver/Transceiver (pnp id: ENE0100/ENE02xxx)" 148 depends on PNP 149 depends on RC_CORE 150 ---help--- 151 Say Y here to enable support for integrated infrared receiver 152 /transceiver made by ENE. 153 154 You can see if you have it by looking at lspnp output. 155 Output should include ENE0100 ENE0200 or something similar. 156 157 To compile this driver as a module, choose M here: the 158 module will be called ene_ir. 159 160config IR_IMON 161 tristate "SoundGraph iMON Receiver and Display" 162 depends on USB_ARCH_HAS_HCD 163 depends on RC_CORE 164 select USB 165 ---help--- 166 Say Y here if you want to use a SoundGraph iMON (aka Antec Veris) 167 IR Receiver and/or LCD/VFD/VGA display. 168 169 To compile this driver as a module, choose M here: the 170 module will be called imon. 171 172config IR_MCEUSB 173 tristate "Windows Media Center Ed. eHome Infrared Transceiver" 174 depends on USB_ARCH_HAS_HCD 175 depends on RC_CORE 176 select USB 177 ---help--- 178 Say Y here if you want to use a Windows Media Center Edition 179 eHome Infrared Transceiver. 180 181 To compile this driver as a module, choose M here: the 182 module will be called mceusb. 183 184config IR_ITE_CIR 185 tristate "ITE Tech Inc. IT8712/IT8512 Consumer Infrared Transceiver" 186 depends on PNP 187 depends on RC_CORE 188 ---help--- 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 192 EEEBox 1501U. 193 194 To compile this driver as a module, choose M here: the 195 module will be called ite-cir. 196 197config IR_FINTEK 198 tristate "Fintek Consumer Infrared Transceiver" 199 depends on PNP 200 depends on RC_CORE 201 ---help--- 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). 205 206 To compile this driver as a module, choose M here: the 207 module will be called fintek-cir. 208 209config IR_NUVOTON 210 tristate "Nuvoton w836x7hg Consumer Infrared Transceiver" 211 depends on PNP 212 depends on RC_CORE 213 ---help--- 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). 218 219 To compile this driver as a module, choose M here: the 220 module will be called nuvoton-cir. 221 222config IR_REDRAT3 223 tristate "RedRat3 IR Transceiver" 224 depends on USB_ARCH_HAS_HCD 225 depends on RC_CORE 226 select USB 227 ---help--- 228 Say Y here if you want to use a RedRat3 Infrared Transceiver. 229 230 To compile this driver as a module, choose M here: the 231 module will be called redrat3. 232 233config IR_STREAMZAP 234 tristate "Streamzap PC Remote IR Receiver" 235 depends on USB_ARCH_HAS_HCD 236 depends on RC_CORE 237 select USB 238 ---help--- 239 Say Y here if you want to use a Streamzap PC Remote 240 Infrared Receiver. 241 242 To compile this driver as a module, choose M here: the 243 module will be called streamzap. 244 245config IR_WINBOND_CIR 246 tristate "Winbond IR remote control" 247 depends on X86 && PNP 248 depends on RC_CORE 249 select NEW_LEDS 250 select LEDS_CLASS 251 select LEDS_TRIGGERS 252 select BITREVERSE 253 ---help--- 254 Say Y here if you want to use the IR remote functionality found 255 in some Winbond SuperI/O chips. Currently only the WPCD376I 256 chip is supported (included in some Intel Media series 257 motherboards). 258 259 To compile this driver as a module, choose M here: the module will 260 be called winbond_cir. 261 262config IR_IGUANA 263 tristate "IguanaWorks USB IR Transceiver" 264 depends on USB_ARCH_HAS_HCD 265 depends on RC_CORE 266 select USB 267 ---help--- 268 Say Y here if you want to use the IguanaWorks USB IR Transceiver. 269 Both infrared receive and send are supported. If you want to 270 change the ID or the pin config, use the user space driver from 271 IguanaWorks. 272 273 Only firmware 0x0205 and later is supported. 274 275 To compile this driver as a module, choose M here: the module will 276 be called iguanair. 277 278config IR_TTUSBIR 279 tristate "TechnoTrend USB IR Receiver" 280 depends on USB_ARCH_HAS_HCD 281 depends on RC_CORE 282 select USB 283 select NEW_LEDS 284 select LEDS_CLASS 285 ---help--- 286 Say Y here if you want to use the TechnoTrend USB IR Receiver. The 287 driver can control the led. 288 289 To compile this driver as a module, choose M here: the module will 290 be called ttusbir. 291 292config IR_RX51 293 tristate "Nokia N900 IR transmitter diode" 294 depends on OMAP_DM_TIMER && LIRC 295 ---help--- 296 Say Y or M here if you want to enable support for the IR 297 transmitter diode built in the Nokia N900 (RX51) device. 298 299 The driver uses omap DM timers for generating the carrier 300 wave and pulses. 301 302config RC_LOOPBACK 303 tristate "Remote Control Loopback Driver" 304 depends on RC_CORE 305 ---help--- 306 Say Y here if you want support for the remote control loopback 307 driver which allows TX data to be sent back as RX data. 308 This is mostly useful for debugging purposes. 309 310 If you're not sure, select N here. 311 312 To compile this driver as a module, choose M here: the module will 313 be called rc_loopback. 314 315config IR_GPIO_CIR 316 tristate "GPIO IR remote control" 317 depends on RC_CORE 318 ---help--- 319 Say Y if you want to use GPIO based IR Receiver. 320 321 To compile this driver as a module, choose M here: the module will 322 be called gpio-ir-recv. 323 324endif #RC_DEVICES 325