1 # drivers/mtd/nand/Kconfig
2 # $Id: Kconfig,v 1.35 2005/11/07 11:14:30 gleixner Exp $
4 menu "NAND Flash Device Drivers"
8 tristate "NAND Device Support"
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>.
16 config MTD_NAND_VERIFY_WRITE
17 bool "Verify NAND page writes"
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.
26 config MTD_NAND_AUTCPU12
27 tristate "SmartMediaCard on autronix autcpu12 board"
28 depends on MTD_NAND && ARCH_AUTCPU12
30 This enables the driver for the autronix autcpu12 board to
31 access the SmartMediaCard.
33 config MTD_NAND_EDB7312
34 tristate "Support for Cirrus Logic EBD7312 evaluation board"
35 depends on MTD_NAND && ARCH_EDB7312
37 This enables the driver for the Cirrus Logic EBD7312 evaluation
38 board to access the onboard NAND Flash.
41 tristate "iPAQ H1900 flash"
42 depends on MTD_NAND && ARCH_PXA && MTD_PARTITIONS
44 This enables the driver for the iPAQ h1900 flash.
47 tristate "NAND Flash device on SPIA board"
48 depends on ARCH_P720T && MTD_NAND
50 If you had to ask, you don't have one. Say 'N'.
52 config MTD_NAND_AMS_DELTA
53 tristate "NAND Flash device on Amstrad E3"
54 depends on MACH_AMS_DELTA && MTD_NAND
56 Support for NAND flash on Amstrad E3 (Delta).
59 tristate "NAND Flash device on TOTO board"
60 depends on ARCH_OMAP && MTD_NAND
62 Support for NAND flash on Texas Instruments Toto platform.
64 config MTD_NAND_TS7250
65 tristate "NAND Flash device on TS-7250 board"
66 depends on MACH_TS72XX && MTD_NAND
68 Support for NAND flash on Technologic Systems TS-7250 platform.
73 config MTD_NAND_AU1550
74 tristate "Au1550/1200 NAND support"
75 depends on (SOC_AU1200 || SOC_AU1550) && MTD_NAND
77 This enables the driver for the NAND flash controller on the
80 config MTD_NAND_RTC_FROM4
81 tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
82 depends on MTD_NAND && SH_SOLUTION_ENGINE
84 select REED_SOLOMON_DEC8
86 This enables the driver for the Renesas Technology AG-AND
87 flash interface board (FROM_BOARD4)
89 config MTD_NAND_PPCHAMELEONEVB
90 tristate "NAND Flash device on PPChameleonEVB board"
91 depends on PPCHAMELEONEVB && MTD_NAND
93 This enables the NAND flash driver on the PPChameleon EVB Board.
95 config MTD_NAND_S3C2410
96 tristate "NAND Flash support for S3C2410/S3C2440 SoC"
97 depends on ARCH_S3C2410 && MTD_NAND
99 This enables the NAND flash controller on the S3C2410 and S3C2440
102 No board specific support is done by this driver, each board
103 must advertise a platform_device for the driver to attach.
105 config MTD_NAND_S3C2410_DEBUG
106 bool "S3C2410 NAND driver debug"
107 depends on MTD_NAND_S3C2410
109 Enable debugging of the S3C2410 NAND driver
111 config MTD_NAND_S3C2410_HWECC
112 bool "S3C2410 NAND Hardware ECC"
113 depends on MTD_NAND_S3C2410
115 Enable the use of the S3C2410's internal ECC generator when
116 using NAND. Early versions of the chip have had problems with
117 incorrect ECC generation, and if using these, the default of
118 software ECC is preferable.
120 If you lay down a device with the hardware ECC, then you will
121 currently not be able to switch to software, as there is no
122 implementation for ECC method used by the S3C2410
124 config MTD_NAND_DISKONCHIP
125 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
126 depends on MTD_NAND && EXPERIMENTAL
128 select REED_SOLOMON_DEC16
130 This is a reimplementation of M-Systems DiskOnChip 2000,
131 Millennium and Millennium Plus as a standard NAND device driver,
132 as opposed to the earlier self-contained MTD device drivers.
133 This should enable, among other things, proper JFFS2 operation on
136 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
137 bool "Advanced detection options for DiskOnChip"
138 depends on MTD_NAND_DISKONCHIP
140 This option allows you to specify nonstandard address at which to
141 probe for a DiskOnChip, or to change the detection options. You
142 are unlikely to need any of this unless you are using LinuxBIOS.
145 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
146 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
147 depends on MTD_NAND_DISKONCHIP
150 By default, the probe for DiskOnChip devices will look for a
151 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
152 This option allows you to specify a single address at which to probe
153 for the device, which is useful if you have other devices in that
154 range which get upset when they are probed.
156 (Note that on PowerPC, the normal probe will only check at
159 Normally, you should leave this set to zero, to allow the probe at
160 the normal addresses.
162 config MTD_NAND_DISKONCHIP_PROBE_HIGH
163 bool "Probe high addresses"
164 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
166 By default, the probe for DiskOnChip devices will look for a
167 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
168 This option changes to make it probe between 0xFFFC8000 and
169 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
170 useful to you. Say 'N'.
172 config MTD_NAND_DISKONCHIP_BBTWRITE
173 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
174 depends on MTD_NAND_DISKONCHIP
176 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
177 and 2000 TSOP/Alon), Linux reserves some space at the end of the
178 device for the Bad Block Table (BBT). If you have existing INFTL
179 data on your device (created by non-Linux tools such as M-Systems'
180 DOS drivers), your data might overlap the area Linux wants to use for
181 the BBT. If this is a concern for you, leave this option disabled and
182 Linux will not write BBT data into this area.
183 The downside of leaving this option disabled is that if bad blocks
184 are detected by Linux, they will not be recorded in the BBT, which
185 could cause future problems.
186 Once you enable this option, new filesystems (INFTL or others, created
187 in Linux or other operating systems) will not use the reserved area.
188 The only reason not to enable this option is to prevent damage to
189 preexisting filesystems.
190 Even if you leave this disabled, you can enable BBT writes at module
191 load time (assuming you build diskonchip as a module) with the module
192 parameter "inftl_bbt_write=1".
194 config MTD_NAND_SHARPSL
195 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
196 depends on MTD_NAND && ARCH_PXA
198 config MTD_NAND_CS553X
199 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
200 depends on MTD_NAND && X86_PC && PCI
202 The CS553x companion chips for the AMD Geode processor
203 include NAND flash controllers with built-in hardware ECC
204 capabilities; enabling this option will allow you to use
205 these. The driver will check the MSRs to verify that the
206 controller is enabled for NAND, and currently requires that
207 the controller be in MMIO mode.
209 If you say "m", the module will be called "cs553x_nand.ko".
211 config MTD_NAND_NANDSIM
212 tristate "Support for NAND Flash Simulator"
213 depends on MTD_NAND && MTD_PARTITIONS
215 The simulator may simulate various NAND flash chips for the