Kconfig 8.1 KB

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