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_SANYO_DECODER 88 tristate "Enable IR raw decoder for the Sanyo protocol" 89 depends on RC_CORE 90 default y 91 92 ---help--- 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. 96 97config IR_SHARP_DECODER 98 tristate "Enable IR raw decoder for the Sharp protocol" 99 depends on RC_CORE 100 default y 101 102 ---help--- 103 Enable this option if you have an infrared remote control which 104 uses the Sharp protocol (Sharp, Denon), and you need software 105 decoding support. 106 107config IR_MCE_KBD_DECODER 108 tristate "Enable IR raw decoder for the MCE keyboard/mouse protocol" 109 depends on RC_CORE 110 select BITREVERSE 111 default y 112 113 ---help--- 114 Enable this option if you have a Microsoft Remote Keyboard for 115 Windows Media Center Edition, which you would like to use with 116 a raw IR receiver in your system. 117 118config IR_XMP_DECODER 119 tristate "Enable IR raw decoder for the XMP protocol" 120 depends on RC_CORE 121 select BITREVERSE 122 default y 123 124 ---help--- 125 Enable this option if you have IR with XMP protocol, and 126 if the IR is decoded in software 127endif #RC_DECODERS 128 129menuconfig RC_DEVICES 130 bool "Remote Controller devices" 131 depends on RC_CORE 132 133if RC_DEVICES 134 135config RC_ATI_REMOTE 136 tristate "ATI / X10 based USB RF remote controls" 137 depends on USB_ARCH_HAS_HCD 138 depends on RC_CORE 139 select USB 140 help 141 Say Y here if you want to use an X10 based USB remote control. 142 These are RF remotes with USB receivers. 143 144 Such devices include the ATI remote that comes with many of ATI's 145 All-In-Wonder video cards, the X10 "Lola" remote, NVIDIA RF remote, 146 Medion RF remote, and SnapStream FireFly remote. 147 148 This driver provides mouse pointer, left and right mouse buttons, 149 and maps all the other remote buttons to keypress events. 150 151 To compile this driver as a module, choose M here: the module will be 152 called ati_remote. 153 154config IR_ENE 155 tristate "ENE eHome Receiver/Transceiver (pnp id: ENE0100/ENE02xxx)" 156 depends on PNP 157 depends on RC_CORE 158 ---help--- 159 Say Y here to enable support for integrated infrared receiver 160 /transceiver made by ENE. 161 162 You can see if you have it by looking at lspnp output. 163 Output should include ENE0100 ENE0200 or something similar. 164 165 To compile this driver as a module, choose M here: the 166 module will be called ene_ir. 167 168config IR_HIX5HD2 169 tristate "Hisilicon hix5hd2 IR remote control" 170 depends on RC_CORE 171 help 172 Say Y here if you want to use hisilicon hix5hd2 remote control. 173 To compile this driver as a module, choose M here: the module will be 174 called ir-hix5hd2. 175 176 If you're not sure, select N here 177 178config IR_IMON 179 tristate "SoundGraph iMON Receiver and Display" 180 depends on USB_ARCH_HAS_HCD 181 depends on RC_CORE 182 select USB 183 ---help--- 184 Say Y here if you want to use a SoundGraph iMON (aka Antec Veris) 185 IR Receiver and/or LCD/VFD/VGA display. 186 187 To compile this driver as a module, choose M here: the 188 module will be called imon. 189 190config IR_MCEUSB 191 tristate "Windows Media Center Ed. eHome Infrared Transceiver" 192 depends on USB_ARCH_HAS_HCD 193 depends on RC_CORE 194 select USB 195 ---help--- 196 Say Y here if you want to use a Windows Media Center Edition 197 eHome Infrared Transceiver. 198 199 To compile this driver as a module, choose M here: the 200 module will be called mceusb. 201 202config IR_ITE_CIR 203 tristate "ITE Tech Inc. IT8712/IT8512 Consumer Infrared Transceiver" 204 depends on PNP 205 depends on RC_CORE 206 ---help--- 207 Say Y here to enable support for integrated infrared receivers 208 /transceivers made by ITE Tech Inc. These are found in 209 several ASUS devices, like the ASUS Digimatrix or the ASUS 210 EEEBox 1501U. 211 212 To compile this driver as a module, choose M here: the 213 module will be called ite-cir. 214 215config IR_FINTEK 216 tristate "Fintek Consumer Infrared Transceiver" 217 depends on PNP 218 depends on RC_CORE 219 ---help--- 220 Say Y here to enable support for integrated infrared receiver 221 /transciever made by Fintek. This chip is found on assorted 222 Jetway motherboards (and of course, possibly others). 223 224 To compile this driver as a module, choose M here: the 225 module will be called fintek-cir. 226 227config IR_MESON 228 tristate "Amlogic Meson IR remote receiver" 229 depends on RC_CORE 230 depends on ARCH_MESON || COMPILE_TEST 231 ---help--- 232 Say Y if you want to use the IR remote receiver available 233 on Amlogic Meson SoCs. 234 235 To compile this driver as a module, choose M here: the 236 module will be called meson-ir. 237 238config IR_NUVOTON 239 tristate "Nuvoton w836x7hg Consumer Infrared Transceiver" 240 depends on PNP 241 depends on RC_CORE 242 ---help--- 243 Say Y here to enable support for integrated infrared receiver 244 /transciever made by Nuvoton (formerly Winbond). This chip is 245 found in the ASRock ION 330HT, as well as assorted Intel 246 DP55-series motherboards (and of course, possibly others). 247 248 To compile this driver as a module, choose M here: the 249 module will be called nuvoton-cir. 250 251config IR_REDRAT3 252 tristate "RedRat3 IR Transceiver" 253 depends on USB_ARCH_HAS_HCD 254 depends on RC_CORE 255 select NEW_LEDS 256 select LEDS_CLASS 257 select USB 258 ---help--- 259 Say Y here if you want to use a RedRat3 Infrared Transceiver. 260 261 To compile this driver as a module, choose M here: the 262 module will be called redrat3. 263 264config IR_STREAMZAP 265 tristate "Streamzap PC Remote IR Receiver" 266 depends on USB_ARCH_HAS_HCD 267 depends on RC_CORE 268 select USB 269 ---help--- 270 Say Y here if you want to use a Streamzap PC Remote 271 Infrared Receiver. 272 273 To compile this driver as a module, choose M here: the 274 module will be called streamzap. 275 276config IR_WINBOND_CIR 277 tristate "Winbond IR remote control" 278 depends on X86 && PNP 279 depends on RC_CORE 280 select NEW_LEDS 281 select LEDS_CLASS 282 select BITREVERSE 283 ---help--- 284 Say Y here if you want to use the IR remote functionality found 285 in some Winbond SuperI/O chips. Currently only the WPCD376I 286 chip is supported (included in some Intel Media series 287 motherboards). 288 289 To compile this driver as a module, choose M here: the module will 290 be called winbond_cir. 291 292config IR_IGORPLUGUSB 293 tristate "IgorPlug-USB IR Receiver" 294 depends on USB_ARCH_HAS_HCD 295 depends on RC_CORE 296 select USB 297 ---help--- 298 Say Y here if you want to use the IgorPlug-USB IR Receiver by 299 Igor Cesko. This device is included on the Fit-PC2. 300 301 Note that this device can only record bursts of 36 IR pulses and 302 spaces, which is not enough for the NEC, Sanyo and RC-6 protocol. 303 304 To compile this driver as a module, choose M here: the module will 305 be called igorplugusb. 306 307config IR_IGUANA 308 tristate "IguanaWorks USB IR Transceiver" 309 depends on USB_ARCH_HAS_HCD 310 depends on RC_CORE 311 select USB 312 ---help--- 313 Say Y here if you want to use the IguanaWorks USB IR Transceiver. 314 Both infrared receive and send are supported. If you want to 315 change the ID or the pin config, use the user space driver from 316 IguanaWorks. 317 318 Only firmware 0x0205 and later is supported. 319 320 To compile this driver as a module, choose M here: the module will 321 be called iguanair. 322 323config IR_TTUSBIR 324 tristate "TechnoTrend USB IR Receiver" 325 depends on USB_ARCH_HAS_HCD 326 depends on RC_CORE 327 select USB 328 select NEW_LEDS 329 select LEDS_CLASS 330 ---help--- 331 Say Y here if you want to use the TechnoTrend USB IR Receiver. The 332 driver can control the led. 333 334 To compile this driver as a module, choose M here: the module will 335 be called ttusbir. 336 337config IR_RX51 338 tristate "Nokia N900 IR transmitter diode" 339 depends on OMAP_DM_TIMER && ARCH_OMAP2PLUS && LIRC && !ARCH_MULTIPLATFORM 340 ---help--- 341 Say Y or M here if you want to enable support for the IR 342 transmitter diode built in the Nokia N900 (RX51) device. 343 344 The driver uses omap DM timers for generating the carrier 345 wave and pulses. 346 347source "drivers/media/rc/img-ir/Kconfig" 348 349config RC_LOOPBACK 350 tristate "Remote Control Loopback Driver" 351 depends on RC_CORE 352 ---help--- 353 Say Y here if you want support for the remote control loopback 354 driver which allows TX data to be sent back as RX data. 355 This is mostly useful for debugging purposes. 356 357 If you're not sure, select N here. 358 359 To compile this driver as a module, choose M here: the module will 360 be called rc_loopback. 361 362config IR_GPIO_CIR 363 tristate "GPIO IR remote control" 364 depends on RC_CORE 365 ---help--- 366 Say Y if you want to use GPIO based IR Receiver. 367 368 To compile this driver as a module, choose M here: the module will 369 be called gpio-ir-recv. 370 371config RC_ST 372 tristate "ST remote control receiver" 373 depends on RC_CORE 374 depends on ARCH_STI || COMPILE_TEST 375 ---help--- 376 Say Y here if you want support for ST remote control driver 377 which allows both IR and UHF RX. 378 The driver passes raw pulse and space information to the LIRC decoder. 379 380 If you're not sure, select N here. 381 382config IR_SUNXI 383 tristate "SUNXI IR remote control" 384 depends on RC_CORE 385 depends on ARCH_SUNXI || COMPILE_TEST 386 ---help--- 387 Say Y if you want to use sunXi internal IR Controller 388 389 To compile this driver as a module, choose M here: the module will 390 be called sunxi-ir. 391 392endif #RC_DEVICES 393