[linux-2.6-block.git] / drivers / pcmcia / Kconfig

#
# PCCARD (PCMCIA/CardBus) bus subsystem configuration
#

menuconfig PCCARD
	tristate "PCCard (PCMCIA/CardBus) support"
	---help---
	  Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
	  computer.  These are credit-card size devices such as network cards,
	  modems or hard drives often used with laptops computers.  There are
	  actually two varieties of these cards: 16 bit PCMCIA and 32 bit
	  CardBus cards.

	  To compile this driver as modules, choose M here: the
	  module will be called pcmcia_core.

if PCCARD

config PCMCIA
	tristate "16-bit PCMCIA support"
	select CRC32
	default y
	---help---
	   This option enables support for 16-bit PCMCIA cards. Most older
	   PC-cards are such 16-bit PCMCIA cards, so unless you know you're
	   only using 32-bit CardBus cards, say Y or M here.

	   To use 16-bit PCMCIA cards, you will need supporting software in
	   most cases. (see the file <file:Documentation/Changes> for
	   location and details).

	   To compile this driver as modules, choose M here: the
	   module will be called pcmcia.

	   If unsure, say Y.

config PCMCIA_LOAD_CIS
	bool "Load CIS updates from userspace"
	depends on PCMCIA
	select FW_LOADER
	default y
	help
	  Some PCMCIA cards require an updated Card Information Structure (CIS)
	  to be loaded from userspace to work correctly. If you say Y here,
	  and your userspace is arranged correctly, this will be loaded
	  automatically using the in-kernel firmware loader and the hotplug
	  subsystem, instead of relying on cardmgr from pcmcia-cs to do so.

	  If unsure, say Y.

config CARDBUS
	bool "32-bit CardBus support"
	depends on PCI
	default y
	---help---
	  CardBus is a bus mastering architecture for PC-cards, which allows
	  for 32 bit PC-cards (the original PCMCIA standard specifies only
	  a 16 bit wide bus). Many newer PC-cards are actually CardBus cards.

	  To use 32 bit PC-cards, you also need a CardBus compatible host
	  bridge. Virtually all modern PCMCIA bridges do this, and most of
	  them are "yenta-compatible", so say Y or M there, too.

	  If unsure, say Y.

comment "PC-card bridges"

config YENTA
	tristate "CardBus yenta-compatible bridge support"
	depends on PCI
	select CARDBUS if !EXPERT
	select PCCARD_NONSTATIC if PCMCIA != n
	---help---
	  This option enables support for CardBus host bridges.  Virtually
	  all modern PCMCIA bridges are CardBus compatible.  A "bridge" is
	  the hardware inside your computer that PCMCIA cards are plugged
	  into.

	  To compile this driver as modules, choose M here: the
	  module will be called yenta_socket.

	  If unsure, say Y.

config YENTA_O2
	default y
	bool "Special initialization for O2Micro bridges" if EXPERT
	depends on YENTA

config YENTA_RICOH
	default y
	bool "Special initialization for Ricoh bridges" if EXPERT
	depends on YENTA

config YENTA_TI
	default y
	bool "Special initialization for TI and EnE bridges" if EXPERT
	depends on YENTA

config YENTA_ENE_TUNE
	default y
	bool "Auto-tune EnE bridges for CB cards" if EXPERT
	depends on YENTA_TI && CARDBUS

config YENTA_TOSHIBA
	default y
	bool "Special initialization for Toshiba ToPIC bridges" if EXPERT
	depends on YENTA

config PD6729
	tristate "Cirrus PD6729 compatible bridge support"
	depends on PCMCIA && PCI
	select PCCARD_NONSTATIC
	help
	  This provides support for the Cirrus PD6729 PCI-to-PCMCIA bridge
	  device, found in some older laptops and PCMCIA card readers.

config I82092
	tristate "i82092 compatible bridge support"
	depends on PCMCIA && PCI
	select PCCARD_NONSTATIC
	help
	  This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device,
	  found in some older laptops and more commonly in evaluation boards for the
	  chip.

