1 # SPDX-License-Identifier: GPL-2.0-only
3 # PCCARD (PCMCIA/CardBus) bus subsystem configuration
7 tristate "PCCard (PCMCIA/CardBus) support"
10 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
11 computer. These are credit-card size devices such as network cards,
12 modems or hard drives often used with laptops computers. There are
13 actually two varieties of these cards: 16 bit PCMCIA and 32 bit
16 To compile this driver as modules, choose M here: the
17 module will be called pcmcia_core.
22 tristate "16-bit PCMCIA support"
26 This option enables support for 16-bit PCMCIA cards. Most older
27 PC-cards are such 16-bit PCMCIA cards, so unless you know you're
28 only using 32-bit CardBus cards, say Y or M here.
30 To use 16-bit PCMCIA cards, you will need supporting software in
31 most cases. (see the file <file:Documentation/Changes> for
32 location and details).
34 To compile this driver as modules, choose M here: the
35 module will be called pcmcia.
39 config PCMCIA_LOAD_CIS
40 bool "Load CIS updates from userspace"
45 Some PCMCIA cards require an updated Card Information Structure (CIS)
46 to be loaded from userspace to work correctly. If you say Y here,
47 and your userspace is arranged correctly, this will be loaded
48 automatically using the in-kernel firmware loader and the hotplug
49 subsystem, instead of relying on cardmgr from pcmcia-cs to do so.
54 bool "32-bit CardBus support"
58 CardBus is a bus mastering architecture for PC-cards, which allows
59 for 32 bit PC-cards (the original PCMCIA standard specifies only
60 a 16 bit wide bus). Many newer PC-cards are actually CardBus cards.
62 To use 32 bit PC-cards, you also need a CardBus compatible host
63 bridge. Virtually all modern PCMCIA bridges do this, and most of
64 them are "yenta-compatible", so say Y or M there, too.
71 comment "PC-card bridges"
74 tristate "CardBus yenta-compatible bridge support"
76 select CARDBUS if !EXPERT
77 select PCCARD_NONSTATIC if PCMCIA != n
79 This option enables support for CardBus host bridges. Virtually
80 all modern PCMCIA bridges are CardBus compatible. A "bridge" is
81 the hardware inside your computer that PCMCIA cards are plugged
84 To compile this driver as modules, choose M here: the
85 module will be called yenta_socket.
91 bool "Special initialization for O2Micro bridges" if EXPERT
96 bool "Special initialization for Ricoh bridges" if EXPERT
101 bool "Special initialization for TI and EnE bridges" if EXPERT
104 config YENTA_ENE_TUNE
106 bool "Auto-tune EnE bridges for CB cards" if EXPERT
107 depends on YENTA_TI && CARDBUS
111 bool "Special initialization for Toshiba ToPIC bridges" if EXPERT
115 tristate "Cirrus PD6729 compatible bridge support"
116 depends on PCMCIA && PCI
117 select PCCARD_NONSTATIC
119 This provides support for the Cirrus PD6729 PCI-to-PCMCIA bridge
120 device, found in some older laptops and PCMCIA card readers.
123 tristate "i82092 compatible bridge support"
124 depends on PCMCIA && PCI
125 select PCCARD_NONSTATIC
127 This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device,
128 found in some older laptops and more commonly in evaluation boards for the
132 tristate "i82365 compatible bridge support"
133 depends on PCMCIA && ISA
134 select PCCARD_NONSTATIC
136 Say Y here to include support for ISA-bus PCMCIA host bridges that
137 are register compatible with the Intel i82365. These are found on
138 older laptops and ISA-bus card readers for desktop systems. A
139 "bridge" is the hardware inside your computer that PCMCIA cards are
140 plugged into. If unsure, say N.
143 tristate "Databook TCIC host bridge support"
144 depends on PCMCIA && ISA
145 select PCCARD_NONSTATIC
147 Say Y here to include support for the Databook TCIC family of PCMCIA
148 host bridges. These are only found on a handful of old systems.
149 "Bridge" is the name used for the hardware inside your computer that
150 PCMCIA cards are plugged into. If unsure, say N.
152 config PCMCIA_ALCHEMY_DEVBOARD
153 tristate "Alchemy Db/Pb1xxx PCMCIA socket services"
154 depends on MIPS_ALCHEMY && PCMCIA
156 Enable this driver of you want PCMCIA support on your Alchemy
157 Db1000, Db/Pb1100, Db/Pb1500, Db/Pb1550, Db/Pb1200, DB1300
158 board. NOT suitable for the PB1000!
160 This driver is also available as a module called db1xxx_ss.ko
162 config PCMCIA_XXS1500
163 tristate "MyCable XXS1500 PCMCIA socket support"
164 depends on PCMCIA && MIPS_XXS1500
166 Support for the PCMCIA/CF socket interface on MyCable XXS1500
169 This driver is also available as a module called xxs1500_ss.ko
171 config PCMCIA_BCM63XX
172 tristate "bcm63xx pcmcia support"
173 depends on BCM63XX && PCMCIA
175 config PCMCIA_SOC_COMMON
178 config PCMCIA_SA11XX_BASE
182 tristate "SA1100 support"
183 depends on ARM && ARCH_SA1100 && PCMCIA
184 select PCMCIA_SOC_COMMON
185 select PCMCIA_SA11XX_BASE
187 Say Y here to include support for SA11x0-based PCMCIA or CF
188 sockets, found on HP iPAQs, Yopy, and other StrongARM(R)/
189 Xscale(R) embedded machines.
191 This driver is also available as a module called sa1100_cs.
194 tristate "SA1111 support"
195 depends on ARM && SA1111 && PCMCIA
196 select PCMCIA_SOC_COMMON
197 select PCMCIA_SA11XX_BASE if ARCH_SA1100
198 select PCMCIA_PXA2XX if ARCH_LUBBOCK && SA1111
199 select PCMCIA_MAX1600 if ASSABET_NEPONSET
200 select PCMCIA_MAX1600 if ARCH_LUBBOCK && SA1111
202 Say Y here to include support for SA1111-based PCMCIA or CF
203 sockets, found on the Jornada 720, Graphicsmaster and other
204 StrongARM(R)/Xscale(R) embedded machines.
206 This driver is also available as a module called sa1111_cs.
209 tristate "PXA2xx support"
210 depends on ARM && ARCH_PXA && PCMCIA
211 depends on (ARCH_LUBBOCK || MACH_MAINSTONE || PXA_SHARPSL \
212 || MACH_ARMCORE || ARCH_PXA_PALM || TRIZEPS_PCMCIA \
213 || ARCOM_PCMCIA || ARCH_PXA_ESERIES || MACH_STARGATE2 \
214 || MACH_VPAC270 || MACH_BALLOON3 || MACH_COLIBRI \
215 || MACH_COLIBRI320 || MACH_H4700)
216 select PCMCIA_SOC_COMMON
217 select PCMCIA_MAX1600 if MACH_MAINSTONE
219 Say Y here to include support for the PXA2xx PCMCIA controller
222 bool "Enable debugging"
223 depends on (PCMCIA_SA1111 || PCMCIA_SA1100 || PCMCIA_PXA2XX)
225 Say Y here to enable debugging for the SoC PCMCIA layer.
226 You will need to choose the debugging level either via the
227 kernel command line, or module options depending whether
228 you build the drivers as modules.
230 The kernel command line options are:
231 sa11xx_core.pc_debug=N
232 pxa2xx_core.pc_debug=N
234 The module option is called pc_debug=N
236 In all the above examples, N is the debugging verbosity
241 default y if ISA && !ARCH_SA1100 && !PARISC
243 config PCMCIA_VRC4171
244 tristate "NEC VRC4171 Card Controllers support"
245 depends on CPU_VR41XX && ISA && PCMCIA
247 config PCMCIA_VRC4173
248 tristate "NEC VRC4173 CARDU support"
249 depends on CPU_VR41XX && PCI && PCMCIA
252 tristate "OMAP CompactFlash Controller"
253 depends on PCMCIA && ARCH_OMAP16XX
255 Say Y here to support the CompactFlash controller on OMAP.
256 Note that this doesn't support "True IDE" mode.
259 tristate "AT91 CompactFlash Controller"
261 depends on PCMCIA && ARCH_AT91
263 Say Y here to support the CompactFlash controller on AT91 chips.
264 Or choose M to compile the driver as a module named "at91_cf".
267 tristate "Electra CompactFlash Controller"
268 depends on PCMCIA && PPC_PASEMI
270 Say Y here to support the CompactFlash controller on the
271 PA Semi Electra eval board.
273 config PCCARD_NONSTATIC