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_ECC_SMC
27 bool "NAND ECC Smart Media byte order"
31 Software ECC according to the Smart Media Specification.
32 The original Linux implementation had byte 0 and 1 swapped.
34 config MTD_NAND_AUTCPU12
35 tristate "SmartMediaCard on autronix autcpu12 board"
36 depends on MTD_NAND && ARCH_AUTCPU12
38 This enables the driver for the autronix autcpu12 board to
39 access the SmartMediaCard.
41 config MTD_NAND_EDB7312
42 tristate "Support for Cirrus Logic EBD7312 evaluation board"
43 depends on MTD_NAND && ARCH_EDB7312
45 This enables the driver for the Cirrus Logic EBD7312 evaluation
46 board to access the onboard NAND Flash.
49 tristate "iPAQ H1900 flash"
50 depends on MTD_NAND && ARCH_PXA && MTD_PARTITIONS
52 This enables the driver for the iPAQ h1900 flash.
55 tristate "NAND Flash device on SPIA board"
56 depends on ARCH_P720T && MTD_NAND
58 If you had to ask, you don't have one. Say 'N'.
60 config MTD_NAND_AMS_DELTA
61 tristate "NAND Flash device on Amstrad E3"
62 depends on MACH_AMS_DELTA && MTD_NAND
64 Support for NAND flash on Amstrad E3 (Delta).
67 tristate "NAND Flash device on TOTO board"
68 depends on ARCH_OMAP && MTD_NAND
70 Support for NAND flash on Texas Instruments Toto platform.
72 config MTD_NAND_TS7250
73 tristate "NAND Flash device on TS-7250 board"
74 depends on MACH_TS72XX && MTD_NAND
76 Support for NAND flash on Technologic Systems TS-7250 platform.
81 config MTD_NAND_AU1550
82 tristate "Au1550/1200 NAND support"
83 depends on (SOC_AU1200 || SOC_AU1550) && MTD_NAND
85 This enables the driver for the NAND flash controller on the
88 config MTD_NAND_RTC_FROM4
89 tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
90 depends on MTD_NAND && SH_SOLUTION_ENGINE
92 select REED_SOLOMON_DEC8
94 This enables the driver for the Renesas Technology AG-AND
95 flash interface board (FROM_BOARD4)
97 config MTD_NAND_PPCHAMELEONEVB
98 tristate "NAND Flash device on PPChameleonEVB board"
99 depends on PPCHAMELEONEVB && MTD_NAND
101 This enables the NAND flash driver on the PPChameleon EVB Board.
103 config MTD_NAND_S3C2410
104 tristate "NAND Flash support for S3C2410/S3C2440 SoC"
105 depends on ARCH_S3C2410 && MTD_NAND
107 This enables the NAND flash controller on the S3C2410 and S3C2440
110 No board specific support is done by this driver, each board
111 must advertise a platform_device for the driver to attach.
113 config MTD_NAND_S3C2410_DEBUG
114 bool "S3C2410 NAND driver debug"
115 depends on MTD_NAND_S3C2410
117 Enable debugging of the S3C2410 NAND driver
119 config MTD_NAND_S3C2410_HWECC
120 bool "S3C2410 NAND Hardware ECC"
121 depends on MTD_NAND_S3C2410
123 Enable the use of the S3C2410's internal ECC generator when
124 using NAND. Early versions of the chip have had problems with
125 incorrect ECC generation, and if using these, the default of
126 software ECC is preferable.
128 If you lay down a device with the hardware ECC, then you will
129 currently not be able to switch to software, as there is no
130 implementation for ECC method used by the S3C2410
132 config MTD_NAND_DISKONCHIP
133 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
134 depends on MTD_NAND && EXPERIMENTAL
136 select REED_SOLOMON_DEC16
138 This is a reimplementation of M-Systems DiskOnChip 2000,
139 Millennium and Millennium Plus as a standard NAND device driver,
140 as opposed to the earlier self-contained MTD device drivers.
141 This should enable, among other things, proper JFFS2 operation on
144 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
145 bool "Advanced detection options for DiskOnChip"
146 depends on MTD_NAND_DISKONCHIP
148 This option allows you to specify nonstandard address at which to
149 probe for a DiskOnChip, or to change the detection options. You
150 are unlikely to need any of this unless you are using LinuxBIOS.
153 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
154 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
155 depends on MTD_NAND_DISKONCHIP
158 By default, the probe for DiskOnChip devices will look for a
159 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
160 This option allows you to specify a single address at which to probe
161 for the device, which is useful if you have other devices in that
162 range which get upset when they are probed.
164 (Note that on PowerPC, the normal probe will only check at
167 Normally, you should leave this set to zero, to allow the probe at
168 the normal addresses.
170 config MTD_NAND_DISKONCHIP_PROBE_HIGH
171 bool "Probe high addresses"
172 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
174 By default, the probe for DiskOnChip devices will look for a
175 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
176 This option changes to make it probe between 0xFFFC8000 and
177 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
178 useful to you. Say 'N'.
180 config MTD_NAND_DISKONCHIP_BBTWRITE
181 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
182 depends on MTD_NAND_DISKONCHIP
184 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
185 and 2000 TSOP/Alon), Linux reserves some space at the end of the
186 device for the Bad Block Table (BBT). If you have existing INFTL
187 data on your device (created by non-Linux tools such as M-Systems'
188 DOS drivers), your data might overlap the area Linux wants to use for
189 the BBT. If this is a concern for you, leave this option disabled and
190 Linux will not write BBT data into this area.
191 The downside of leaving this option disabled is that if bad blocks
192 are detected by Linux, they will not be recorded in the BBT, which
193 could cause future problems.
194 Once you enable this option, new filesystems (INFTL or others, created
195 in Linux or other operating systems) will not use the reserved area.
196 The only reason not to enable this option is to prevent damage to
197 preexisting filesystems.
198 Even if you leave this disabled, you can enable BBT writes at module
199 load time (assuming you build diskonchip as a module) with the module
200 parameter "inftl_bbt_write=1".
202 config MTD_NAND_SHARPSL
203 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
204 depends on MTD_NAND && ARCH_PXA
206 config MTD_NAND_CS553X
207 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
208 depends on MTD_NAND && X86_PC && PCI
210 The CS553x companion chips for the AMD Geode processor
211 include NAND flash controllers with built-in hardware ECC
212 capabilities; enabling this option will allow you to use
213 these. The driver will check the MSRs to verify that the
214 controller is enabled for NAND, and currently requires that
215 the controller be in MMIO mode.
217 If you say "m", the module will be called "cs553x_nand.ko".
219 config MTD_NAND_NANDSIM
220 tristate "Support for NAND Flash Simulator"
221 depends on MTD_NAND && MTD_PARTITIONS
223 The simulator may simulate various NAND flash chips for the