config I82365
	tristate "i82365 compatible bridge support"
	depends on PCMCIA && ISA
	select PCCARD_NONSTATIC
	help
	  Say Y here to include support for ISA-bus PCMCIA host bridges that
	  are register compatible with the Intel i82365.  These are found on
	  older laptops and ISA-bus card readers for desktop systems.  A
	  "bridge" is the hardware inside your computer that PCMCIA cards are
	  plugged into. If unsure, say N.

config TCIC
	tristate "Databook TCIC host bridge support"
	depends on PCMCIA && ISA
	select PCCARD_NONSTATIC
	help
	  Say Y here to include support for the Databook TCIC family of PCMCIA
	  host bridges. These are only found on a handful of old systems.
	  "Bridge" is the name used for the hardware inside your computer that
	  PCMCIA cards are plugged into. If unsure, say N.

config PCMCIA_ALCHEMY_DEVBOARD
	tristate "Alchemy Db/Pb1xxx PCMCIA socket services"
	depends on MIPS_ALCHEMY && PCMCIA
	select 64BIT_PHYS_ADDR
	help
	  Enable this driver of you want PCMCIA support on your Alchemy
	  Db1000, Db/Pb1100, Db/Pb1500, Db/Pb1550, Db/Pb1200, DB1300
	  board.  NOT suitable for the PB1000!

	  This driver is also available as a module called db1xxx_ss.ko

config PCMCIA_XXS1500
	tristate "MyCable XXS1500 PCMCIA socket support"
	depends on PCMCIA && MIPS_XXS1500
	select 64BIT_PHYS_ADDR
	help
	  Support for the PCMCIA/CF socket interface on MyCable XXS1500
	  systems.

	  This driver is also available as a module called xxs1500_ss.ko

config PCMCIA_BCM63XX
	tristate "bcm63xx pcmcia support"
	depends on BCM63XX && PCMCIA

config PCMCIA_SOC_COMMON
	tristate

config PCMCIA_SA11XX_BASE
	tristate

config PCMCIA_SA1100
	tristate "SA1100 support"
	depends on ARM && ARCH_SA1100 && PCMCIA
	select PCMCIA_SOC_COMMON
	select PCMCIA_SA11XX_BASE
	help
	  Say Y here to include support for SA11x0-based PCMCIA or CF
	  sockets, found on HP iPAQs, Yopy, and other StrongARM(R)/
	  Xscale(R) embedded machines.

	  This driver is also available as a module called sa1100_cs.

config PCMCIA_SA1111
	tristate "SA1111 support"
	depends on ARM && SA1111 && PCMCIA
	select PCMCIA_SOC_COMMON
	select PCMCIA_SA11XX_BASE if ARCH_SA1100
	help
	  Say Y  here to include support for SA1111-based PCMCIA or CF
	  sockets, found on the Jornada 720, Graphicsmaster and other
	  StrongARM(R)/Xscale(R) embedded machines.

	  This driver is also available as a module called sa1111_cs.

config PCMCIA_PXA2XX
	tristate "PXA2xx support"
	depends on ARM && ARCH_PXA && PCMCIA
	depends on (ARCH_LUBBOCK || MACH_MAINSTONE || PXA_SHARPSL \
		    || MACH_ARMCORE || ARCH_PXA_PALM || TRIZEPS_PCMCIA \
		    || ARCOM_PCMCIA || ARCH_PXA_ESERIES || MACH_STARGATE2 \
		    || MACH_VPAC270 || MACH_BALLOON3 || MACH_COLIBRI \
		    || MACH_COLIBRI320 || MACH_H4700)
	select PCMCIA_SA1111 if ARCH_LUBBOCK && SA1111
	select PCMCIA_SOC_COMMON
	help
	  Say Y here to include support for the PXA2xx PCMCIA controller

config PCMCIA_DEBUG
	bool "Enable debugging"
	depends on (PCMCIA_SA1111 || PCMCIA_SA1100 || PCMCIA_PXA2XX)
	help
	  Say Y here to enable debugging for the SoC PCMCIA layer.
	  You will need to choose the debugging level either via the
	  kernel command line, or module options depending whether
	  you build the drivers as modules.

	  The kernel command line options are:
	    sa11xx_core.pc_debug=N
	    pxa2xx_core.pc_debug=N

	  The module option is called pc_debug=N

	  In all the above examples, N is the debugging verbosity
	  level.

