[deliverable/linux.git] / drivers / mtd / nand / Kconfig

# drivers/mtd/nand/Kconfig
# $Id: Kconfig,v 1.35 2005/11/07 11:14:30 gleixner Exp $

menu "NAND Flash Device Drivers"
	depends on MTD!=n

config MTD_NAND
	tristate "NAND Device Support"
	depends on MTD
	select MTD_NAND_IDS
	help
	  This enables support for accessing all type of NAND flash
	  devices. For further information see
	  <http://www.linux-mtd.infradead.org/tech/nand.html>.

config MTD_NAND_VERIFY_WRITE
	bool "Verify NAND page writes"
	depends on MTD_NAND
	help
	  This adds an extra check when data is written to the flash. The
	  NAND flash device internally checks only bits transitioning
	  from 1 to 0. There is a rare possibility that even though the
	  device thinks the write was successful, a bit could have been
	  flipped accidentaly due to device wear or something else.

config MTD_NAND_AUTCPU12
	tristate "SmartMediaCard on autronix autcpu12 board"
	depends on MTD_NAND && ARCH_AUTCPU12
	help
	  This enables the driver for the autronix autcpu12 board to
	  access the SmartMediaCard.

config MTD_NAND_EDB7312
	tristate "Support for Cirrus Logic EBD7312 evaluation board"
	depends on MTD_NAND && ARCH_EDB7312
	help
	  This enables the driver for the Cirrus Logic EBD7312 evaluation
	  board to access the onboard NAND Flash.

config MTD_NAND_H1900
	tristate "iPAQ H1900 flash"
	depends on MTD_NAND && ARCH_PXA && MTD_PARTITIONS
	help
	  This enables the driver for the iPAQ h1900 flash.

config MTD_NAND_SPIA
	tristate "NAND Flash device on SPIA board"
	depends on ARCH_P720T && MTD_NAND
	help
	  If you had to ask, you don't have one. Say 'N'.

config MTD_NAND_TOTO
	tristate "NAND Flash device on TOTO board"
	depends on ARCH_OMAP && MTD_NAND
	help
	  Support for NAND flash on Texas Instruments Toto platform.

config MTD_NAND_TS7250
	tristate "NAND Flash device on TS-7250 board"
	depends on MACH_TS72XX && MTD_NAND
	help
	  Support for NAND flash on Technologic Systems TS-7250 platform.

config MTD_NAND_IDS
	tristate

config MTD_NAND_AU1550
	tristate "Au1550/1200 NAND support"
	depends on (SOC_AU1200 || SOC_AU1550) && MTD_NAND
	help
	  This enables the driver for the NAND flash controller on the
	  AMD/Alchemy 1550 SOC.

config MTD_NAND_RTC_FROM4
	tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
	depends on MTD_NAND && SH_SOLUTION_ENGINE
	select REED_SOLOMON
	select REED_SOLOMON_DEC8
	help
	  This enables the driver for the Renesas Technology AG-AND
	  flash interface board (FROM_BOARD4)

config MTD_NAND_PPCHAMELEONEVB
	tristate "NAND Flash device on PPChameleonEVB board"
	depends on PPCHAMELEONEVB && MTD_NAND
	help
	  This enables the NAND flash driver on the PPChameleon EVB Board.

config MTD_NAND_S3C2410
	tristate "NAND Flash support for S3C2410/S3C2440 SoC"
	depends on ARCH_S3C2410 && MTD_NAND
	help
	  This enables the NAND flash controller on the S3C2410 and S3C2440
	  SoCs

	  No board specfic support is done by this driver, each board
	  must advertise a platform_device for the driver to attach.

config MTD_NAND_S3C2410_DEBUG
	bool "S3C2410 NAND driver debug"
	depends on MTD_NAND_S3C2410
	help
	  Enable debugging of the S3C2410 NAND driver

config MTD_NAND_S3C2410_HWECC
	bool "S3C2410 NAND Hardware ECC"
	depends on MTD_NAND_S3C2410
	help
	  Enable the use of the S3C2410's internal ECC generator when
	  using NAND. Early versions of the chip have had problems with
	  incorrect ECC generation, and if using these, the default of
	  software ECC is preferable.

	  If you lay down a device with the hardware ECC, then you will
	  currently not be able to switch to software, as there is no
	  implementation for ECC method used by the S3C2410

