1 # drivers/mtd/nand/Kconfig
2 # $Id: Kconfig,v 1.22 2004/10/05 22:11:46 gleixner Exp $
4 menu "NAND Flash Device Drivers"
8 tristate "NAND Device Support"
11 This enables support for accessing all type of NAND flash
12 devices. For further information see
13 <http://www.linux-mtd.infradead.org/tech/nand.html>.
15 config MTD_NAND_VERIFY_WRITE
16 bool "Verify NAND page writes"
19 This adds an extra check when data is written to the flash. The
20 NAND flash device internally checks only bits transitioning
21 from 1 to 0. There is a rare possibility that even though the
22 device thinks the write was successful, a bit could have been
23 flipped accidentaly due to device wear or something else.
25 config MTD_NAND_AUTCPU12
26 tristate "SmartMediaCard on autronix autcpu12 board"
27 depends on ARM && MTD_NAND && ARCH_AUTCPU12
29 This enables the driver for the autronix autcpu12 board to
30 access the SmartMediaCard.
32 config MTD_NAND_EDB7312
33 tristate "Support for Cirrus Logic EBD7312 evaluation board"
34 depends on ARM && MTD_NAND && ARCH_EDB7312
36 This enables the driver for the Cirrus Logic EBD7312 evaluation
37 board to access the onboard NAND Flash.
40 tristate "iPAQ H1900 flash"
41 depends on ARM && MTD_NAND && ARCH_PXA && MTD_PARTITIONS
43 This enables the driver for the iPAQ h1900 flash.
46 tristate "NAND Flash device on SPIA board"
47 depends on ARM && ARCH_P720T && MTD_NAND
49 If you had to ask, you don't have one. Say 'N'.
52 tristate "NAND Flash device on TOTO board"
53 depends on ARM && ARCH_OMAP && MTD_NAND
55 Support for NAND flash on Texas Instruments Toto platform.
59 default y if MTD_NAND = y || MTD_DOC2000 = y || MTD_DOC2001 = y || MTD_DOC2001PLUS = y
60 default m if MTD_NAND = m || MTD_DOC2000 = m || MTD_DOC2001 = m || MTD_DOC2001PLUS = m
62 config MTD_NAND_TX4925NDFMC
63 tristate "SmartMedia Card on Toshiba RBTX4925 reference board"
64 depends on TOSHIBA_RBTX4925 && MTD_NAND && TOSHIBA_RBTX4925_MPLEX_NAND
66 This enables the driver for the NAND flash device found on the
67 Toshiba RBTX4925 reference board, which is a SmartMediaCard.
69 config MTD_NAND_TX4938NDFMC
70 tristate "NAND Flash device on Toshiba RBTX4938 reference board"
71 depends on TOSHIBA_RBTX4938 && MTD_NAND && TOSHIBA_RBTX4938_MPLEX_NAND
73 This enables the driver for the NAND flash device found on the
74 Toshiba RBTX4938 reference board.
76 config MTD_NAND_AU1550
77 tristate "Au1550 NAND support"
78 depends on SOC_AU1550 && MTD_NAND
80 This enables the driver for the NAND flash controller on the
83 config MTD_NAND_RTC_FROM4
84 tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
85 depends on MTD_NAND && SH_SOLUTION_ENGINE
87 select REED_SOLOMON_DEC8
89 This enables the driver for the Renesas Technology AG-AND
90 flash interface board (FROM_BOARD4)
92 config MTD_NAND_PPCHAMELEONEVB
93 tristate "NAND Flash device on PPChameleonEVB board"
94 depends on PPCHAMELEONEVB && MTD_NAND
96 This enables the NAND flash driver on the PPChameleon EVB Board.
98 config MTD_NAND_S3C2410
99 tristate "NAND Flash support for S3C2410 SoC"
100 depends on ARCH_S3C2410 && MTD_NAND
102 This enables the NAND flash controller on the S3C2410.
104 No board specfic support is done by this driver, each board
105 must advertise a platform_device for the driver to attach.
107 config MTD_NAND_S3C2410_DEBUG
108 bool "S3C2410 NAND driver debug"
109 depends on MTD_NAND_S3C2410
111 Enable debugging of the S3C2410 NAND driver
113 config MTD_NAND_S3C2410_HWECC
114 bool "S3C2410 NAND Hardware ECC"
115 depends on MTD_NAND_S3C2410
117 Enable the use of the S3C2410's internal ECC generator when
118 using NAND. Early versions of the chip have had problems with
119 incorrect ECC generation, and if using these, the default of
120 software ECC is preferable.
122 If you lay down a device with the hardware ECC, then you will
123 currently not be able to switch to software, as there is no
124 implementation for ECC method used by the S3C2410
126 config MTD_NAND_DISKONCHIP
127 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
128 depends on MTD_NAND && EXPERIMENTAL
130 select REED_SOLOMON_DEC16
132 This is a reimplementation of M-Systems DiskOnChip 2000,
133 Millennium and Millennium Plus as a standard NAND device driver,
134 as opposed to the earlier self-contained MTD device drivers.
135 This should enable, among other things, proper JFFS2 operation on
138 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
139 bool "Advanced detection options for DiskOnChip"
140 depends on MTD_NAND_DISKONCHIP
142 This option allows you to specify nonstandard address at which to
143 probe for a DiskOnChip, or to change the detection options. You
144 are unlikely to need any of this unless you are using LinuxBIOS.
147 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
148 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
149 depends on MTD_NAND_DISKONCHIP
152 By default, the probe for DiskOnChip devices will look for a
153 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
154 This option allows you to specify a single address at which to probe
155 for the device, which is useful if you have other devices in that
156 range which get upset when they are probed.
158 (Note that on PowerPC, the normal probe will only check at
161 Normally, you should leave this set to zero, to allow the probe at
162 the normal addresses.
164 config MTD_NAND_DISKONCHIP_PROBE_HIGH
165 bool "Probe high addresses"
166 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
168 By default, the probe for DiskOnChip devices will look for a
169 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
170 This option changes to make it probe between 0xFFFC8000 and
171 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
172 useful to you. Say 'N'.
174 config MTD_NAND_DISKONCHIP_BBTWRITE
175 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
176 depends on MTD_NAND_DISKONCHIP
178 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
179 and 2000 TSOP/Alon), Linux reserves some space at the end of the
180 device for the Bad Block Table (BBT). If you have existing INFTL
181 data on your device (created by non-Linux tools such as M-Systems'
182 DOS drivers), your data might overlap the area Linux wants to use for
183 the BBT. If this is a concern for you, leave this option disabled and
184 Linux will not write BBT data into this area.
185 The downside of leaving this option disabled is that if bad blocks
186 are detected by Linux, they will not be recorded in the BBT, which
187 could cause future problems.
188 Once you enable this option, new filesystems (INFTL or others, created
189 in Linux or other operating systems) will not use the reserved area.
190 The only reason not to enable this option is to prevent damage to
191 preexisting filesystems.
192 Even if you leave this disabled, you can enable BBT writes at module
193 load time (assuming you build diskonchip as a module) with the module
194 parameter "inftl_bbt_write=1".