config PCMCIA_PROBE
	bool
	default y if ISA && !ARCH_SA1100 && !PARISC

config M32R_PCC
	bool "M32R PCMCIA I/F"
	depends on M32R && CHIP_M32700 && PCMCIA
	help
	  Say Y here to use the M32R PCMCIA controller.

config M32R_CFC
	bool "M32R CF I/F Controller"
	depends on M32R && (PLAT_USRV || PLAT_M32700UT || PLAT_MAPPI2 || PLAT_MAPPI3 || PLAT_OPSPUT)
	help
	  Say Y here to use the M32R CompactFlash controller.

config M32R_CFC_NUM
	int "M32R CF I/F number"
	depends on M32R_CFC
	default "1" if PLAT_USRV || PLAT_M32700UT || PLAT_MAPPI2 || PLAT_MAPPI3 || PLAT_OPSPUT
	help
	  Set the number of M32R CF slots.

config PCMCIA_VRC4171
	tristate "NEC VRC4171 Card Controllers support"
	depends on CPU_VR41XX && ISA && PCMCIA

config PCMCIA_VRC4173
	tristate "NEC VRC4173 CARDU support"
	depends on CPU_VR41XX && PCI && PCMCIA

config OMAP_CF
	tristate "OMAP CompactFlash Controller"
	depends on PCMCIA && ARCH_OMAP16XX
	help
	  Say Y here to support the CompactFlash controller on OMAP.
	  Note that this doesn't support "True IDE" mode.

config BFIN_CFPCMCIA
	tristate "Blackfin CompactFlash PCMCIA Driver"
	depends on PCMCIA && BLACKFIN
	help
	  Say Y here to support the CompactFlash PCMCIA driver for Blackfin.


config AT91_CF
	tristate "AT91 CompactFlash Controller"
	depends on PCMCIA && ARCH_AT91
	help
	  Say Y here to support the CompactFlash controller on AT91 chips.
	  Or choose M to compile the driver as a module named "at91_cf".

config ELECTRA_CF
	tristate "Electra CompactFlash Controller"
	depends on PCMCIA && PPC_PASEMI
	help
	  Say Y here to support the CompactFlash controller on the
	  PA Semi Electra eval board.

config PCCARD_NONSTATIC
	bool

config PCCARD_IODYN
	bool

endif	# PCCARD
Commit	Line	Data
1da177e4	1	#
bf45d9b0	2	# PCCARD (PCMCIA/CardBus) bus subsystem configuration
1da177e4 LT	3	#
1da177e4 LT	4
42c5323c	5	menuconfig PCCARD
1da177e4	6	tristate "PCCard (PCMCIA/CardBus) support"
1da177e4 LT	7	---help---
	8	Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
	9	computer. These are credit-card size devices such as network cards,
	10	modems or hard drives often used with laptops computers. There are
9a5555b8 DB	11	actually two varieties of these cards: 16 bit PCMCIA and 32 bit
9a5555b8 DB	12	CardBus cards.
1da177e4 LT	13
	14	To compile this driver as modules, choose M here: the
	15	module will be called pcmcia_core.
	16
	17	if PCCARD
	18
1da177e4 LT	19	config PCMCIA
1da177e4 LT	20	tristate "16-bit PCMCIA support"
f861bd23	21	select CRC32
1da177e4 LT	22	default y
	23	---help---
	24	This option enables support for 16-bit PCMCIA cards. Most older
	25	PC-cards are such 16-bit PCMCIA cards, so unless you know you're
	26	only using 32-bit CardBus cards, say Y or M here.
	27
9a5555b8 DB	28	To use 16-bit PCMCIA cards, you will need supporting software in
	29	most cases. (see the file <file:Documentation/Changes> for
	30	location and details).
1da177e4 LT	31
	32	To compile this driver as modules, choose M here: the
	33	module will be called pcmcia.
	34
	35	If unsure, say Y.
	36