config MTD_NAND_DISKONCHIP
	tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
	depends on MTD_NAND && EXPERIMENTAL
	select REED_SOLOMON
	select REED_SOLOMON_DEC16
	help
	  This is a reimplementation of M-Systems DiskOnChip 2000,
	  Millennium and Millennium Plus as a standard NAND device driver,
	  as opposed to the earlier self-contained MTD device drivers.
	  This should enable, among other things, proper JFFS2 operation on
	  these devices.

config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
        bool "Advanced detection options for DiskOnChip"
        depends on MTD_NAND_DISKONCHIP
        help
          This option allows you to specify nonstandard address at which to
          probe for a DiskOnChip, or to change the detection options.  You
          are unlikely to need any of this unless you are using LinuxBIOS.
          Say 'N'.

config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
        hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
        depends on MTD_NAND_DISKONCHIP
        default "0"
        ---help---
        By default, the probe for DiskOnChip devices will look for a
        DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
        This option allows you to specify a single address at which to probe
        for the device, which is useful if you have other devices in that
        range which get upset when they are probed.

        (Note that on PowerPC, the normal probe will only check at
        0xE4000000.)

        Normally, you should leave this set to zero, to allow the probe at
        the normal addresses.

config MTD_NAND_DISKONCHIP_PROBE_HIGH
        bool "Probe high addresses"
        depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
        help
          By default, the probe for DiskOnChip devices will look for a
          DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
          This option changes to make it probe between 0xFFFC8000 and
          0xFFFEE000.  Unless you are using LinuxBIOS, this is unlikely to be
          useful to you.  Say 'N'.

config MTD_NAND_DISKONCHIP_BBTWRITE
	bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
	depends on MTD_NAND_DISKONCHIP
	help
	  On DiskOnChip devices shipped with the INFTL filesystem (Millennium
	  and 2000 TSOP/Alon), Linux reserves some space at the end of the
	  device for the Bad Block Table (BBT).  If you have existing INFTL
	  data on your device (created by non-Linux tools such as M-Systems'
	  DOS drivers), your data might overlap the area Linux wants to use for
	  the BBT.  If this is a concern for you, leave this option disabled and
	  Linux will not write BBT data into this area.
	  The downside of leaving this option disabled is that if bad blocks
	  are detected by Linux, they will not be recorded in the BBT, which
	  could cause future problems.
	  Once you enable this option, new filesystems (INFTL or others, created
	  in Linux or other operating systems) will not use the reserved area.
	  The only reason not to enable this option is to prevent damage to
	  preexisting filesystems.
	  Even if you leave this disabled, you can enable BBT writes at module
	  load time (assuming you build diskonchip as a module) with the module
	  parameter "inftl_bbt_write=1".

config MTD_NAND_SHARPSL
	tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
	depends on MTD_NAND && ARCH_PXA

config MTD_NAND_CS553X
	tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
	depends on MTD_NAND && X86_PC && PCI
	
config MTD_NAND_NANDSIM
	tristate "Support for NAND Flash Simulator"
	depends on MTD_NAND && MTD_PARTITIONS
	help
	  The simulator may simulate verious NAND flash chips for the
	  MTD nand layer.

endmenu
Commit	Line	Data
1da177e4	1	# drivers/mtd/nand/Kconfig
61b03bd7	2	# $Id: Kconfig,v 1.35 2005/11/07 11:14:30 gleixner Exp $
1da177e4 LT	3
	4	menu "NAND Flash Device Drivers"
	5	depends on MTD!=n
	6
	7	config MTD_NAND
	8	tristate "NAND Device Support"
	9	depends on MTD
	10	select MTD_NAND_IDS
	11	help
	12	This enables support for accessing all type of NAND flash
	13	devices. For further information see
	14	<http://www.linux-mtd.infradead.org/tech/nand.html>.
	15
	16	config MTD_NAND_VERIFY_WRITE
	17	bool "Verify NAND page writes"
	18	depends on MTD_NAND
	19	help
	20	This adds an extra check when data is written to the flash. The
	21	NAND flash device internally checks only bits transitioning
	22	from 1 to 0. There is a rare possibility that even though the
	23	device thinks the write was successful, a bit could have been
	24	flipped accidentaly due to device wear or something else.
	25
	26	config MTD_NAND_AUTCPU12
	27	tristate "SmartMediaCard on autronix autcpu12 board"
