Kconfig 11 KB

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