Kconfig 8.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301
  1. menuconfig RC_CORE
  2. tristate "Remote Controller adapters"
  3. depends on INPUT
  4. default INPUT
  5. ---help---
  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.
  9. Enable this option if you have a video capture board even
  10. if you don't need IR, as otherwise, you may not be able to
  11. compile the driver for your adapter.
  12. if RC_CORE
  13. config LIRC
  14. tristate
  15. default y
  16. ---help---
  17. Enable this option to build the Linux Infrared Remote
  18. Control (LIRC) core device interface driver. The LIRC
  19. interface passes raw IR to and from userspace, where the
  20. LIRC daemon handles protocol decoding for IR reception and
  21. encoding for IR transmitting (aka "blasting").
  22. config USER_RC_INPUT
  23. tristate "User Space Input device wrapper for Remote Control"
  24. depends on RC_CORE
  25. ---help---
  26. Say Y if you want to report remote control input events
  27. from userspace.
  28. To compile this driver as a module, choose M here: the module will
  29. be called user-rc-input.
  30. config USER_SP_RC_INPUT
  31. tristate "User Space Input device wrapper for Standby Processor Remote Control"
  32. depends on RC_CORE
  33. ---help---
  34. Say Y if you want to report remote control input events
  35. from userspace.
  36. To compile this driver as a module, choose M here: the module will
  37. be called user-sp-input.
  38. source "drivers/media/rc/keymaps/Kconfig"
  39. config IR_NEC_DECODER
  40. tristate "Enable IR raw decoder for the NEC protocol"
  41. depends on RC_CORE
  42. select BITREVERSE
  43. default y
  44. ---help---
  45. Enable this option if you have IR with NEC protocol, and
  46. if the IR is decoded in software
  47. config 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. ---help---
  53. Enable this option if you have IR with RC-5 protocol, and
  54. if the IR is decoded in software
  55. config IR_RC6_DECODER
  56. tristate "Enable IR raw decoder for the RC6 protocol"
  57. depends on RC_CORE
  58. select BITREVERSE
  59. default y
  60. ---help---
  61. Enable this option if you have an infrared remote control which
  62. uses the RC6 protocol, and you need software decoding support.
  63. config IR_JVC_DECODER
  64. tristate "Enable IR raw decoder for the JVC protocol"
  65. depends on RC_CORE
  66. select BITREVERSE
  67. default y
  68. ---help---
  69. Enable this option if you have an infrared remote control which
  70. uses the JVC protocol, and you need software decoding support.
  71. config IR_SONY_DECODER
  72. tristate "Enable IR raw decoder for the Sony protocol"
  73. depends on RC_CORE
  74. default y
  75. ---help---
  76. Enable this option if you have an infrared remote control which
  77. uses the Sony protocol, and you need software decoding support.
  78. config IR_RC5_SZ_DECODER
  79. tristate "Enable IR raw decoder for the RC-5 (streamzap) protocol"
  80. depends on RC_CORE
  81. select BITREVERSE
  82. default y
  83. ---help---
  84. Enable this option if you have IR with RC-5 (streamzap) protocol,
  85. and if the IR is decoded in software. (The Streamzap PC Remote
  86. uses an IR protocol that is almost standard RC-5, but not quite,
  87. as it uses an additional bit).
  88. config IR_SANYO_DECODER
  89. tristate "Enable IR raw decoder for the Sanyo protocol"
  90. depends on RC_CORE
  91. default y
  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. config IR_MCE_KBD_DECODER
  97. tristate "Enable IR raw decoder for the MCE keyboard/mouse protocol"
  98. depends on RC_CORE
  99. select BITREVERSE
  100. default y
  101. ---help---
  102. Enable this option if you have a Microsoft Remote Keyboard for
  103. Windows Media Center Edition, which you would like to use with
  104. a raw IR receiver in your system.
  105. config IR_LIRC_CODEC
  106. tristate "Enable IR to LIRC bridge"
  107. depends on RC_CORE
  108. depends on LIRC
  109. default y
  110. ---help---
  111. Enable this option to pass raw IR to and from userspace via
  112. the LIRC interface.
  113. config RC_ATI_REMOTE
  114. tristate "ATI / X10 based USB RF remote controls"
  115. depends on USB_ARCH_HAS_HCD
  116. depends on RC_CORE
  117. select USB
  118. help
  119. Say Y here if you want to use an X10 based USB remote control.
  120. These are RF remotes with USB receivers.
  121. Such devices include the ATI remote that comes with many of ATI's
  122. All-In-Wonder video cards, the X10 "Lola" remote, NVIDIA RF remote,
  123. Medion RF remote, and SnapStream FireFly remote.
  124. This driver provides mouse pointer, left and right mouse buttons,
  125. and maps all the other remote buttons to keypress events.
  126. To compile this driver as a module, choose M here: the module will be
  127. called ati_remote.
  128. config IR_ENE
  129. tristate "ENE eHome Receiver/Transceiver (pnp id: ENE0100/ENE02xxx)"
  130. depends on PNP
  131. depends on RC_CORE
  132. ---help---
  133. Say Y here to enable support for integrated infrared receiver
  134. /transceiver made by ENE.
  135. You can see if you have it by looking at lspnp output.
  136. Output should include ENE0100 ENE0200 or something similar.
  137. To compile this driver as a module, choose M here: the
  138. module will be called ene_ir.
  139. config IR_IMON
  140. tristate "SoundGraph iMON Receiver and Display"
  141. depends on USB_ARCH_HAS_HCD
  142. depends on RC_CORE
  143. select USB
  144. ---help---
  145. Say Y here if you want to use a SoundGraph iMON (aka Antec Veris)
  146. IR Receiver and/or LCD/VFD/VGA display.
  147. To compile this driver as a module, choose M here: the
  148. module will be called imon.
  149. config IR_MCEUSB
  150. tristate "Windows Media Center Ed. eHome Infrared Transceiver"
  151. depends on USB_ARCH_HAS_HCD
  152. depends on RC_CORE
  153. select USB
  154. ---help---
  155. Say Y here if you want to use a Windows Media Center Edition
  156. eHome Infrared Transceiver.
  157. To compile this driver as a module, choose M here: the
  158. module will be called mceusb.
  159. config IR_ITE_CIR
  160. tristate "ITE Tech Inc. IT8712/IT8512 Consumer Infrared Transceiver"
  161. depends on PNP
  162. depends on RC_CORE
  163. ---help---
  164. Say Y here to enable support for integrated infrared receivers
  165. /transceivers made by ITE Tech Inc. These are found in
  166. several ASUS devices, like the ASUS Digimatrix or the ASUS
  167. EEEBox 1501U.
  168. To compile this driver as a module, choose M here: the
  169. module will be called ite-cir.
  170. config IR_FINTEK
  171. tristate "Fintek Consumer Infrared Transceiver"
  172. depends on PNP
  173. depends on RC_CORE
  174. ---help---
  175. Say Y here to enable support for integrated infrared receiver
  176. /transciever made by Fintek. This chip is found on assorted
  177. Jetway motherboards (and of course, possibly others).
  178. To compile this driver as a module, choose M here: the
  179. module will be called fintek-cir.
  180. config IR_NUVOTON
  181. tristate "Nuvoton w836x7hg Consumer Infrared Transceiver"
  182. depends on PNP
  183. depends on RC_CORE
  184. ---help---
  185. Say Y here to enable support for integrated infrared receiver
  186. /transciever made by Nuvoton (formerly Winbond). This chip is
  187. found in the ASRock ION 330HT, as well as assorted Intel
  188. DP55-series motherboards (and of course, possibly others).
  189. To compile this driver as a module, choose M here: the
  190. module will be called nuvoton-cir.
  191. config IR_REDRAT3
  192. tristate "RedRat3 IR Transceiver"
  193. depends on USB_ARCH_HAS_HCD
  194. depends on RC_CORE
  195. select USB
  196. ---help---
  197. Say Y here if you want to use a RedRat3 Infrared Transceiver.
  198. To compile this driver as a module, choose M here: the
  199. module will be called redrat3.
  200. config IR_STREAMZAP
  201. tristate "Streamzap PC Remote IR Receiver"
  202. depends on USB_ARCH_HAS_HCD
  203. depends on RC_CORE
  204. select USB
  205. ---help---
  206. Say Y here if you want to use a Streamzap PC Remote
  207. Infrared Receiver.
  208. To compile this driver as a module, choose M here: the
  209. module will be called streamzap.
  210. config IR_WINBOND_CIR
  211. tristate "Winbond IR remote control"
  212. depends on X86 && PNP
  213. depends on RC_CORE
  214. select NEW_LEDS
  215. select LEDS_CLASS
  216. select LEDS_TRIGGERS
  217. select BITREVERSE
  218. ---help---
  219. Say Y here if you want to use the IR remote functionality found
  220. in some Winbond SuperI/O chips. Currently only the WPCD376I
  221. chip is supported (included in some Intel Media series
  222. motherboards).
  223. To compile this driver as a module, choose M here: the module will
  224. be called winbond_cir.
  225. config RC_LOOPBACK
  226. tristate "Remote Control Loopback Driver"
  227. depends on RC_CORE
  228. ---help---
  229. Say Y here if you want support for the remote control loopback
  230. driver which allows TX data to be sent back as RX data.
  231. This is mostly useful for debugging purposes.
  232. If you're not sure, select N here.
  233. To compile this driver as a module, choose M here: the module will
  234. be called rc_loopback.
  235. config IR_GPIO_CIR
  236. tristate "GPIO IR remote control"
  237. depends on RC_CORE
  238. ---help---
  239. Say Y if you want to use GPIO based IR Receiver.
  240. To compile this driver as a module, choose M here: the module will
  241. be called gpio-ir-recv.
  242. endif #RC_CORE