[GitHub/mt8127/android_kernel_alcatel_ttab.git] / drivers / pcmcia / Kconfig

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

menuconfig PCCARD
	tristate "PCCard (PCMCIA/CardBus) support"
	depends on HOTPLUG
	---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 (EXPERIMENTAL)"
	depends on PCMCIA && EXPERIMENTAL
	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_M8XX
	tristate "MPC8xx PCMCIA support"
	depends on PCCARD && PPC && 8xx
	select PCCARD_IODYN if PCMCIA != n
	help
	  Say Y here to include support for PowerPC 8xx series PCMCIA
	  controller.

	  This driver is also available as a module called m8xx_pcmcia.

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