daa9517d	37	config PCMCIA_LOAD_CIS
204911fb KC	38	bool "Load CIS updates from userspace"
204911fb KC	39	depends on PCMCIA
daa9517d DB	40	select FW_LOADER
	41	default y
	42	help
	43	Some PCMCIA cards require an updated Card Information Structure (CIS)
	44	to be loaded from userspace to work correctly. If you say Y here,
	45	and your userspace is arranged correctly, this will be loaded
	46	automatically using the in-kernel firmware loader and the hotplug
	47	subsystem, instead of relying on cardmgr from pcmcia-cs to do so.
	48
	49	If unsure, say Y.
	50
1da177e4	51	config CARDBUS
9fea84f4	52	bool "32-bit CardBus support"
1da177e4 LT	53	depends on PCI
	54	default y
	55	---help---
	56	CardBus is a bus mastering architecture for PC-cards, which allows
	57	for 32 bit PC-cards (the original PCMCIA standard specifies only
	58	a 16 bit wide bus). Many newer PC-cards are actually CardBus cards.
	59
	60	To use 32 bit PC-cards, you also need a CardBus compatible host
	61	bridge. Virtually all modern PCMCIA bridges do this, and most of
	62	them are "yenta-compatible", so say Y or M there, too.
	63
	64	If unsure, say Y.
	65
	66	comment "PC-card bridges"
	67
	68	config YENTA
	69	tristate "CardBus yenta-compatible bridge support"
89b39f5d	70	depends on PCI
6a108a14	71	select CARDBUS if !EXPERT
9d9c98e8	72	select PCCARD_NONSTATIC if PCMCIA != n
1da177e4 LT	73	---help---
1da177e4 LT	74	This option enables support for CardBus host bridges. Virtually
9fea84f4 DB	75	all modern PCMCIA bridges are CardBus compatible. A "bridge" is
9fea84f4 DB	76	the hardware inside your computer that PCMCIA cards are plugged
1da177e4 LT	77	into.
	78
	79	To compile this driver as modules, choose M here: the
	80	module will be called yenta_socket.
	81
	82	If unsure, say Y.
	83
63e7ebd0 DR	84	config YENTA_O2
63e7ebd0 DR	85	default y
6a108a14	86	bool "Special initialization for O2Micro bridges" if EXPERT
63e7ebd0 DR	87	depends on YENTA
	88
	89	config YENTA_RICOH
	90	default y
6a108a14	91	bool "Special initialization for Ricoh bridges" if EXPERT
63e7ebd0 DR	92	depends on YENTA
	93
	94	config YENTA_TI
	95	default y
6a108a14	96	bool "Special initialization for TI and EnE bridges" if EXPERT
63e7ebd0 DR	97	depends on YENTA
	98
	99	config YENTA_ENE_TUNE
	100	default y
6a108a14	101	bool "Auto-tune EnE bridges for CB cards" if EXPERT
63e7ebd0 DR	102	depends on YENTA_TI && CARDBUS
	103
	104	config YENTA_TOSHIBA
	105	default y
6a108a14	106	bool "Special initialization for Toshiba ToPIC bridges" if EXPERT
63e7ebd0 DR	107	depends on YENTA
63e7ebd0 DR	108
1da177e4 LT	109	config PD6729
	110	tristate "Cirrus PD6729 compatible bridge support"
	111	depends on PCMCIA && PCI
	112	select PCCARD_NONSTATIC
	113	help
	114	This provides support for the Cirrus PD6729 PCI-to-PCMCIA bridge
	115	device, found in some older laptops and PCMCIA card readers.
	116
	117	config I82092
	118	tristate "i82092 compatible bridge support"
	119	depends on PCMCIA && PCI
	120	select PCCARD_NONSTATIC
	121	help
	122	This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device,
	123	found in some older laptops and more commonly in evaluation boards for the
	124	chip.
	125
	126	config I82365
	127	tristate "i82365 compatible bridge support"
	128	depends on PCMCIA && ISA
	129	select PCCARD_NONSTATIC
	130	help
	131	Say Y here to include support for ISA-bus PCMCIA host bridges that
	132	are register compatible with the Intel i82365. These are found on
	133	older laptops and ISA-bus card readers for desktop systems. A
	134	"bridge" is the hardware inside your computer that PCMCIA cards are
	135	plugged into. If unsure, say N.
	136
	137	config TCIC
	138	tristate "Databook TCIC host bridge support"
