Kconfig 11 KB

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