Kconfig 15 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510
  1. menuconfig RC_CORE
  2. tristate "Remote Controller support"
  3. depends on INPUT
  4. ---help---
  5. Enable support for Remote Controllers on Linux. This is
  6. needed in order to support several video capture adapters,
  7. standalone IR receivers/transmitters, and RF receivers.
  8. Enable this option if you have a video capture board even
  9. if you don't need IR, as otherwise, you may not be able to
  10. compile the driver for your adapter.
  11. Say Y when you have a TV or an IR device.
  12. if RC_CORE
  13. source "drivers/media/rc/keymaps/Kconfig"
  14. config LIRC
  15. bool "LIRC user interface"
  16. depends on RC_CORE
  17. ---help---
  18. Enable this option to enable the Linux Infrared Remote
  19. Control user interface (e.g. /dev/lirc*). This interface
  20. passes raw IR to and from userspace, which is needed for
  21. IR transmitting (aka "blasting") and for the lirc daemon.
  22. config BPF_LIRC_MODE2
  23. bool "Support for eBPF programs attached to lirc devices"
  24. depends on BPF_SYSCALL
  25. depends on RC_CORE=y
  26. depends on LIRC
  27. help
  28. Allow attaching eBPF programs to a lirc device using the bpf(2)
  29. syscall command BPF_PROG_ATTACH. This is supported for raw IR
  30. receivers.
  31. These eBPF programs can be used to decode IR into scancodes, for
  32. IR protocols not supported by the kernel decoders.
  33. menuconfig RC_DECODERS
  34. bool "Remote controller decoders"
  35. depends on RC_CORE
  36. if RC_DECODERS
  37. config IR_NEC_DECODER
  38. tristate "Enable IR raw decoder for the NEC protocol"
  39. depends on RC_CORE
  40. select BITREVERSE
  41. ---help---
  42. Enable this option if you have IR with NEC protocol, and
  43. if the IR is decoded in software
  44. config IR_RC5_DECODER
  45. tristate "Enable IR raw decoder for the RC-5 protocol"
  46. depends on RC_CORE
  47. select BITREVERSE
  48. ---help---
  49. Enable this option if you have IR with RC-5 protocol, and
  50. if the IR is decoded in software
  51. config IR_RC6_DECODER
  52. tristate "Enable IR raw decoder for the RC6 protocol"
  53. depends on RC_CORE
  54. select BITREVERSE
  55. ---help---
  56. Enable this option if you have an infrared remote control which
  57. uses the RC6 protocol, and you need software decoding support.
  58. config IR_JVC_DECODER
  59. tristate "Enable IR raw decoder for the JVC protocol"
  60. depends on RC_CORE
  61. select BITREVERSE
  62. ---help---
  63. Enable this option if you have an infrared remote control which
  64. uses the JVC protocol, and you need software decoding support.
  65. config IR_SONY_DECODER
  66. tristate "Enable IR raw decoder for the Sony protocol"
  67. depends on RC_CORE
  68. select BITREVERSE
  69. ---help---
  70. Enable this option if you have an infrared remote control which
  71. uses the Sony protocol, and you need software decoding support.
  72. config IR_SANYO_DECODER
  73. tristate "Enable IR raw decoder for the Sanyo protocol"
  74. depends on RC_CORE
  75. ---help---
  76. Enable this option if you have an infrared remote control which
  77. uses the Sanyo protocol (Sanyo, Aiwa, Chinon remotes),
  78. and you need software decoding support.
  79. config IR_SHARP_DECODER
  80. tristate "Enable IR raw decoder for the Sharp protocol"
  81. depends on RC_CORE
  82. ---help---
  83. Enable this option if you have an infrared remote control which
  84. uses the Sharp protocol (Sharp, Denon), and you need software
  85. decoding support.
  86. config IR_MCE_KBD_DECODER
  87. tristate "Enable IR raw decoder for the MCE keyboard/mouse protocol"
  88. depends on RC_CORE
  89. select BITREVERSE
  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. ---help---
  99. Enable this option if you have IR with XMP protocol, and
  100. if the IR is decoded in software
  101. config IR_IMON_DECODER
  102. tristate "Enable IR raw decoder for the iMON protocol"
  103. depends on RC_CORE
  104. ---help---
  105. Enable this option if you have iMON PAD or Antec Veris infrared
  106. remote control and you would like to use it with a raw IR
  107. receiver, or if you wish to use an encoder to transmit this IR.
  108. endif #RC_DECODERS
  109. menuconfig RC_DEVICES
  110. bool "Remote Controller devices"
  111. depends on RC_CORE
  112. if RC_DEVICES
  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 || COMPILE_TEST
  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_HIX5HD2
  140. tristate "Hisilicon hix5hd2 IR remote control"
  141. depends on RC_CORE
  142. depends on OF || COMPILE_TEST
  143. help
  144. Say Y here if you want to use hisilicon hix5hd2 remote control.
  145. To compile this driver as a module, choose M here: the module will be
  146. called ir-hix5hd2.
  147. If you're not sure, select N here
  148. config IR_IMON
  149. tristate "SoundGraph iMON Receiver and Display"
  150. depends on USB_ARCH_HAS_HCD
  151. depends on RC_CORE
  152. select USB
  153. ---help---
  154. Say Y here if you want to use a SoundGraph iMON (aka Antec Veris)
  155. IR Receiver and/or LCD/VFD/VGA display.
  156. To compile this driver as a module, choose M here: the
  157. module will be called imon.
  158. config IR_IMON_RAW
  159. tristate "SoundGraph iMON Receiver (early raw IR models)"
  160. depends on USB_ARCH_HAS_HCD
  161. depends on RC_CORE
  162. select USB
  163. ---help---
  164. Say Y here if you want to use a SoundGraph iMON IR Receiver,
  165. early raw models.
  166. To compile this driver as a module, choose M here: the
  167. module will be called imon_raw.
  168. config IR_MCEUSB
  169. tristate "Windows Media Center Ed. eHome Infrared Transceiver"
  170. depends on USB_ARCH_HAS_HCD
  171. depends on RC_CORE
  172. select USB
  173. ---help---
  174. Say Y here if you want to use a Windows Media Center Edition
  175. eHome Infrared Transceiver.
  176. To compile this driver as a module, choose M here: the
  177. module will be called mceusb.
  178. config IR_ITE_CIR
  179. tristate "ITE Tech Inc. IT8712/IT8512 Consumer Infrared Transceiver"
  180. depends on PNP || COMPILE_TEST
  181. depends on RC_CORE
  182. ---help---
  183. Say Y here to enable support for integrated infrared receivers
  184. /transceivers made by ITE Tech Inc. These are found in
  185. several ASUS devices, like the ASUS Digimatrix or the ASUS
  186. EEEBox 1501U.
  187. To compile this driver as a module, choose M here: the
  188. module will be called ite-cir.
  189. config IR_FINTEK
  190. tristate "Fintek Consumer Infrared Transceiver"
  191. depends on PNP || COMPILE_TEST
  192. depends on RC_CORE
  193. ---help---
  194. Say Y here to enable support for integrated infrared receiver
  195. /transciever made by Fintek. This chip is found on assorted
  196. Jetway motherboards (and of course, possibly others).
  197. To compile this driver as a module, choose M here: the
  198. module will be called fintek-cir.
  199. config IR_MESON
  200. tristate "Amlogic Meson IR remote receiver"
  201. depends on RC_CORE
  202. depends on ARCH_MESON || COMPILE_TEST
  203. ---help---
  204. Say Y if you want to use the IR remote receiver available
  205. on Amlogic Meson SoCs.
  206. To compile this driver as a module, choose M here: the
  207. module will be called meson-ir.
  208. config IR_MTK
  209. tristate "Mediatek IR remote receiver"
  210. depends on RC_CORE
  211. depends on ARCH_MEDIATEK || COMPILE_TEST
  212. ---help---
  213. Say Y if you want to use the IR remote receiver available
  214. on Mediatek SoCs.
  215. To compile this driver as a module, choose M here: the
  216. module will be called mtk-cir.
  217. config IR_NUVOTON
  218. tristate "Nuvoton w836x7hg Consumer Infrared Transceiver"
  219. depends on PNP || COMPILE_TEST
  220. depends on RC_CORE
  221. ---help---
  222. Say Y here to enable support for integrated infrared receiver
  223. /transciever made by Nuvoton (formerly Winbond). This chip is
  224. found in the ASRock ION 330HT, as well as assorted Intel
  225. DP55-series motherboards (and of course, possibly others).
  226. To compile this driver as a module, choose M here: the
  227. module will be called nuvoton-cir.
  228. config IR_REDRAT3
  229. tristate "RedRat3 IR Transceiver"
  230. depends on USB_ARCH_HAS_HCD
  231. depends on RC_CORE
  232. select NEW_LEDS
  233. select LEDS_CLASS
  234. select USB
  235. ---help---
  236. Say Y here if you want to use a RedRat3 Infrared Transceiver.
  237. To compile this driver as a module, choose M here: the
  238. module will be called redrat3.
  239. config IR_SPI
  240. tristate "SPI connected IR LED"
  241. depends on SPI && LIRC
  242. depends on OF || COMPILE_TEST
  243. ---help---
  244. Say Y if you want to use an IR LED connected through SPI bus.
  245. To compile this driver as a module, choose M here: the module will be
  246. called ir-spi.
  247. config IR_STREAMZAP
  248. tristate "Streamzap PC Remote IR Receiver"
  249. depends on USB_ARCH_HAS_HCD
  250. depends on RC_CORE
  251. select USB
  252. ---help---
  253. Say Y here if you want to use a Streamzap PC Remote
  254. Infrared Receiver.
  255. To compile this driver as a module, choose M here: the
  256. module will be called streamzap.
  257. config IR_WINBOND_CIR
  258. tristate "Winbond IR remote control"
  259. depends on (X86 && PNP) || COMPILE_TEST
  260. depends on RC_CORE
  261. select NEW_LEDS
  262. select LEDS_CLASS
  263. select BITREVERSE
  264. ---help---
  265. Say Y here if you want to use the IR remote functionality found
  266. in some Winbond SuperI/O chips. Currently only the WPCD376I
  267. chip is supported (included in some Intel Media series
  268. motherboards).
  269. To compile this driver as a module, choose M here: the module will
  270. be called winbond_cir.
  271. config IR_IGORPLUGUSB
  272. tristate "IgorPlug-USB IR Receiver"
  273. depends on USB_ARCH_HAS_HCD
  274. depends on RC_CORE
  275. select USB
  276. ---help---
  277. Say Y here if you want to use the IgorPlug-USB IR Receiver by
  278. Igor Cesko. This device is included on the Fit-PC2.
  279. Note that this device can only record bursts of 36 IR pulses and
  280. spaces, which is not enough for the NEC, Sanyo and RC-6 protocol.
  281. To compile this driver as a module, choose M here: the module will
  282. be called igorplugusb.
  283. config IR_IGUANA
  284. tristate "IguanaWorks USB IR Transceiver"
  285. depends on USB_ARCH_HAS_HCD
  286. depends on RC_CORE
  287. select USB
  288. ---help---
  289. Say Y here if you want to use the IguanaWorks USB IR Transceiver.
  290. Both infrared receive and send are supported. If you want to
  291. change the ID or the pin config, use the user space driver from
  292. IguanaWorks.
  293. Only firmware 0x0205 and later is supported.
  294. To compile this driver as a module, choose M here: the module will
  295. be called iguanair.
  296. config IR_TTUSBIR
  297. tristate "TechnoTrend USB IR Receiver"
  298. depends on USB_ARCH_HAS_HCD
  299. depends on RC_CORE
  300. select USB
  301. select NEW_LEDS
  302. select LEDS_CLASS
  303. ---help---
  304. Say Y here if you want to use the TechnoTrend USB IR Receiver. The
  305. driver can control the led.
  306. To compile this driver as a module, choose M here: the module will
  307. be called ttusbir.
  308. config IR_RX51
  309. tristate "Nokia N900 IR transmitter diode"
  310. depends on (OMAP_DM_TIMER && PWM_OMAP_DMTIMER && ARCH_OMAP2PLUS || COMPILE_TEST) && RC_CORE
  311. ---help---
  312. Say Y or M here if you want to enable support for the IR
  313. transmitter diode built in the Nokia N900 (RX51) device.
  314. The driver uses omap DM timers for generating the carrier
  315. wave and pulses.
  316. source "drivers/media/rc/img-ir/Kconfig"
  317. config RC_LOOPBACK
  318. tristate "Remote Control Loopback Driver"
  319. depends on RC_CORE
  320. ---help---
  321. Say Y here if you want support for the remote control loopback
  322. driver which allows TX data to be sent back as RX data.
  323. This is mostly useful for debugging purposes.
  324. If you're not sure, select N here.
  325. To compile this driver as a module, choose M here: the module will
  326. be called rc_loopback.
  327. config IR_GPIO_CIR
  328. tristate "GPIO IR remote control"
  329. depends on RC_CORE
  330. depends on (OF && GPIOLIB) || COMPILE_TEST
  331. ---help---
  332. Say Y if you want to use GPIO based IR Receiver.
  333. To compile this driver as a module, choose M here: the module will
  334. be called gpio-ir-recv.
  335. config IR_GPIO_TX
  336. tristate "GPIO IR Bit Banging Transmitter"
  337. depends on RC_CORE
  338. depends on LIRC
  339. depends on (OF && GPIOLIB) || COMPILE_TEST
  340. ---help---
  341. Say Y if you want to a GPIO based IR transmitter. This is a
  342. bit banging driver.
  343. To compile this driver as a module, choose M here: the module will
  344. be called gpio-ir-tx.
  345. config IR_PWM_TX
  346. tristate "PWM IR transmitter"
  347. depends on RC_CORE
  348. depends on LIRC
  349. depends on PWM
  350. depends on OF || COMPILE_TEST
  351. ---help---
  352. Say Y if you want to use a PWM based IR transmitter. This is
  353. more power efficient than the bit banging gpio driver.
  354. To compile this driver as a module, choose M here: the module will
  355. be called pwm-ir-tx.
  356. config RC_ST
  357. tristate "ST remote control receiver"
  358. depends on RC_CORE
  359. depends on ARCH_STI || COMPILE_TEST
  360. ---help---
  361. Say Y here if you want support for ST remote control driver
  362. which allows both IR and UHF RX.
  363. The driver passes raw pulse and space information to the LIRC decoder.
  364. If you're not sure, select N here.
  365. config IR_SUNXI
  366. tristate "SUNXI IR remote control"
  367. depends on RC_CORE
  368. depends on ARCH_SUNXI || COMPILE_TEST
  369. ---help---
  370. Say Y if you want to use sunXi internal IR Controller
  371. To compile this driver as a module, choose M here: the module will
  372. be called sunxi-ir.
  373. config IR_SERIAL
  374. tristate "Homebrew Serial Port Receiver"
  375. depends on RC_CORE
  376. ---help---
  377. Say Y if you want to use Homebrew Serial Port Receivers and
  378. Transceivers.
  379. To compile this driver as a module, choose M here: the module will
  380. be called serial-ir.
  381. config IR_SERIAL_TRANSMITTER
  382. bool "Serial Port Transmitter"
  383. depends on IR_SERIAL
  384. ---help---
  385. Serial Port Transmitter support
  386. config IR_SIR
  387. tristate "Built-in SIR IrDA port"
  388. depends on RC_CORE
  389. ---help---
  390. Say Y if you want to use a IrDA SIR port Transceivers.
  391. To compile this driver as a module, choose M here: the module will
  392. be called sir-ir.
  393. config IR_TANGO
  394. tristate "Sigma Designs SMP86xx IR decoder"
  395. depends on RC_CORE
  396. depends on ARCH_TANGO || COMPILE_TEST
  397. ---help---
  398. Adds support for the HW IR decoder embedded on Sigma Designs
  399. Tango-based systems (SMP86xx, SMP87xx).
  400. The HW decoder supports NEC, RC-5, RC-6 IR protocols.
  401. When compiled as a module, look for tango-ir.
  402. config IR_ZX
  403. tristate "ZTE ZX IR remote control"
  404. depends on RC_CORE
  405. depends on ARCH_ZX || COMPILE_TEST
  406. ---help---
  407. Say Y if you want to use the IR remote control available
  408. on ZTE ZX family SoCs.
  409. To compile this driver as a module, choose M here: the
  410. module will be called zx-irdec.
  411. endif #RC_DEVICES
  412. endif #RC_CORE