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 "GPIO NAND Flash driver"
61 depends on GENERIC_GPIO && ARM
63 This enables a GPIO based NAND flash driver.
66 tristate "NAND Flash device on SPIA board"
69 If you had to ask, you don't have one. Say 'N'.
71 config MTD_NAND_AMS_DELTA
72 tristate "NAND Flash device on Amstrad E3"
73 depends on MACH_AMS_DELTA
75 Support for NAND flash on Amstrad E3 (Delta).
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"
108 depends on MTD_NAND_BF5XX
110 Enable the use of the BF5XX's internal ECC generator when
113 config MTD_NAND_BF5XX_BOOTROM_ECC
114 bool "Use Blackfin BootROM ECC Layout"
116 depends on MTD_NAND_BF5XX_HWECC
118 If you wish to modify NAND pages and allow the Blackfin on-chip
119 BootROM to boot from them, say Y here. This is only necessary
120 if you are booting U-Boot out of NAND and you wish to update
121 U-Boot from Linux' userspace. Otherwise, you should say N here.
125 config MTD_NAND_RTC_FROM4
126 tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
127 depends on SH_SOLUTION_ENGINE
129 select REED_SOLOMON_DEC8
132 This enables the driver for the Renesas Technology AG-AND
133 flash interface board (FROM_BOARD4)
135 config MTD_NAND_PPCHAMELEONEVB
136 tristate "NAND Flash device on PPChameleonEVB board"
137 depends on PPCHAMELEONEVB && BROKEN
139 This enables the NAND flash driver on the PPChameleon EVB Board.
141 config MTD_NAND_S3C2410
142 tristate "NAND Flash support for S3C2410/S3C2440 SoC"
143 depends on ARCH_S3C2410
145 This enables the NAND flash controller on the S3C2410 and S3C2440
148 No board specific support is done by this driver, each board
149 must advertise a platform_device for the driver to attach.
151 config MTD_NAND_S3C2410_DEBUG
152 bool "S3C2410 NAND driver debug"
153 depends on MTD_NAND_S3C2410
155 Enable debugging of the S3C2410 NAND driver
157 config MTD_NAND_S3C2410_HWECC
158 bool "S3C2410 NAND Hardware ECC"
159 depends on MTD_NAND_S3C2410
161 Enable the use of the S3C2410's internal ECC generator when
162 using NAND. Early versions of the chip have had problems with
163 incorrect ECC generation, and if using these, the default of
164 software ECC is preferable.
167 tristate "NDFC NanD Flash Controller"
169 select MTD_NAND_ECC_SMC
171 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
173 config MTD_NAND_S3C2410_CLKSTOP
174 bool "S3C2410 NAND IDLE clock stop"
175 depends on MTD_NAND_S3C2410
178 Stop the clock to the NAND controller when there is no chip
179 selected to save power. This will mean there is a small delay
180 when the is NAND chip selected or released, but will save
181 approximately 5mA of power when there is nothing happening.
183 config MTD_NAND_DISKONCHIP
184 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
185 depends on EXPERIMENTAL
187 select REED_SOLOMON_DEC16
189 This is a reimplementation of M-Systems DiskOnChip 2000,
190 Millennium and Millennium Plus as a standard NAND device driver,
191 as opposed to the earlier self-contained MTD device drivers.
192 This should enable, among other things, proper JFFS2 operation on
195 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
196 bool "Advanced detection options for DiskOnChip"
197 depends on MTD_NAND_DISKONCHIP
199 This option allows you to specify nonstandard address at which to
200 probe for a DiskOnChip, or to change the detection options. You
201 are unlikely to need any of this unless you are using LinuxBIOS.
204 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
205 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
206 depends on MTD_NAND_DISKONCHIP
209 By default, the probe for DiskOnChip devices will look for a
210 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
211 This option allows you to specify a single address at which to probe
212 for the device, which is useful if you have other devices in that
213 range which get upset when they are probed.
215 (Note that on PowerPC, the normal probe will only check at
218 Normally, you should leave this set to zero, to allow the probe at
219 the normal addresses.
221 config MTD_NAND_DISKONCHIP_PROBE_HIGH
222 bool "Probe high addresses"
223 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
225 By default, the probe for DiskOnChip devices will look for a
226 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
227 This option changes to make it probe between 0xFFFC8000 and
228 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
229 useful to you. Say 'N'.
231 config MTD_NAND_DISKONCHIP_BBTWRITE
232 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
233 depends on MTD_NAND_DISKONCHIP
235 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
236 and 2000 TSOP/Alon), Linux reserves some space at the end of the
237 device for the Bad Block Table (BBT). If you have existing INFTL
238 data on your device (created by non-Linux tools such as M-Systems'
239 DOS drivers), your data might overlap the area Linux wants to use for
240 the BBT. If this is a concern for you, leave this option disabled and
241 Linux will not write BBT data into this area.
242 The downside of leaving this option disabled is that if bad blocks
243 are detected by Linux, they will not be recorded in the BBT, which
244 could cause future problems.
245 Once you enable this option, new filesystems (INFTL or others, created
246 in Linux or other operating systems) will not use the reserved area.
247 The only reason not to enable this option is to prevent damage to
248 preexisting filesystems.
249 Even if you leave this disabled, you can enable BBT writes at module
250 load time (assuming you build diskonchip as a module) with the module
251 parameter "inftl_bbt_write=1".
253 config MTD_NAND_SHARPSL
254 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
257 config MTD_NAND_BASLER_EXCITE
258 tristate "Support for NAND Flash on Basler eXcite"
259 depends on BASLER_EXCITE
261 This enables the driver for the NAND flash device found on the
262 Basler eXcite Smart Camera. If built as a module, the driver
263 will be named excite_nandflash.
266 tristate "NAND support for OLPC CAFÉ chip"
269 select REED_SOLOMON_DEC16
271 Use NAND flash attached to the CAFÉ chip designed for the OLPC
274 config MTD_NAND_CS553X
275 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
278 The CS553x companion chips for the AMD Geode processor
279 include NAND flash controllers with built-in hardware ECC
280 capabilities; enabling this option will allow you to use
281 these. The driver will check the MSRs to verify that the
282 controller is enabled for NAND, and currently requires that
283 the controller be in MMIO mode.
285 If you say "m", the module will be called cs553x_nand.
287 config MTD_NAND_ATMEL
288 tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
289 depends on ARCH_AT91 || AVR32
291 Enables support for NAND Flash / Smart Media Card interface
292 on Atmel AT91 and AVR32 processors.
294 prompt "ECC management for NAND Flash / SmartMedia on AT91 / AVR32"
295 depends on MTD_NAND_ATMEL
297 config MTD_NAND_ATMEL_ECC_HW
299 depends on ARCH_AT91SAM9263 || ARCH_AT91SAM9260 || AVR32
301 Use hardware ECC instead of software ECC when the chip
304 The hardware ECC controller is capable of single bit error
305 correction and 2-bit random detection per page.
307 NB : hardware and software ECC schemes are incompatible.
308 If you switch from one to another, you'll have to erase your
313 config MTD_NAND_ATMEL_ECC_SOFT
318 NB : hardware and software ECC schemes are incompatible.
319 If you switch from one to another, you'll have to erase your
322 config MTD_NAND_ATMEL_ECC_NONE
323 bool "No ECC (testing only, DANGEROUS)"
324 depends on DEBUG_KERNEL
327 It's not a good idea and it should be reserved for testing
336 config MTD_NAND_PXA3xx
337 tristate "Support for NAND flash devices on PXA3xx"
338 depends on MTD_NAND && PXA3xx
340 This enables the driver for the NAND flash device found on
343 config MTD_NAND_PXA3xx_BUILTIN
344 bool "Use builtin definitions for some NAND chips (deprecated)"
345 depends on MTD_NAND_PXA3xx
347 This enables builtin definitions for some NAND chips. This
348 is deprecated in favor of platform specific data.
350 config MTD_NAND_CM_X270
351 tristate "Support for NAND Flash on CM-X270 modules"
352 depends on MTD_NAND && MACH_ARMCORE
354 config MTD_NAND_PASEMI
355 tristate "NAND support for PA Semi PWRficient"
356 depends on MTD_NAND && PPC_PASEMI
358 Enables support for NAND Flash interface on PA Semi PWRficient
362 tristate "NAND Flash device on Toshiba Mobile IO Controller"
363 depends on MTD_NAND && MFD_TMIO
365 Support for NAND flash connected to a Toshiba Mobile IO
366 Controller in some PDAs, including the Sharp SL6000x.
368 config MTD_NAND_NANDSIM
369 tristate "Support for NAND Flash Simulator"
370 depends on MTD_PARTITIONS
372 The simulator may simulate various NAND flash chips for the
375 config MTD_NAND_PLATFORM
376 tristate "Support for generic platform NAND driver"
379 This implements a generic NAND driver for on-SOC platform
380 devices. You will need to provide platform-specific functions
384 tristate "MTD driver for Olympus MAUSB-10 and Fujifilm DPC-R1"
385 depends on MTD_NAND && USB
387 These two (and possibly other) Alauda-based cardreaders for
388 SmartMedia and xD allow raw flash access.
390 config MTD_NAND_ORION
391 tristate "NAND Flash support for Marvell Orion SoC"
392 depends on PLAT_ORION && MTD_NAND
394 This enables the NAND flash controller on Orion machines.
396 No board specific support is done by this driver, each board
397 must advertise a platform_device for the driver to attach.
399 config MTD_NAND_FSL_ELBC
400 tristate "NAND support for Freescale eLBC controllers"
401 depends on MTD_NAND && PPC_OF
403 Various Freescale chips, including the 8313, include a NAND Flash
404 Controller Module with built-in hardware ECC capabilities.
405 Enabling this option will enable you to use this to control
406 external NAND devices.
408 config MTD_NAND_FSL_UPM
409 tristate "Support for NAND on Freescale UPM"
410 depends on MTD_NAND && (PPC_83xx || PPC_85xx)
413 Enables support for NAND Flash chips wired onto Freescale PowerPC
414 processor localbus with User-Programmable Machine support.
417 tristate "MXC NAND support"
418 depends on ARCH_MX2 || ARCH_MX3
420 This enables the driver for the NAND flash controller on the
423 config MTD_NAND_SH_FLCTL
424 tristate "Support for NAND on Renesas SuperH FLCTL"
425 depends on MTD_NAND && SUPERH && CPU_SUBTYPE_SH7723
427 Several Renesas SuperH CPU has FLCTL. This option enables support
428 for NAND Flash using FLCTL. This driver support SH7723.
430 config MTD_NAND_DAVINCI
431 tristate "Support NAND on DaVinci SoC"
432 depends on ARCH_DAVINCI
434 Enable the driver for NAND flash chips on Texas Instruments
437 config MTD_NAND_TXX9NDFMC
438 tristate "NAND Flash support for TXx9 SoC"
439 depends on SOC_TX4938 || SOC_TX4939
441 This enables the NAND flash controller on the TXx9 SoCs.
443 config MTD_NAND_SOCRATES
444 tristate "Support for NAND on Socrates board"
445 depends on MTD_NAND && SOCRATES
447 Enables support for NAND Flash chips wired onto Socrates board.