30966174	28	depends on MTD_NAND && ARCH_AUTCPU12
1da177e4	29	help
61b03bd7	30	This enables the driver for the autronix autcpu12 board to
1da177e4 LT	31	access the SmartMediaCard.
	32
	33	config MTD_NAND_EDB7312
	34	tristate "Support for Cirrus Logic EBD7312 evaluation board"
30966174	35	depends on MTD_NAND && ARCH_EDB7312
1da177e4	36	help
61b03bd7	37	This enables the driver for the Cirrus Logic EBD7312 evaluation
1da177e4 LT	38	board to access the onboard NAND Flash.
	39
	40	config MTD_NAND_H1900
	41	tristate "iPAQ H1900 flash"
30966174	42	depends on MTD_NAND && ARCH_PXA && MTD_PARTITIONS
1da177e4 LT	43	help
	44	This enables the driver for the iPAQ h1900 flash.
	45
	46	config MTD_NAND_SPIA
	47	tristate "NAND Flash device on SPIA board"
30966174	48	depends on ARCH_P720T && MTD_NAND
1da177e4 LT	49	help
	50	If you had to ask, you don't have one. Say 'N'.
	51
	52	config MTD_NAND_TOTO
	53	tristate "NAND Flash device on TOTO board"
30966174	54	depends on ARCH_OMAP && MTD_NAND
1da177e4 LT	55	help
	56	Support for NAND flash on Texas Instruments Toto platform.
	57
7d532dd5 LB	58	config MTD_NAND_TS7250
	59	tristate "NAND Flash device on TS-7250 board"
	60	depends on MACH_TS72XX && MTD_NAND
	61	help
	62	Support for NAND flash on Technologic Systems TS-7250 platform.
	63
1da177e4 LT	64	config MTD_NAND_IDS
	65	tristate
	66
1da177e4	67	config MTD_NAND_AU1550
ef6f0d1f PP	68	tristate "Au1550/1200 NAND support"
ef6f0d1f PP	69	depends on (SOC_AU1200 \|\| SOC_AU1550) && MTD_NAND
1da177e4 LT	70	help
	71	This enables the driver for the NAND flash controller on the
	72	AMD/Alchemy 1550 SOC.
	73
	74	config MTD_NAND_RTC_FROM4
	75	tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
	76	depends on MTD_NAND && SH_SOLUTION_ENGINE
	77	select REED_SOLOMON
	78	select REED_SOLOMON_DEC8
	79	help
61b03bd7	80	This enables the driver for the Renesas Technology AG-AND
1da177e4 LT	81	flash interface board (FROM_BOARD4)
	82
	83	config MTD_NAND_PPCHAMELEONEVB
	84	tristate "NAND Flash device on PPChameleonEVB board"
	85	depends on PPCHAMELEONEVB && MTD_NAND
	86	help
	87	This enables the NAND flash driver on the PPChameleon EVB Board.
	88
	89	config MTD_NAND_S3C2410
