Kconfig 8.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. #
  3. # PCCARD (PCMCIA/CardBus) bus subsystem configuration
  4. #
  5. menuconfig PCCARD
  6. tristate "PCCard (PCMCIA/CardBus) support"
  7. depends on !UML
  8. help
  9. Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
  10. computer. These are credit-card size devices such as network cards,
  11. modems or hard drives often used with laptops computers. There are
  12. actually two varieties of these cards: 16 bit PCMCIA and 32 bit
  13. CardBus cards.
  14. To compile this driver as modules, choose M here: the
  15. module will be called pcmcia_core.
  16. if PCCARD
  17. config PCMCIA
  18. tristate "16-bit PCMCIA support"
  19. select CRC32
  20. default y
  21. help
  22. This option enables support for 16-bit PCMCIA cards. Most older
  23. PC-cards are such 16-bit PCMCIA cards, so unless you know you're
  24. only using 32-bit CardBus cards, say Y or M here.
  25. To use 16-bit PCMCIA cards, you will need supporting software in
  26. most cases. (see the file <file:Documentation/Changes> for
  27. location and details).
  28. To compile this driver as modules, choose M here: the
  29. module will be called pcmcia.
  30. If unsure, say Y.
  31. config PCMCIA_LOAD_CIS
  32. bool "Load CIS updates from userspace"
  33. depends on PCMCIA
  34. select FW_LOADER
  35. default y
  36. help
  37. Some PCMCIA cards require an updated Card Information Structure (CIS)
  38. to be loaded from userspace to work correctly. If you say Y here,
  39. and your userspace is arranged correctly, this will be loaded
  40. automatically using the in-kernel firmware loader and the hotplug
  41. subsystem, instead of relying on cardmgr from pcmcia-cs to do so.
  42. If unsure, say Y.
  43. config CARDBUS
  44. bool "32-bit CardBus support"
  45. depends on PCI
  46. default y
  47. help
  48. CardBus is a bus mastering architecture for PC-cards, which allows
  49. for 32 bit PC-cards (the original PCMCIA standard specifies only
  50. a 16 bit wide bus). Many newer PC-cards are actually CardBus cards.
  51. To use 32 bit PC-cards, you also need a CardBus compatible host
  52. bridge. Virtually all modern PCMCIA bridges do this, and most of
  53. them are "yenta-compatible", so say Y or M there, too.
  54. If unsure, say Y.
  55. config PCMCIA_MAX1600
  56. tristate
  57. comment "PC-card bridges"
  58. config YENTA
  59. tristate "CardBus yenta-compatible bridge support"
  60. depends on PCI
  61. select CARDBUS if !EXPERT
  62. select PCCARD_NONSTATIC if PCMCIA != n
  63. help
  64. This option enables support for CardBus host bridges. Virtually
  65. all modern PCMCIA bridges are CardBus compatible. A "bridge" is
  66. the hardware inside your computer that PCMCIA cards are plugged
  67. into.
  68. To compile this driver as modules, choose M here: the
  69. module will be called yenta_socket.
  70. If unsure, say Y.
  71. config YENTA_O2
  72. default y
  73. bool "Special initialization for O2Micro bridges" if EXPERT
  74. depends on YENTA
  75. config YENTA_RICOH
  76. default y
  77. bool "Special initialization for Ricoh bridges" if EXPERT
  78. depends on YENTA
  79. config YENTA_TI
  80. default y
  81. bool "Special initialization for TI and EnE bridges" if EXPERT
  82. depends on YENTA
  83. config YENTA_ENE_TUNE
  84. default y
  85. bool "Auto-tune EnE bridges for CB cards" if EXPERT
  86. depends on YENTA_TI && CARDBUS
  87. config YENTA_TOSHIBA
  88. default y
  89. bool "Special initialization for Toshiba ToPIC bridges" if EXPERT
  90. depends on YENTA
  91. config PD6729
  92. tristate "Cirrus PD6729 compatible bridge support"
  93. depends on PCMCIA && PCI
  94. select PCCARD_NONSTATIC
  95. help
  96. This provides support for the Cirrus PD6729 PCI-to-PCMCIA bridge
  97. device, found in some older laptops and PCMCIA card readers.
  98. config I82092
  99. tristate "i82092 compatible bridge support"
  100. depends on PCMCIA && PCI
  101. select PCCARD_NONSTATIC
  102. help
  103. This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device,
  104. found in some older laptops and more commonly in evaluation boards for the
  105. chip.
  106. config I82365
  107. tristate "i82365 compatible bridge support"
  108. depends on PCMCIA && ISA
  109. select PCCARD_NONSTATIC
  110. help
  111. Say Y here to include support for ISA-bus PCMCIA host bridges that
  112. are register compatible with the Intel i82365. These are found on
  113. older laptops and ISA-bus card readers for desktop systems. A
  114. "bridge" is the hardware inside your computer that PCMCIA cards are
  115. plugged into. If unsure, say N.
  116. config TCIC
  117. tristate "Databook TCIC host bridge support"
  118. depends on PCMCIA && ISA
  119. select PCCARD_NONSTATIC
  120. help
  121. Say Y here to include support for the Databook TCIC family of PCMCIA
  122. host bridges. These are only found on a handful of old systems.
  123. "Bridge" is the name used for the hardware inside your computer that
  124. PCMCIA cards are plugged into. If unsure, say N.
  125. config PCMCIA_ALCHEMY_DEVBOARD
  126. tristate "Alchemy Db/Pb1xxx PCMCIA socket services"
  127. depends on MIPS_ALCHEMY && PCMCIA
  128. help
  129. Enable this driver of you want PCMCIA support on your Alchemy
  130. Db1000, Db/Pb1100, Db/Pb1500, Db/Pb1550, Db/Pb1200, DB1300
  131. board. NOT suitable for the PB1000!
  132. This driver is also available as a module called db1xxx_ss.ko
  133. config PCMCIA_XXS1500
  134. tristate "MyCable XXS1500 PCMCIA socket support"
  135. depends on PCMCIA && MIPS_XXS1500
  136. help
  137. Support for the PCMCIA/CF socket interface on MyCable XXS1500
  138. systems.
  139. This driver is also available as a module called xxs1500_ss.ko
  140. config PCMCIA_BCM63XX
  141. tristate "bcm63xx pcmcia support"
  142. depends on BCM63XX && PCMCIA
  143. config PCMCIA_SOC_COMMON
  144. tristate
  145. config PCMCIA_SA11XX_BASE
  146. tristate
  147. config PCMCIA_SA1100
  148. tristate "SA1100 support"
  149. depends on ARM && ARCH_SA1100 && PCMCIA
  150. select PCMCIA_SOC_COMMON
  151. select PCMCIA_SA11XX_BASE
  152. help
  153. Say Y here to include support for SA11x0-based PCMCIA or CF
  154. sockets, found on HP iPAQs, Yopy, and other StrongARM(R)/
  155. Xscale(R) embedded machines.
  156. This driver is also available as a module called sa1100_cs.
  157. config PCMCIA_SA1111
  158. tristate "SA1111 support"
  159. depends on ARM && SA1111 && PCMCIA
  160. select PCMCIA_SOC_COMMON
  161. select PCMCIA_SA11XX_BASE if ARCH_SA1100
  162. select PCMCIA_PXA2XX if ARCH_LUBBOCK && SA1111
  163. select PCMCIA_MAX1600 if ASSABET_NEPONSET
  164. select PCMCIA_MAX1600 if ARCH_LUBBOCK && SA1111
  165. help
  166. Say Y here to include support for SA1111-based PCMCIA or CF
  167. sockets, found on the Jornada 720, Graphicsmaster and other
  168. StrongARM(R)/Xscale(R) embedded machines.
  169. This driver is also available as a module called sa1111_cs.
  170. config PCMCIA_PXA2XX
  171. tristate "PXA2xx support"
  172. depends on ARM && ARCH_PXA && PCMCIA
  173. depends on (ARCH_LUBBOCK || MACH_MAINSTONE || PXA_SHARPSL \
  174. || MACH_ARMCORE || ARCH_PXA_PALM || TRIZEPS_PCMCIA \
  175. || ARCOM_PCMCIA || ARCH_PXA_ESERIES || MACH_STARGATE2 \
  176. || MACH_VPAC270 || MACH_BALLOON3 || MACH_COLIBRI \
  177. || MACH_COLIBRI320 || MACH_H4700)
  178. select PCMCIA_SOC_COMMON
  179. select PCMCIA_MAX1600 if MACH_MAINSTONE
  180. help
  181. Say Y here to include support for the PXA2xx PCMCIA controller
  182. config PCMCIA_DEBUG
  183. bool "Enable debugging"
  184. depends on (PCMCIA_SA1111 || PCMCIA_SA1100 || PCMCIA_PXA2XX)
  185. help
  186. Say Y here to enable debugging for the SoC PCMCIA layer.
  187. You will need to choose the debugging level either via the
  188. kernel command line, or module options depending whether
  189. you build the drivers as modules.
  190. The kernel command line options are:
  191. sa11xx_core.pc_debug=N
  192. pxa2xx_core.pc_debug=N
  193. The module option is called pc_debug=N
  194. In all the above examples, N is the debugging verbosity
  195. level.
  196. config PCMCIA_PROBE
  197. bool
  198. default y if ISA && !ARCH_SA1100 && !PARISC
  199. config PCMCIA_VRC4171
  200. tristate "NEC VRC4171 Card Controllers support"
  201. depends on CPU_VR41XX && ISA && PCMCIA
  202. config PCMCIA_VRC4173
  203. tristate "NEC VRC4173 CARDU support"
  204. depends on CPU_VR41XX && PCI && PCMCIA
  205. config OMAP_CF
  206. tristate "OMAP CompactFlash Controller"
  207. depends on PCMCIA && ARCH_OMAP16XX
  208. help
  209. Say Y here to support the CompactFlash controller on OMAP.
  210. Note that this doesn't support "True IDE" mode.
  211. config AT91_CF
  212. tristate "AT91 CompactFlash Controller"
  213. depends on PCI
  214. depends on PCMCIA && ARCH_AT91
  215. help
  216. Say Y here to support the CompactFlash controller on AT91 chips.
  217. Or choose M to compile the driver as a module named "at91_cf".
  218. config ELECTRA_CF
  219. tristate "Electra CompactFlash Controller"
  220. depends on PCMCIA && PPC_PASEMI
  221. help
  222. Say Y here to support the CompactFlash controller on the
  223. PA Semi Electra eval board.
  224. config PCCARD_NONSTATIC
  225. bool
  226. config PCCARD_IODYN
  227. bool
  228. endif # PCCARD