1 # drivers/mtd/nand/Kconfig
4 tristate "NAND Device Support"
8 This enables support for accessing all type of NAND flash
9 devices. For further information see
10 <http://www.linux-mtd.infradead.org/doc/nand.html>.
14 config MTD_NAND_VERIFY_WRITE
15 bool "Verify NAND page writes"
17 This adds an extra check when data is written to the flash. The
18 NAND flash device internally checks only bits transitioning
19 from 1 to 0. There is a rare possibility that even though the
20 device thinks the write was successful, a bit could have been
21 flipped accidentally due to device wear or something else.
23 config MTD_NAND_ECC_SMC
24 bool "NAND ECC Smart Media byte order"
27 Software ECC according to the Smart Media Specification.
28 The original Linux implementation had byte 0 and 1 swapped.
30 config MTD_NAND_MUSEUM_IDS
31 bool "Enable chip ids for obsolete ancient NAND devices"
35 Enable this option only when your board has first generation
36 NAND chips (page size 256 byte, erase size 4-8KiB). The IDs
37 of these chips were reused by later, larger chips.
39 config MTD_NAND_AUTCPU12
40 tristate "SmartMediaCard on autronix autcpu12 board"
41 depends on ARCH_AUTCPU12
43 This enables the driver for the autronix autcpu12 board to
44 access the SmartMediaCard.
46 config MTD_NAND_EDB7312
47 tristate "Support for Cirrus Logic EBD7312 evaluation board"
48 depends on ARCH_EDB7312
50 This enables the driver for the Cirrus Logic EBD7312 evaluation
51 board to access the onboard NAND Flash.
54 tristate "iPAQ H1900 flash"
55 depends on ARCH_PXA && MTD_PARTITIONS
57 This enables the driver for the iPAQ h1900 flash.
60 tristate "NAND Flash device on SPIA board"
63 If you had to ask, you don't have one. Say 'N'.
65 config MTD_NAND_AMS_DELTA
66 tristate "NAND Flash device on Amstrad E3"
67 depends on MACH_AMS_DELTA
69 Support for NAND flash on Amstrad E3 (Delta).
72 tristate "NAND Flash device on TOTO board"
73 depends on ARCH_OMAP && BROKEN
75 Support for NAND flash on Texas Instruments Toto platform.
77 config MTD_NAND_TS7250
78 tristate "NAND Flash device on TS-7250 board"
79 depends on MACH_TS72XX
81 Support for NAND flash on Technologic Systems TS-7250 platform.
86 config MTD_NAND_AU1550
87 tristate "Au1550/1200 NAND support"
88 depends on SOC_AU1200 || SOC_AU1550
90 This enables the driver for the NAND flash controller on the
94 tristate "Blackfin on-chip NAND Flash Controller driver"
95 depends on (BF54x || BF52x) && MTD_NAND
97 This enables the Blackfin on-chip NAND flash controller
99 No board specific support is done by this driver, each board
100 must advertise a platform_device for the driver to attach.
102 This driver can also be built as a module. If so, the module
103 will be called bf5xx-nand.
105 config MTD_NAND_BF5XX_HWECC
106 bool "BF5XX NAND Hardware ECC"
107 depends on MTD_NAND_BF5XX
109 Enable the use of the BF5XX's internal ECC generator when
112 config MTD_NAND_RTC_FROM4
113 tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
114 depends on SH_SOLUTION_ENGINE
116 select REED_SOLOMON_DEC8
119 This enables the driver for the Renesas Technology AG-AND
120 flash interface board (FROM_BOARD4)
122 config MTD_NAND_PPCHAMELEONEVB
123 tristate "NAND Flash device on PPChameleonEVB board"
124 depends on PPCHAMELEONEVB && BROKEN
126 This enables the NAND flash driver on the PPChameleon EVB Board.
128 config MTD_NAND_S3C2410
129 tristate "NAND Flash support for S3C2410/S3C2440 SoC"
130 depends on ARCH_S3C2410
132 This enables the NAND flash controller on the S3C2410 and S3C2440
135 No board specific support is done by this driver, each board
136 must advertise a platform_device for the driver to attach.
138 config MTD_NAND_S3C2410_DEBUG
139 bool "S3C2410 NAND driver debug"
140 depends on MTD_NAND_S3C2410
142 Enable debugging of the S3C2410 NAND driver
144 config MTD_NAND_S3C2410_HWECC
145 bool "S3C2410 NAND Hardware ECC"
146 depends on MTD_NAND_S3C2410
148 Enable the use of the S3C2410's internal ECC generator when
149 using NAND. Early versions of the chip have had problems with
150 incorrect ECC generation, and if using these, the default of
151 software ECC is preferable.
154 tristate "NDFC NanD Flash Controller"
155 depends on 4xx && !PPC_MERGE
156 select MTD_NAND_ECC_SMC
158 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
160 config MTD_NAND_S3C2410_CLKSTOP
161 bool "S3C2410 NAND IDLE clock stop"
162 depends on MTD_NAND_S3C2410
165 Stop the clock to the NAND controller when there is no chip
166 selected to save power. This will mean there is a small delay
167 when the is NAND chip selected or released, but will save
168 approximately 5mA of power when there is nothing happening.
170 config MTD_NAND_DISKONCHIP
171 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
172 depends on EXPERIMENTAL
174 select REED_SOLOMON_DEC16
176 This is a reimplementation of M-Systems DiskOnChip 2000,
177 Millennium and Millennium Plus as a standard NAND device driver,
178 as opposed to the earlier self-contained MTD device drivers.
179 This should enable, among other things, proper JFFS2 operation on
182 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
183 bool "Advanced detection options for DiskOnChip"
184 depends on MTD_NAND_DISKONCHIP
186 This option allows you to specify nonstandard address at which to
187 probe for a DiskOnChip, or to change the detection options. You
188 are unlikely to need any of this unless you are using LinuxBIOS.
191 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
192 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
193 depends on MTD_NAND_DISKONCHIP
196 By default, the probe for DiskOnChip devices will look for a
197 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
198 This option allows you to specify a single address at which to probe
199 for the device, which is useful if you have other devices in that
200 range which get upset when they are probed.
202 (Note that on PowerPC, the normal probe will only check at
205 Normally, you should leave this set to zero, to allow the probe at
206 the normal addresses.
208 config MTD_NAND_DISKONCHIP_PROBE_HIGH
209 bool "Probe high addresses"
210 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
212 By default, the probe for DiskOnChip devices will look for a
213 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
214 This option changes to make it probe between 0xFFFC8000 and
215 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
216 useful to you. Say 'N'.
218 config MTD_NAND_DISKONCHIP_BBTWRITE
219 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
220 depends on MTD_NAND_DISKONCHIP
222 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
223 and 2000 TSOP/Alon), Linux reserves some space at the end of the
224 device for the Bad Block Table (BBT). If you have existing INFTL
225 data on your device (created by non-Linux tools such as M-Systems'
226 DOS drivers), your data might overlap the area Linux wants to use for
227 the BBT. If this is a concern for you, leave this option disabled and
228 Linux will not write BBT data into this area.
229 The downside of leaving this option disabled is that if bad blocks
230 are detected by Linux, they will not be recorded in the BBT, which
231 could cause future problems.
232 Once you enable this option, new filesystems (INFTL or others, created
233 in Linux or other operating systems) will not use the reserved area.
234 The only reason not to enable this option is to prevent damage to
235 preexisting filesystems.
236 Even if you leave this disabled, you can enable BBT writes at module
237 load time (assuming you build diskonchip as a module) with the module
238 parameter "inftl_bbt_write=1".
240 config MTD_NAND_SHARPSL
241 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
244 config MTD_NAND_BASLER_EXCITE
245 tristate "Support for NAND Flash on Basler eXcite"
246 depends on BASLER_EXCITE
248 This enables the driver for the NAND flash device found on the
249 Basler eXcite Smart Camera. If built as a module, the driver
250 will be named "excite_nandflash.ko".
253 tristate "NAND support for OLPC CAFÉ chip"
256 select REED_SOLOMON_DEC16
258 Use NAND flash attached to the CAFÉ chip designed for the OLPC
261 config MTD_NAND_CS553X
262 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
263 depends on X86_32 && (X86_PC || X86_GENERICARCH)
265 The CS553x companion chips for the AMD Geode processor
266 include NAND flash controllers with built-in hardware ECC
267 capabilities; enabling this option will allow you to use
268 these. The driver will check the MSRs to verify that the
269 controller is enabled for NAND, and currently requires that
270 the controller be in MMIO mode.
272 If you say "m", the module will be called "cs553x_nand.ko".
274 config MTD_NAND_ATMEL
275 tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
276 depends on ARCH_AT91 || AVR32
278 Enables support for NAND Flash / Smart Media Card interface
279 on Atmel AT91 and AVR32 processors.
281 prompt "ECC management for NAND Flash / SmartMedia on AT91 / AVR32"
282 depends on MTD_NAND_ATMEL
284 config MTD_NAND_ATMEL_ECC_HW
286 depends on ARCH_AT91SAM9263 || ARCH_AT91SAM9260 || AVR32
288 Use hardware ECC instead of software ECC when the chip
291 The hardware ECC controller is capable of single bit error
292 correction and 2-bit random detection per page.
294 NB : hardware and software ECC schemes are incompatible.
295 If you switch from one to another, you'll have to erase your
300 config MTD_NAND_ATMEL_ECC_SOFT
305 NB : hardware and software ECC schemes are incompatible.
306 If you switch from one to another, you'll have to erase your
309 config MTD_NAND_ATMEL_ECC_NONE
310 bool "No ECC (testing only, DANGEROUS)"
311 depends on DEBUG_KERNEL
314 It's not a good idea and it should be reserved for testing
323 config MTD_NAND_PXA3xx
324 bool "Support for NAND flash devices on PXA3xx"
325 depends on MTD_NAND && PXA3xx
327 This enables the driver for the NAND flash device found on
330 config MTD_NAND_CM_X270
331 tristate "Support for NAND Flash on CM-X270 modules"
332 depends on MTD_NAND && MACH_ARMCORE
334 config MTD_NAND_PASEMI
335 tristate "NAND support for PA Semi PWRficient"
336 depends on MTD_NAND && PPC_PASEMI
338 Enables support for NAND Flash interface on PA Semi PWRficient
341 config MTD_NAND_NANDSIM
342 tristate "Support for NAND Flash Simulator"
343 depends on MTD_PARTITIONS
345 The simulator may simulate various NAND flash chips for the
348 config MTD_NAND_PLATFORM
349 tristate "Support for generic platform NAND driver"
352 This implements a generic NAND driver for on-SOC platform
353 devices. You will need to provide platform-specific functions
357 tristate "MTD driver for Olympus MAUSB-10 and Fujifilm DPC-R1"
358 depends on MTD_NAND && USB
360 These two (and possibly other) Alauda-based cardreaders for
361 SmartMedia and xD allow raw flash access.
363 config MTD_NAND_ORION
364 tristate "NAND Flash support for Marvell Orion SoC"
365 depends on PLAT_ORION && MTD_NAND
367 This enables the NAND flash controller on Orion machines.
369 No board specific support is done by this driver, each board
370 must advertise a platform_device for the driver to attach.
372 config MTD_NAND_FSL_ELBC
373 tristate "NAND support for Freescale eLBC controllers"
374 depends on MTD_NAND && PPC_OF
376 Various Freescale chips, including the 8313, include a NAND Flash
377 Controller Module with built-in hardware ECC capabilities.
378 Enabling this option will enable you to use this to control
379 external NAND devices.
381 config MTD_NAND_FSL_UPM
382 tristate "Support for NAND on Freescale UPM"
383 depends on MTD_NAND && OF_GPIO && (PPC_83xx || PPC_85xx)
386 Enables support for NAND Flash chips wired onto Freescale PowerPC
387 processor localbus with User-Programmable Machine support.