Kconfig 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. menuconfig RC_CORE
  3. tristate "Remote Controller support"
  4. depends on 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. Say Y when you have a TV or an IR device.
  13. if RC_CORE
  14. config BPF_LIRC_MODE2
  15. bool "Support for eBPF programs attached to lirc devices"
  16. depends on BPF_SYSCALL
  17. depends on RC_CORE=y
  18. depends on LIRC
  19. help
  20. Allow attaching eBPF programs to a lirc device using the bpf(2)
  21. syscall command BPF_PROG_ATTACH. This is supported for raw IR
  22. receivers.
  23. These eBPF programs can be used to decode IR into scancodes, for
  24. IR protocols not supported by the kernel decoders.
  25. config LIRC
  26. bool "LIRC user interface"
  27. help
  28. Enable this option to enable the Linux Infrared Remote
  29. Control user interface (e.g. /dev/lirc*). This interface
  30. passes raw IR to and from userspace, which is needed for
  31. IR transmitting (aka "blasting") and for the lirc daemon.
  32. source "drivers/media/rc/keymaps/Kconfig"
  33. menuconfig RC_DECODERS
  34. bool "Remote controller decoders"
  35. if RC_DECODERS
  36. config IR_IMON_DECODER
  37. tristate "Enable IR raw decoder for the iMON protocol"
  38. help
  39. Enable this option if you have iMON PAD or Antec Veris infrared
  40. remote control and you would like to use it with a raw IR
  41. receiver, or if you wish to use an encoder to transmit this IR.
  42. config IR_JVC_DECODER
  43. tristate "Enable IR raw decoder for the JVC protocol"
  44. select BITREVERSE
  45. help
  46. Enable this option if you have an infrared remote control which
  47. uses the JVC protocol, and you need software decoding support.
  48. config IR_MCE_KBD_DECODER
  49. tristate "Enable IR raw decoder for the MCE keyboard/mouse protocol"
  50. select BITREVERSE
  51. help
  52. Enable this option if you have a Microsoft Remote Keyboard for
  53. Windows Media Center Edition, which you would like to use with
  54. a raw IR receiver in your system.
  55. config IR_NEC_DECODER
  56. tristate "Enable IR raw decoder for the NEC protocol"
  57. select BITREVERSE
  58. help
  59. Enable this option if you have IR with NEC protocol, and
  60. if the IR is decoded in software
  61. config IR_RC5_DECODER
  62. tristate "Enable IR raw decoder for the RC-5 protocol"
  63. select BITREVERSE
  64. help
  65. Enable this option if you have IR with RC-5 protocol, and
  66. if the IR is decoded in software
  67. config IR_RC6_DECODER
  68. tristate "Enable IR raw decoder for the RC6 protocol"
  69. select BITREVERSE
  70. help
  71. Enable this option if you have an infrared remote control which
  72. uses the RC6 protocol, and you need software decoding support.
  73. config IR_RCMM_DECODER
  74. tristate "Enable IR raw decoder for the RC-MM protocol"
  75. help
  76. Enable this option when you have IR with RC-MM protocol, and
  77. you need the software decoder. The driver supports 12,
  78. 24 and 32 bits RC-MM variants. You can enable or disable the
  79. different modes using the following RC protocol keywords:
  80. 'rc-mm-12', 'rc-mm-24' and 'rc-mm-32'.
  81. To compile this driver as a module, choose M here: the module
  82. will be called ir-rcmm-decoder.
  83. config IR_SANYO_DECODER
  84. tristate "Enable IR raw decoder for the Sanyo protocol"
  85. select BITREVERSE
  86. help
  87. Enable this option if you have an infrared remote control which
  88. uses the Sanyo protocol (Sanyo, Aiwa, Chinon remotes),
  89. and you need software decoding support.
  90. config IR_SHARP_DECODER
  91. tristate "Enable IR raw decoder for the Sharp protocol"
  92. select BITREVERSE
  93. help
  94. Enable this option if you have an infrared remote control which
  95. uses the Sharp protocol (Sharp, Denon), and you need software
  96. decoding support.
  97. config IR_SONY_DECODER
  98. tristate "Enable IR raw decoder for the Sony protocol"
  99. select BITREVERSE
  100. help
  101. Enable this option if you have an infrared remote control which
  102. uses the Sony protocol, and you need software decoding support.
  103. config IR_XMP_DECODER
  104. tristate "Enable IR raw decoder for the XMP protocol"
  105. select BITREVERSE
  106. help
  107. Enable this option if you have IR with XMP protocol, and
  108. if the IR is decoded in software
  109. endif #RC_DECODERS
  110. menuconfig RC_DEVICES
  111. bool "Remote Controller devices"
  112. if RC_DEVICES
  113. config IR_ENE
  114. tristate "ENE eHome Receiver/Transceiver (pnp id: ENE0100/ENE02xxx)"
  115. depends on PNP || COMPILE_TEST
  116. depends on HAS_IOPORT
  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_FINTEK
  125. tristate "Fintek Consumer Infrared Transceiver"
  126. depends on PNP || COMPILE_TEST
  127. depends on HAS_IOPORT
  128. help
  129. Say Y here to enable support for integrated infrared receiver
  130. /transceiver made by Fintek. This chip is found on assorted
  131. Jetway motherboards (and of course, possibly others).
  132. To compile this driver as a module, choose M here: the
  133. module will be called fintek-cir.
  134. config IR_GPIO_CIR
  135. tristate "GPIO IR remote control"
  136. depends on (OF && GPIOLIB) || COMPILE_TEST
  137. help
  138. Say Y if you want to use GPIO based IR Receiver.
  139. To compile this driver as a module, choose M here: the module will
  140. be called gpio-ir-recv.
  141. config IR_GPIO_TX
  142. tristate "GPIO IR Bit Banging Transmitter"
  143. depends on LIRC
  144. depends on (OF && GPIOLIB) || COMPILE_TEST
  145. depends on !PREEMPT_RT
  146. help
  147. Say Y if you want to a GPIO based IR transmitter. This is a
  148. bit banging driver.
  149. To compile this driver as a module, choose M here: the module will
  150. be called gpio-ir-tx.
  151. config IR_HIX5HD2
  152. tristate "Hisilicon hix5hd2 IR remote control"
  153. depends on (OF && HAS_IOMEM) || COMPILE_TEST
  154. help
  155. Say Y here if you want to use hisilicon hix5hd2 remote control.
  156. To compile this driver as a module, choose M here: the module will be
  157. called ir-hix5hd2.
  158. If you're not sure, select N here
  159. config IR_IGORPLUGUSB
  160. tristate "IgorPlug-USB IR Receiver"
  161. depends on USB
  162. help
  163. Say Y here if you want to use the IgorPlug-USB IR Receiver by
  164. Igor Cesko. This device is included on the Fit-PC2.
  165. Note that this device can only record bursts of 36 IR pulses and
  166. spaces, which is not enough for the NEC, Sanyo and RC-6 protocol.
  167. To compile this driver as a module, choose M here: the module will
  168. be called igorplugusb.
  169. config IR_IGUANA
  170. tristate "IguanaWorks USB IR Transceiver"
  171. depends on USB
  172. help
  173. Say Y here if you want to use the IguanaWorks USB IR Transceiver.
  174. Both infrared receive and send are supported. If you want to
  175. change the ID or the pin config, use the user space driver from
  176. IguanaWorks.
  177. Only firmware 0x0205 and later is supported.
  178. To compile this driver as a module, choose M here: the module will
  179. be called iguanair.
  180. config IR_IMON
  181. tristate "SoundGraph iMON Receiver and Display"
  182. depends on 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. To compile this driver as a module, choose M here: the
  187. module will be called imon.
  188. config IR_IMON_RAW
  189. tristate "SoundGraph iMON Receiver (early raw IR models)"
  190. depends on USB
  191. help
  192. Say Y here if you want to use a SoundGraph iMON IR Receiver,
  193. early raw models.
  194. To compile this driver as a module, choose M here: the
  195. module will be called imon_raw.
  196. config IR_ITE_CIR
  197. tristate "ITE Tech Inc. IT8712/IT8512 Consumer Infrared Transceiver"
  198. depends on PNP || COMPILE_TEST
  199. depends on HAS_IOPORT
  200. help
  201. Say Y here to enable support for integrated infrared receivers
  202. /transceivers made by ITE Tech Inc. These are found in
  203. several ASUS devices, like the ASUS Digimatrix or the ASUS
  204. EEEBox 1501U.
  205. To compile this driver as a module, choose M here: the
  206. module will be called ite-cir.
  207. config IR_MCEUSB
  208. tristate "Windows Media Center Ed. eHome Infrared Transceiver"
  209. depends on USB
  210. help
  211. Say Y here if you want to use a Windows Media Center Edition
  212. eHome Infrared Transceiver.
  213. To compile this driver as a module, choose M here: the
  214. module will be called mceusb.
  215. config IR_MESON
  216. tristate "Amlogic Meson IR remote receiver"
  217. depends on ARCH_MESON || COMPILE_TEST
  218. select REGMAP_MMIO
  219. help
  220. Say Y if you want to use the IR remote receiver available
  221. on Amlogic Meson SoCs.
  222. To compile this driver as a module, choose M here: the
  223. module will be called meson-ir.
  224. config IR_MESON_TX
  225. tristate "Amlogic Meson IR TX"
  226. depends on ARCH_MESON || COMPILE_TEST
  227. help
  228. Say Y if you want to use the IR transmitter available on
  229. Amlogic Meson SoCs.
  230. To compile this driver as a module, choose M here: the
  231. module will be called meson-ir-tx.
  232. config IR_MTK
  233. tristate "Mediatek IR remote receiver"
  234. depends on ARCH_MEDIATEK || COMPILE_TEST
  235. help
  236. Say Y if you want to use the IR remote receiver available
  237. on Mediatek SoCs.
  238. To compile this driver as a module, choose M here: the
  239. module will be called mtk-cir.
  240. config IR_NUVOTON
  241. tristate "Nuvoton w836x7hg Consumer Infrared Transceiver"
  242. depends on PNP || COMPILE_TEST
  243. depends on HAS_IOPORT
  244. help
  245. Say Y here to enable support for integrated infrared receiver
  246. /transceiver made by Nuvoton (formerly Winbond). This chip is
  247. found in the ASRock ION 330HT, as well as assorted Intel
  248. DP55-series motherboards (and of course, possibly others).
  249. To compile this driver as a module, choose M here: the
  250. module will be called nuvoton-cir.
  251. config IR_PWM_TX
  252. tristate "PWM IR transmitter"
  253. depends on LIRC
  254. depends on PWM
  255. depends on HIGH_RES_TIMERS
  256. depends on OF
  257. help
  258. Say Y if you want to use a PWM based IR transmitter. This is
  259. more power efficient than the bit banging gpio driver.
  260. To compile this driver as a module, choose M here: the module will
  261. be called pwm-ir-tx.
  262. config IR_REDRAT3
  263. tristate "RedRat3 IR Transceiver"
  264. depends on USB
  265. select NEW_LEDS
  266. select LEDS_CLASS
  267. help
  268. Say Y here if you want to use a RedRat3 Infrared Transceiver.
  269. To compile this driver as a module, choose M here: the
  270. module will be called redrat3.
  271. config IR_SERIAL
  272. tristate "Homebrew Serial Port Receiver"
  273. depends on HAS_IOPORT
  274. help
  275. Say Y if you want to use Homebrew Serial Port Receivers and
  276. Transceivers.
  277. To compile this driver as a module, choose M here: the module will
  278. be called serial-ir.
  279. config IR_SERIAL_TRANSMITTER
  280. bool "Serial Port Transmitter"
  281. depends on IR_SERIAL
  282. help
  283. Serial Port Transmitter support
  284. config IR_SPI
  285. tristate "SPI connected IR LED"
  286. depends on SPI && LIRC
  287. depends on OF
  288. help
  289. Say Y if you want to use an IR LED connected through SPI bus.
  290. To compile this driver as a module, choose M here: the module will be
  291. called ir-spi.
  292. config IR_STREAMZAP
  293. tristate "Streamzap PC Remote IR Receiver"
  294. depends on USB
  295. help
  296. Say Y here if you want to use a Streamzap PC Remote
  297. Infrared Receiver.
  298. To compile this driver as a module, choose M here: the
  299. module will be called streamzap.
  300. config IR_SUNXI
  301. tristate "SUNXI IR remote control"
  302. depends on ARCH_SUNXI || COMPILE_TEST
  303. help
  304. Say Y if you want to use sunXi internal IR Controller
  305. To compile this driver as a module, choose M here: the module will
  306. be called sunxi-ir.
  307. config IR_TOY
  308. tristate "Infrared Toy and IR Droid"
  309. depends on USB
  310. help
  311. Say Y here if you want to use the Infrared Toy or IR Droid, USB
  312. versions.
  313. To compile this driver as a module, choose M here: the module will be
  314. called ir_toy.
  315. config IR_TTUSBIR
  316. tristate "TechnoTrend USB IR Receiver"
  317. depends on USB
  318. select NEW_LEDS
  319. select LEDS_CLASS
  320. help
  321. Say Y here if you want to use the TechnoTrend USB IR Receiver. The
  322. driver can control the led.
  323. To compile this driver as a module, choose M here: the module will
  324. be called ttusbir.
  325. config IR_WINBOND_CIR
  326. tristate "Winbond IR remote control"
  327. depends on (X86 && PNP) || COMPILE_TEST
  328. depends on HAS_IOPORT
  329. select NEW_LEDS
  330. select LEDS_CLASS
  331. select BITREVERSE
  332. help
  333. Say Y here if you want to use the IR remote functionality found
  334. in some Winbond SuperI/O chips. Currently only the WPCD376I
  335. chip is supported (included in some Intel Media series
  336. motherboards).
  337. To compile this driver as a module, choose M here: the module will
  338. be called winbond_cir.
  339. config RC_ATI_REMOTE
  340. tristate "ATI / X10 based USB RF remote controls"
  341. depends on USB
  342. help
  343. Say Y here if you want to use an X10 based USB remote control.
  344. These are RF remotes with USB receivers.
  345. Such devices include the ATI remote that comes with many of ATI's
  346. All-In-Wonder video cards, the X10 "Lola" remote, NVIDIA RF remote,
  347. Medion RF remote, and SnapStream FireFly remote.
  348. This driver provides mouse pointer, left and right mouse buttons,
  349. and maps all the other remote buttons to keypress events.
  350. To compile this driver as a module, choose M here: the module will be
  351. called ati_remote.
  352. config RC_LOOPBACK
  353. tristate "Remote Control Loopback Driver"
  354. help
  355. Say Y here if you want support for the remote control loopback
  356. driver which allows TX data to be sent back as RX data.
  357. This is mostly useful for debugging purposes.
  358. If you're not sure, select N here.
  359. To compile this driver as a module, choose M here: the module will
  360. be called rc_loopback.
  361. config RC_ST
  362. tristate "ST remote control receiver"
  363. depends on ARCH_STI || COMPILE_TEST
  364. help
  365. Say Y here if you want support for ST remote control driver
  366. which allows both IR and UHF RX.
  367. The driver passes raw pulse and space information to the LIRC decoder.
  368. If you're not sure, select N here.
  369. config RC_XBOX_DVD
  370. tristate "Xbox DVD Movie Playback Kit"
  371. depends on USB
  372. help
  373. Say Y here if you want to use the Xbox DVD Movie Playback Kit.
  374. These are IR remotes with USB receivers for the Original Xbox (2001).
  375. To compile this driver as a module, choose M here: the module will be
  376. called xbox_remote.
  377. source "drivers/media/rc/img-ir/Kconfig"
  378. endif #RC_DEVICES
  379. endif #RC_CORE