Kconfig 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391
  1. menu "Infrared-port device drivers"
  2. depends on IRDA!=n
  3. comment "SIR device drivers"
  4. config IRTTY_SIR
  5. tristate "IrTTY (uses Linux serial driver)"
  6. depends on IRDA
  7. help
  8. Say Y here if you want to build support for the IrTTY line
  9. discipline. To compile it as a module, choose M here: the module
  10. will be called irtty-sir. IrTTY makes it possible to use Linux's
  11. own serial driver for all IrDA ports that are 16550 compatible.
  12. Most IrDA chips are 16550 compatible so you should probably say Y
  13. to this option. Using IrTTY will however limit the speed of the
  14. connection to 115200 bps (IrDA SIR mode).
  15. If unsure, say Y.
  16. config BFIN_SIR
  17. tristate "Blackfin SIR on UART"
  18. depends on BLACKFIN && IRDA
  19. default n
  20. help
  21. Say Y here if your want to enable SIR function on Blackfin UART
  22. devices.
  23. To activate this driver you can start irattach like:
  24. "irattach irda0 -s"
  25. Saying M, it will be built as a module named bfin_sir.
  26. Note that you need to turn off one of the serial drivers for SIR
  27. to use that UART.
  28. config BFIN_SIR0
  29. bool "Blackfin SIR on UART0"
  30. depends on BFIN_SIR && !SERIAL_BFIN_UART0
  31. config BFIN_SIR1
  32. bool "Blackfin SIR on UART1"
  33. depends on BFIN_SIR && !SERIAL_BFIN_UART1 && (!BF531 && !BF532 && !BF533 && !BF561)
  34. config BFIN_SIR2
  35. bool "Blackfin SIR on UART2"
  36. depends on BFIN_SIR && !SERIAL_BFIN_UART2 && (BF54x || BF538 || BF539)
  37. config BFIN_SIR3
  38. bool "Blackfin SIR on UART3"
  39. depends on BFIN_SIR && !SERIAL_BFIN_UART3 && (BF54x)
  40. choice
  41. prompt "SIR Mode"
  42. depends on BFIN_SIR
  43. default SIR_BFIN_DMA
  44. config SIR_BFIN_DMA
  45. bool "DMA mode"
  46. depends on !DMA_UNCACHED_NONE
  47. config SIR_BFIN_PIO
  48. bool "PIO mode"
  49. endchoice
  50. comment "Dongle support"
  51. config DONGLE
  52. bool "Serial dongle support"
  53. depends on IRTTY_SIR
  54. help
  55. Say Y here if you have an infrared device that connects to your
  56. computer's serial port. These devices are called dongles. Then say Y
  57. or M to the driver for your particular dongle below.
  58. Note that the answer to this question won't directly affect the
  59. kernel: saying N will just cause the configurator to skip all
  60. the questions about serial dongles.
  61. config ESI_DONGLE
  62. tristate "ESI JetEye PC dongle"
  63. depends on IRTTY_SIR && DONGLE && IRDA
  64. help
  65. Say Y here if you want to build support for the Extended Systems
  66. JetEye PC dongle. To compile it as a module, choose M here. The ESI
  67. dongle attaches to the normal 9-pin serial port connector, and can
  68. currently only be used by IrTTY. To activate support for ESI
  69. dongles you will have to start irattach like this:
  70. "irattach -d esi".
  71. config ACTISYS_DONGLE
  72. tristate "ACTiSYS IR-220L and IR220L+ dongle"
  73. depends on IRTTY_SIR && DONGLE && IRDA
  74. help
  75. Say Y here if you want to build support for the ACTiSYS IR-220L and
  76. IR220L+ dongles. To compile it as a module, choose M here. The
  77. ACTiSYS dongles attaches to the normal 9-pin serial port connector,
  78. and can currently only be used by IrTTY. To activate support for
  79. ACTiSYS dongles you will have to start irattach like this:
  80. "irattach -d actisys" or "irattach -d actisys+".
  81. config TEKRAM_DONGLE
  82. tristate "Tekram IrMate 210B dongle"
  83. depends on IRTTY_SIR && DONGLE && IRDA
  84. help
  85. Say Y here if you want to build support for the Tekram IrMate 210B
  86. dongle. To compile it as a module, choose M here. The Tekram dongle
  87. attaches to the normal 9-pin serial port connector, and can
  88. currently only be used by IrTTY. To activate support for Tekram
  89. dongles you will have to start irattach like this:
  90. "irattach -d tekram".
  91. config TOIM3232_DONGLE
  92. tristate "TOIM3232 IrDa dongle"
  93. depends on IRTTY_SIR && DONGLE && IRDA
  94. help
  95. Say Y here if you want to build support for the Vishay/Temic
  96. TOIM3232 and TOIM4232 based dongles.
  97. To compile it as a module, choose M here.
  98. config LITELINK_DONGLE
  99. tristate "Parallax LiteLink dongle"
  100. depends on IRTTY_SIR && DONGLE && IRDA
  101. help
  102. Say Y here if you want to build support for the Parallax Litelink
  103. dongle. To compile it as a module, choose M here. The Parallax
  104. dongle attaches to the normal 9-pin serial port connector, and can
  105. currently only be used by IrTTY. To activate support for Parallax
  106. dongles you will have to start irattach like this:
  107. "irattach -d litelink".
  108. config MA600_DONGLE
  109. tristate "Mobile Action MA600 dongle"
  110. depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
  111. help
  112. Say Y here if you want to build support for the Mobile Action MA600
  113. dongle. To compile it as a module, choose M here. The MA600 dongle
  114. attaches to the normal 9-pin serial port connector, and can
  115. currently only be used by IrTTY. The driver should also support
  116. the MA620 USB version of the dongle, if the integrated USB-to-RS232
  117. converter is supported by usbserial. To activate support for
  118. MA600 dongle you will have to start irattach like this:
  119. "irattach -d ma600".
  120. config GIRBIL_DONGLE
  121. tristate "Greenwich GIrBIL dongle"
  122. depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
  123. help
  124. Say Y here if you want to build support for the Greenwich GIrBIL
  125. dongle. If you want to compile it as a module, choose M here.
  126. The Greenwich dongle attaches to the normal 9-pin serial port
  127. connector, and can currently only be used by IrTTY. To activate
  128. support for Greenwich dongles you will have to start irattach
  129. like this: "irattach -d girbil".
  130. config MCP2120_DONGLE
  131. tristate "Microchip MCP2120"
  132. depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
  133. help
  134. Say Y here if you want to build support for the Microchip MCP2120
  135. dongle. If you want to compile it as a module, choose M here.
  136. The MCP2120 dongle attaches to the normal 9-pin serial port
  137. connector, and can currently only be used by IrTTY. To activate
  138. support for MCP2120 dongles you will have to start irattach
  139. like this: "irattach -d mcp2120".
  140. You must build this dongle yourself. For more information see:
  141. <http://www.eyetap.org/~tangf/irda_sir_linux.html>
  142. config OLD_BELKIN_DONGLE
  143. tristate "Old Belkin dongle"
  144. depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
  145. help
  146. Say Y here if you want to build support for the Adaptec Airport 1000
  147. and 2000 dongles. If you want to compile it as a module, choose
  148. M here. Some information is contained in the comments
  149. at the top of <file:drivers/net/irda/old_belkin.c>.
  150. config ACT200L_DONGLE
  151. tristate "ACTiSYS IR-200L dongle"
  152. depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
  153. help
  154. Say Y here if you want to build support for the ACTiSYS IR-200L
  155. dongle. If you want to compile it as a module, choose M here.
  156. The ACTiSYS IR-200L dongle attaches to the normal 9-pin serial
  157. port connector, and can currently only be used by IrTTY.
  158. To activate support for ACTiSYS IR-200L dongle you will have to
  159. start irattach like this: "irattach -d act200l".
  160. config KINGSUN_DONGLE
  161. tristate "KingSun/DonShine DS-620 IrDA-USB dongle"
  162. depends on IRDA && USB && EXPERIMENTAL
  163. help
  164. Say Y or M here if you want to build support for the KingSun/DonShine
  165. DS-620 IrDA-USB bridge device driver.
  166. This USB bridge does not conform to the IrDA-USB device class
  167. specification, and therefore needs its own specific driver. This
  168. dongle supports SIR speed only (9600 bps).
  169. To compile it as a module, choose M here: the module will be called
  170. kingsun-sir.
  171. config EP7211_DONGLE
  172. tristate "EP7211 I/R support"
  173. depends on IRTTY_SIR && ARCH_EP7211 && IRDA && EXPERIMENTAL
  174. help
  175. Say Y here if you want to build support for the Cirrus logic
  176. EP7211 chipset's infrared module.
  177. config KSDAZZLE_DONGLE
  178. tristate "KingSun Dazzle IrDA-USB dongle (EXPERIMENTAL)"
  179. depends on IRDA && USB && EXPERIMENTAL
  180. help
  181. Say Y or M here if you want to build support for the KingSun Dazzle
  182. IrDA-USB bridge device driver.
  183. This USB bridge does not conform to the IrDA-USB device class
  184. specification, and therefore needs its own specific driver. This
  185. dongle supports SIR speeds only (9600 through 115200 bps).
  186. To compile it as a module, choose M here: the module will be called
  187. ksdazzle-sir.
  188. config KS959_DONGLE
  189. tristate "KingSun KS-959 IrDA-USB dongle (EXPERIMENTAL)"
  190. depends on IRDA && USB && EXPERIMENTAL
  191. help
  192. Say Y or M here if you want to build support for the KingSun KS-959
  193. IrDA-USB bridge device driver.
  194. This USB bridge does not conform to the IrDA-USB device class
  195. specification, and therefore needs its own specific driver. This
  196. dongle supports SIR speeds only (9600 through 57600 bps).
  197. To compile it as a module, choose M here: the module will be called
  198. ks959-sir.
  199. comment "FIR device drivers"
  200. config USB_IRDA
  201. tristate "IrDA USB dongles"
  202. depends on IRDA && USB
  203. select FW_LOADER
  204. ---help---
  205. Say Y here if you want to build support for the USB IrDA FIR Dongle
  206. device driver. To compile it as a module, choose M here: the module
  207. will be called irda-usb. IrDA-USB support the various IrDA USB
  208. dongles available and most of their peculiarities. Those dongles
  209. plug in the USB port of your computer, are plug and play, and
  210. support SIR and FIR (4Mbps) speeds. On the other hand, those
  211. dongles tend to be less efficient than a FIR chipset.
  212. Please note that the driver is still experimental. And of course,
  213. you will need both USB and IrDA support in your kernel...
  214. config SIGMATEL_FIR
  215. tristate "SigmaTel STIr4200 bridge (EXPERIMENTAL)"
  216. depends on IRDA && USB && EXPERIMENTAL
  217. select CRC32
  218. ---help---
  219. Say Y here if you want to build support for the SigmaTel STIr4200
  220. USB IrDA FIR bridge device driver.
  221. USB bridge based on the SigmaTel STIr4200 don't conform to the
  222. IrDA-USB device class specification, and therefore need their
  223. own specific driver. Those dongles support SIR and FIR (4Mbps)
  224. speeds.
  225. To compile it as a module, choose M here: the module will be called
  226. stir4200.
  227. config NSC_FIR
  228. tristate "NSC PC87108/PC87338"
  229. depends on IRDA && ISA_DMA_API
  230. help
  231. Say Y here if you want to build support for the NSC PC87108 and
  232. PC87338 IrDA chipsets. This driver supports SIR,
  233. MIR and FIR (4Mbps) speeds.
  234. To compile it as a module, choose M here: the module will be called
  235. nsc-ircc.
  236. config WINBOND_FIR
  237. tristate "Winbond W83977AF (IR)"
  238. depends on IRDA && ISA_DMA_API
  239. help
  240. Say Y here if you want to build IrDA support for the Winbond
  241. W83977AF super-io chipset. This driver should be used for the IrDA
  242. chipset in the Corel NetWinder. The driver supports SIR, MIR and
  243. FIR (4Mbps) speeds.
  244. To compile it as a module, choose M here: the module will be called
  245. w83977af_ir.
  246. config TOSHIBA_FIR
  247. tristate "Toshiba Type-O IR Port"
  248. depends on IRDA && PCI && !64BIT && VIRT_TO_BUS
  249. help
  250. Say Y here if you want to build support for the Toshiba Type-O IR
  251. and Donau oboe chipsets. These chipsets are used by the Toshiba
  252. Libretto 100/110CT, Tecra 8100, Portege 7020 and many more laptops.
  253. To compile it as a module, choose M here: the module will be called
  254. donauboe.
  255. config AU1000_FIR
  256. tristate "Alchemy Au1000 SIR/FIR"
  257. depends on SOC_AU1000 && IRDA
  258. config SMC_IRCC_FIR
  259. tristate "SMSC IrCC (EXPERIMENTAL)"
  260. depends on EXPERIMENTAL && IRDA && ISA_DMA_API
  261. help
  262. Say Y here if you want to build support for the SMC Infrared
  263. Communications Controller. It is used in a wide variety of
  264. laptops (Fujitsu, Sony, Compaq and some Toshiba).
  265. To compile it as a module, choose M here: the module will be called
  266. smsc-ircc2.o.
  267. config ALI_FIR
  268. tristate "ALi M5123 FIR (EXPERIMENTAL)"
  269. depends on EXPERIMENTAL && IRDA && ISA_DMA_API
  270. help
  271. Say Y here if you want to build support for the ALi M5123 FIR
  272. Controller. The ALi M5123 FIR Controller is embedded in ALi M1543C,
  273. M1535, M1535D, M1535+, M1535D South Bridge. This driver supports
  274. SIR, MIR and FIR (4Mbps) speeds.
  275. To compile it as a module, choose M here: the module will be called
  276. ali-ircc.
  277. config VLSI_FIR
  278. tristate "VLSI 82C147 SIR/MIR/FIR (EXPERIMENTAL)"
  279. depends on EXPERIMENTAL && IRDA && PCI
  280. help
  281. Say Y here if you want to build support for the VLSI 82C147
  282. PCI-IrDA Controller. This controller is used by the HP OmniBook 800
  283. and 5500 notebooks. The driver provides support for SIR, MIR and
  284. FIR (4Mbps) speeds.
  285. To compile it as a module, choose M here: the module will be called
  286. vlsi_ir.
  287. config SA1100_FIR
  288. tristate "SA1100 Internal IR"
  289. depends on ARCH_SA1100 && IRDA
  290. config VIA_FIR
  291. tristate "VIA VT8231/VT1211 SIR/MIR/FIR"
  292. depends on IRDA && ISA_DMA_API
  293. help
  294. Say Y here if you want to build support for the VIA VT8231
  295. and VIA VT1211 IrDA controllers, found on the motherboards using
  296. those VIA chipsets. To use this controller, you will need
  297. to plug a specific 5 pins FIR IrDA dongle in the specific
  298. motherboard connector. The driver provides support for SIR, MIR
  299. and FIR (4Mbps) speeds.
  300. You will need to specify the 'dongle_id' module parameter to
  301. indicate the FIR dongle attached to the controller.
  302. To compile it as a module, choose M here: the module will be called
  303. via-ircc.
  304. config PXA_FICP
  305. tristate "Intel PXA2xx Internal FICP"
  306. depends on ARCH_PXA && IRDA
  307. help
  308. Say Y or M here if you want to build support for the PXA2xx
  309. built-in IRDA interface which can support both SIR and FIR.
  310. This driver relies on platform specific helper routines so
  311. available capabilities may vary from one PXA2xx target to
  312. another.
  313. config MCS_FIR
  314. tristate "MosChip MCS7780 IrDA-USB dongle"
  315. depends on IRDA && USB && EXPERIMENTAL
  316. select CRC32
  317. help
  318. Say Y or M here if you want to build support for the MosChip
  319. MCS7780 IrDA-USB bridge device driver.
  320. USB bridge based on the MosChip MCS7780 don't conform to the
  321. IrDA-USB device class specification, and therefore need their
  322. own specific driver. Those dongles support SIR and FIR (4Mbps)
  323. speeds.
  324. To compile it as a module, choose M here: the module will be called
  325. mcs7780.
  326. endmenu