81000808	139	depends on PCMCIA && ISA
1da177e4 LT	140	select PCCARD_NONSTATIC
	141	help
	142	Say Y here to include support for the Databook TCIC family of PCMCIA
	143	host bridges. These are only found on a handful of old systems.
	144	"Bridge" is the name used for the hardware inside your computer that
	145	PCMCIA cards are plugged into. If unsure, say N.
	146
66213b3c ML	147	config PCMCIA_ALCHEMY_DEVBOARD
66213b3c ML	148	tristate "Alchemy Db/Pb1xxx PCMCIA socket services"
42a4f17d	149	depends on MIPS_ALCHEMY && PCMCIA
66213b3c ML	150	select 64BIT_PHYS_ADDR
	151	help
	152	Enable this driver of you want PCMCIA support on your Alchemy
64cd04d0 ML	153	Db1000, Db/Pb1100, Db/Pb1500, Db/Pb1550, Db/Pb1200, DB1300
64cd04d0 ML	154	board. NOT suitable for the PB1000!
66213b3c ML	155
	156	This driver is also available as a module called db1xxx_ss.ko
	157
0273b4ef ML	158	config PCMCIA_XXS1500
	159	tristate "MyCable XXS1500 PCMCIA socket support"
	160	depends on PCMCIA && MIPS_XXS1500
	161	select 64BIT_PHYS_ADDR
	162	help
	163	Support for the PCMCIA/CF socket interface on MyCable XXS1500
	164	systems.
	165
	166	This driver is also available as a module called xxs1500_ss.ko
	167
553d6d5f MB	168	config PCMCIA_BCM63XX
	169	tristate "bcm63xx pcmcia support"
	170	depends on BCM63XX && PCMCIA
	171
0f767de6	172	config PCMCIA_SOC_COMMON
1bf8e621	173	tristate
0f767de6	174
136b758b RK	175	config PCMCIA_SA11XX_BASE
	176	tristate
	177
1da177e4 LT	178	config PCMCIA_SA1100
	179	tristate "SA1100 support"
	180	depends on ARM && ARCH_SA1100 && PCMCIA
0f767de6	181	select PCMCIA_SOC_COMMON
136b758b	182	select PCMCIA_SA11XX_BASE
1da177e4 LT	183	help
	184	Say Y here to include support for SA11x0-based PCMCIA or CF
	185	sockets, found on HP iPAQs, Yopy, and other StrongARM(R)/
	186	Xscale(R) embedded machines.
	187
	188	This driver is also available as a module called sa1100_cs.
	189
	190	config PCMCIA_SA1111
	191	tristate "SA1111 support"
11990b2b	192	depends on ARM && SA1111 && PCMCIA
0f767de6	193	select PCMCIA_SOC_COMMON
11990b2b	194	select PCMCIA_SA11XX_BASE if ARCH_SA1100
1da177e4 LT	195	help
	196	Say Y here to include support for SA1111-based PCMCIA or CF
	197	sockets, found on the Jornada 720, Graphicsmaster and other
	198	StrongARM(R)/Xscale(R) embedded machines.
	199
	200	This driver is also available as a module called sa1111_cs.
	201
	202	config PCMCIA_PXA2XX
	203	tristate "PXA2xx support"
	204	depends on ARM && ARCH_PXA && PCMCIA
35978408	205	depends on (ARCH_LUBBOCK \|\| MACH_MAINSTONE \|\| PXA_SHARPSL \
cc513ac0	206	\|\| MACH_ARMCORE \|\| ARCH_PXA_PALM \|\| TRIZEPS_PCMCIA \
addff0fa	207	\|\| ARCOM_PCMCIA \|\| ARCH_PXA_ESERIES \|\| MACH_STARGATE2 \
fd62999b	208	\|\| MACH_VPAC270 \|\| MACH_BALLOON3 \|\| MACH_COLIBRI \
95244306	209	\|\| MACH_COLIBRI320 \|\| MACH_H4700)
11990b2b	210	select PCMCIA_SA1111 if ARCH_LUBBOCK && SA1111
0f767de6	211	select PCMCIA_SOC_COMMON
1da177e4 LT	212	help
	213	Say Y here to include support for the PXA2xx PCMCIA controller
	214