a4f957f1	90	tristate "NAND Flash support for S3C2410/S3C2440 SoC"
1da177e4 LT	91	depends on ARCH_S3C2410 && MTD_NAND
1da177e4 LT	92	help
a4f957f1 BD	93	This enables the NAND flash controller on the S3C2410 and S3C2440
a4f957f1 BD	94	SoCs
1da177e4 LT	95
1da177e4 LT	96	No board specfic support is done by this driver, each board
61b03bd7	97	must advertise a platform_device for the driver to attach.
1da177e4 LT	98
	99	config MTD_NAND_S3C2410_DEBUG
	100	bool "S3C2410 NAND driver debug"
	101	depends on MTD_NAND_S3C2410
	102	help
	103	Enable debugging of the S3C2410 NAND driver
	104
	105	config MTD_NAND_S3C2410_HWECC
	106	bool "S3C2410 NAND Hardware ECC"
	107	depends on MTD_NAND_S3C2410
	108	help
	109	Enable the use of the S3C2410's internal ECC generator when
	110	using NAND. Early versions of the chip have had problems with
	111	incorrect ECC generation, and if using these, the default of
	112	software ECC is preferable.
	113
	114	If you lay down a device with the hardware ECC, then you will
	115	currently not be able to switch to software, as there is no
	116	implementation for ECC method used by the S3C2410
	117
	118	config MTD_NAND_DISKONCHIP
	119	tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
	120	depends on MTD_NAND && EXPERIMENTAL
	121	select REED_SOLOMON
	122	select REED_SOLOMON_DEC16
	123	help
	124	This is a reimplementation of M-Systems DiskOnChip 2000,
	125	Millennium and Millennium Plus as a standard NAND device driver,
	126	as opposed to the earlier self-contained MTD device drivers.
	127	This should enable, among other things, proper JFFS2 operation on
	128	these devices.
	129
	130	config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
	131	bool "Advanced detection options for DiskOnChip"
	132	depends on MTD_NAND_DISKONCHIP
	133	help
	134	This option allows you to specify nonstandard address at which to
	135	probe for a DiskOnChip, or to change the detection options. You
	136	are unlikely to need any of this unless you are using LinuxBIOS.
	137	Say 'N'.
	138
	139	config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
	140	hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
	141	depends on MTD_NAND_DISKONCHIP
	142	default "0"
	143	---help---
	144	By default, the probe for DiskOnChip devices will look for a
	145	DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
	146	This option allows you to specify a single address at which to probe
	147	for the device, which is useful if you have other devices in that
	148	range which get upset when they are probed.
	149
	150	(Note that on PowerPC, the normal probe will only check at
	151	0xE4000000.)
	152
	153	Normally, you should leave this set to zero, to allow the probe at
	154	the normal addresses.
	155
	156	config MTD_NAND_DISKONCHIP_PROBE_HIGH
	157	bool "Probe high addresses"
	158	depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
	159	help
	160	By default, the probe for DiskOnChip devices will look for a
	161	DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
162	This option changes to make it probe between 0xFFFC8000 and
163	0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
164	useful to you. Say 'N'.
165
166	config MTD_NAND_DISKONCHIP_BBTWRITE
167	bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
168	depends on MTD_NAND_DISKONCHIP
169	help
170	On DiskOnChip devices shipped with the INFTL filesystem (Millennium
171	and 2000 TSOP/Alon), Linux reserves some space at the end of the
172	device for the Bad Block Table (BBT). If you have existing INFTL
173	data on your device (created by non-Linux tools such as M-Systems'
174	DOS drivers), your data might overlap the area Linux wants to use for
175	the BBT. If this is a concern for you, leave this option disabled and
176	Linux will not write BBT data into this area.
177	The downside of leaving this option disabled is that if bad blocks
178	are detected by Linux, they will not be recorded in the BBT, which
179	could cause future problems.
180	Once you enable this option, new filesystems (INFTL or others, created
181	in Linux or other operating systems) will not use the reserved area.
182	The only reason not to enable this option is to prevent damage to
183	preexisting filesystems.
184	Even if you leave this disabled, you can enable BBT writes at module
185	load time (assuming you build diskonchip as a module) with the module
186	parameter "inftl_bbt_write=1".
1da177e4	187
54af6b46 AB	188	config MTD_NAND_SHARPSL
	189	tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
	190	depends on MTD_NAND && ARCH_PXA
	191
179fdc3f DW	192	config MTD_NAND_CS553X
	193	tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
	194	depends on MTD_NAND && X86_PC && PCI
	195
54af6b46 AB	196	config MTD_NAND_NANDSIM
	197	tristate "Support for NAND Flash Simulator"
	198	depends on MTD_NAND && MTD_PARTITIONS
1da177e4 LT	199	help
	200	The simulator may simulate verious NAND flash chips for the
	201	MTD nand layer.
54af6b46	202
1da177e4	203	endmenu