c9f50ddd DB	215	config PCMCIA_DEBUG
	216	bool "Enable debugging"
	217	depends on (PCMCIA_SA1111 \|\| PCMCIA_SA1100 \|\| PCMCIA_PXA2XX)
	218	help
	219	Say Y here to enable debugging for the SoC PCMCIA layer.
	220	You will need to choose the debugging level either via the
	221	kernel command line, or module options depending whether
	222	you build the drivers as modules.
	223
	224	The kernel command line options are:
	225	sa11xx_core.pc_debug=N
	226	pxa2xx_core.pc_debug=N
	227
	228	The module option is called pc_debug=N
	229
	230	In all the above examples, N is the debugging verbosity
	231	level.
	232
1da177e4 LT	233	config PCMCIA_PROBE
1da177e4 LT	234	bool
ea6add0b	235	default y if ISA && !ARCH_SA1100 && !PARISC
1da177e4 LT	236
	237	config M32R_PCC
	238	bool "M32R PCMCIA I/F"
	239	depends on M32R && CHIP_M32700 && PCMCIA
	240	help
	241	Say Y here to use the M32R PCMCIA controller.
	242
	243	config M32R_CFC
	244	bool "M32R CF I/F Controller"
934bb7f8	245	depends on M32R && (PLAT_USRV \|\| PLAT_M32700UT \|\| PLAT_MAPPI2 \|\| PLAT_MAPPI3 \|\| PLAT_OPSPUT)
1da177e4 LT	246	help
	247	Say Y here to use the M32R CompactFlash controller.
	248
	249	config M32R_CFC_NUM
	250	int "M32R CF I/F number"
	251	depends on M32R_CFC
934bb7f8	252	default "1" if PLAT_USRV \|\| PLAT_M32700UT \|\| PLAT_MAPPI2 \|\| PLAT_MAPPI3 \|\| PLAT_OPSPUT
1da177e4 LT	253	help
	254	Set the number of M32R CF slots.
	255
	256	config PCMCIA_VRC4171
	257	tristate "NEC VRC4171 Card Controllers support"
daaeb72b	258	depends on CPU_VR41XX && ISA && PCMCIA
1da177e4 LT	259
	260	config PCMCIA_VRC4173
	261	tristate "NEC VRC4173 CARDU support"
	262	depends on CPU_VR41XX && PCI && PCMCIA
	263
f74e48a5 DB	264	config OMAP_CF
	265	tristate "OMAP CompactFlash Controller"
	266	depends on PCMCIA && ARCH_OMAP16XX
	267	help
	268	Say Y here to support the CompactFlash controller on OMAP.
	269	Note that this doesn't support "True IDE" mode.
	270
785e821e MH	271	config BFIN_CFPCMCIA
	272	tristate "Blackfin CompactFlash PCMCIA Driver"
	273	depends on PCMCIA && BLACKFIN
	274	help
	275	Say Y here to support the CompactFlash PCMCIA driver for Blackfin.
	276
	277
2c1f3b7a AV	278	config AT91_CF
2c1f3b7a AV	279	tristate "AT91 CompactFlash Controller"
ed9084ec	280	depends on PCMCIA && ARCH_AT91
2c1f3b7a AV	281	help
	282	Say Y here to support the CompactFlash controller on AT91 chips.
	283	Or choose M to compile the driver as a module named "at91_cf".
	284
2b571a06 OJ	285	config ELECTRA_CF
	286	tristate "Electra CompactFlash Controller"
	287	depends on PCMCIA && PPC_PASEMI
	288	help
	289	Say Y here to support the CompactFlash controller on the
	290	PA Semi Electra eval board.
	291
1da177e4	292	config PCCARD_NONSTATIC
49b1153a	293	bool
1da177e4	294
3b27e942 DB	295	config PCCARD_IODYN
	296	bool
	297
1da177e4	298	endif # PCCARD