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).
78 tristate "NAND Flash device on OMAP2 and OMAP3"
79 depends on ARM && MTD_NAND && (ARCH_OMAP2 || ARCH_OMAP3)
81 Support for NAND flash on Texas Instruments OMAP2 and OMAP3 platforms.
84 tristate "NAND Flash device on OMAP H3/H2/P2 boards"
85 depends on ARM && ARCH_OMAP1 && MTD_NAND && (MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_PERSEUS2)
87 Support for NAND flash on Texas Instruments H3/H2/P2 platforms.
89 config MTD_NAND_OMAP_HW
90 bool "OMAP HW NAND Flash controller support"
91 depends on ARM && ARCH_OMAP16XX && MTD_NAND
94 Driver for TI OMAP16xx hardware NAND flash controller.
97 tristate "NAND Flash device on TOTO board"
98 depends on ARCH_OMAP && BROKEN
100 Support for NAND flash on Texas Instruments Toto platform.
102 config MTD_NAND_TS7250
103 tristate "NAND Flash device on TS-7250 board"
104 depends on MACH_TS72XX
106 Support for NAND flash on Technologic Systems TS-7250 platform.
111 config MTD_NAND_AU1550
112 tristate "Au1550/1200 NAND support"
113 depends on SOC_AU1200 || SOC_AU1550
115 This enables the driver for the NAND flash controller on the
116 AMD/Alchemy 1550 SOC.
118 config MTD_NAND_BF5XX
119 tristate "Blackfin on-chip NAND Flash Controller driver"
120 depends on (BF54x || BF52x) && MTD_NAND
122 This enables the Blackfin on-chip NAND flash controller
124 No board specific support is done by this driver, each board
125 must advertise a platform_device for the driver to attach.
127 This driver can also be built as a module. If so, the module
128 will be called bf5xx-nand.
130 config MTD_NAND_BF5XX_HWECC
131 bool "BF5XX NAND Hardware ECC"
133 depends on MTD_NAND_BF5XX
135 Enable the use of the BF5XX's internal ECC generator when
138 config MTD_NAND_BF5XX_BOOTROM_ECC
139 bool "Use Blackfin BootROM ECC Layout"
141 depends on MTD_NAND_BF5XX_HWECC
143 If you wish to modify NAND pages and allow the Blackfin on-chip
144 BootROM to boot from them, say Y here. This is only necessary
145 if you are booting U-Boot out of NAND and you wish to update
146 U-Boot from Linux' userspace. Otherwise, you should say N here.
150 config MTD_NAND_RTC_FROM4
151 tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
152 depends on SH_SOLUTION_ENGINE
154 select REED_SOLOMON_DEC8
157 This enables the driver for the Renesas Technology AG-AND
158 flash interface board (FROM_BOARD4)
160 config MTD_NAND_PPCHAMELEONEVB
161 tristate "NAND Flash device on PPChameleonEVB board"
162 depends on PPCHAMELEONEVB && BROKEN
164 This enables the NAND flash driver on the PPChameleon EVB Board.
166 config MTD_NAND_S3C2410
167 tristate "NAND Flash support for S3C2410/S3C2440 SoC"
168 depends on ARCH_S3C2410
170 This enables the NAND flash controller on the S3C2410 and S3C2440
173 No board specific support is done by this driver, each board
174 must advertise a platform_device for the driver to attach.
176 config MTD_NAND_S3C2410_DEBUG
177 bool "S3C2410 NAND driver debug"
178 depends on MTD_NAND_S3C2410
180 Enable debugging of the S3C2410 NAND driver
182 config MTD_NAND_S3C2410_HWECC
183 bool "S3C2410 NAND Hardware ECC"
184 depends on MTD_NAND_S3C2410
186 Enable the use of the S3C2410's internal ECC generator when
187 using NAND. Early versions of the chip have had problems with
188 incorrect ECC generation, and if using these, the default of
189 software ECC is preferable.
191 config MTD_NAND_S3C2410_CLKSTOP
192 bool "S3C2410 NAND IDLE clock stop"
193 depends on MTD_NAND_S3C2410
196 Stop the clock to the NAND controller when there is no chip
197 selected to save power. This will mean there is a small delay
198 when the is NAND chip selected or released, but will save
199 approximately 5mA of power when there is nothing happening.
201 config MTD_NAND_DISKONCHIP
202 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
203 depends on EXPERIMENTAL
205 select REED_SOLOMON_DEC16
207 This is a reimplementation of M-Systems DiskOnChip 2000,
208 Millennium and Millennium Plus as a standard NAND device driver,
209 as opposed to the earlier self-contained MTD device drivers.
210 This should enable, among other things, proper JFFS2 operation on
213 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
214 bool "Advanced detection options for DiskOnChip"
215 depends on MTD_NAND_DISKONCHIP
217 This option allows you to specify nonstandard address at which to
218 probe for a DiskOnChip, or to change the detection options. You
219 are unlikely to need any of this unless you are using LinuxBIOS.
222 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
223 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
224 depends on MTD_NAND_DISKONCHIP
227 By default, the probe for DiskOnChip devices will look for a
228 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
229 This option allows you to specify a single address at which to probe
230 for the device, which is useful if you have other devices in that
231 range which get upset when they are probed.
233 (Note that on PowerPC, the normal probe will only check at
236 Normally, you should leave this set to zero, to allow the probe at
237 the normal addresses.
239 config MTD_NAND_DISKONCHIP_PROBE_HIGH
240 bool "Probe high addresses"
241 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
243 By default, the probe for DiskOnChip devices will look for a
244 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
245 This option changes to make it probe between 0xFFFC8000 and
246 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
247 useful to you. Say 'N'.
249 config MTD_NAND_DISKONCHIP_BBTWRITE
250 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
251 depends on MTD_NAND_DISKONCHIP
253 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
254 and 2000 TSOP/Alon), Linux reserves some space at the end of the
255 device for the Bad Block Table (BBT). If you have existing INFTL
256 data on your device (created by non-Linux tools such as M-Systems'
257 DOS drivers), your data might overlap the area Linux wants to use for
258 the BBT. If this is a concern for you, leave this option disabled and
259 Linux will not write BBT data into this area.
260 The downside of leaving this option disabled is that if bad blocks
261 are detected by Linux, they will not be recorded in the BBT, which
262 could cause future problems.
263 Once you enable this option, new filesystems (INFTL or others, created
264 in Linux or other operating systems) will not use the reserved area.
265 The only reason not to enable this option is to prevent damage to
266 preexisting filesystems.
267 Even if you leave this disabled, you can enable BBT writes at module
268 load time (assuming you build diskonchip as a module) with the module
269 parameter "inftl_bbt_write=1".
271 config MTD_NAND_SHARPSL
272 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
275 config MTD_NAND_BASLER_EXCITE
276 tristate "Support for NAND Flash on Basler eXcite"
277 depends on BASLER_EXCITE
279 This enables the driver for the NAND flash device found on the
280 Basler eXcite Smart Camera. If built as a module, the driver
281 will be named "excite_nandflash.ko".
284 tristate "NAND support for OLPC CAFÉ chip"
287 select REED_SOLOMON_DEC16
289 Use NAND flash attached to the CAFÉ chip designed for the OLPC
292 config MTD_NAND_CS553X
293 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
294 depends on X86_32 && (X86_PC || X86_GENERICARCH)
296 The CS553x companion chips for the AMD Geode processor
297 include NAND flash controllers with built-in hardware ECC
298 capabilities; enabling this option will allow you to use
299 these. The driver will check the MSRs to verify that the
300 controller is enabled for NAND, and currently requires that
301 the controller be in MMIO mode.
303 If you say "m", the module will be called "cs553x_nand.ko".
305 config MTD_NAND_ATMEL
306 tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
307 depends on ARCH_AT91 || AVR32
309 Enables support for NAND Flash / Smart Media Card interface
310 on Atmel AT91 and AVR32 processors.
312 prompt "ECC management for NAND Flash / SmartMedia on AT91 / AVR32"
313 depends on MTD_NAND_ATMEL
315 config MTD_NAND_ATMEL_ECC_HW
317 depends on ARCH_AT91SAM9263 || ARCH_AT91SAM9260 || AVR32
319 Use hardware ECC instead of software ECC when the chip
322 The hardware ECC controller is capable of single bit error
323 correction and 2-bit random detection per page.
325 NB : hardware and software ECC schemes are incompatible.
326 If you switch from one to another, you'll have to erase your
331 config MTD_NAND_ATMEL_ECC_SOFT
336 NB : hardware and software ECC schemes are incompatible.
337 If you switch from one to another, you'll have to erase your
340 config MTD_NAND_ATMEL_ECC_NONE
341 bool "No ECC (testing only, DANGEROUS)"
342 depends on DEBUG_KERNEL
345 It's not a good idea and it should be reserved for testing
354 config MTD_NAND_PXA3xx
355 bool "Support for NAND flash devices on PXA3xx"
356 depends on MTD_NAND && PXA3xx
358 This enables the driver for the NAND flash device found on
361 config MTD_NAND_PXA3xx_BUILTIN
362 bool "Use builtin definitions for some NAND chips (deprecated)"
363 depends on MTD_NAND_PXA3xx
365 This enables builtin definitions for some NAND chips. This
366 is deprecated in favor of platform specific data.
368 config MTD_NAND_CM_X270
369 tristate "Support for NAND Flash on CM-X270 modules"
370 depends on MTD_NAND && MACH_ARMCORE
372 config MTD_NAND_PASEMI
373 tristate "NAND support for PA Semi PWRficient"
374 depends on MTD_NAND && PPC_PASEMI
376 Enables support for NAND Flash interface on PA Semi PWRficient
380 tristate "NAND Flash device on Toshiba Mobile IO Controller"
381 depends on MTD_NAND && MFD_TMIO
383 Support for NAND flash connected to a Toshiba Mobile IO
384 Controller in some PDAs, including the Sharp SL6000x.
386 config MTD_NAND_NANDSIM
387 tristate "Support for NAND Flash Simulator"
388 depends on MTD_PARTITIONS
390 The simulator may simulate various NAND flash chips for the
393 config MTD_NAND_PLATFORM
394 tristate "Support for generic platform NAND driver"
397 This implements a generic NAND driver for on-SOC platform
398 devices. You will need to provide platform-specific functions
402 tristate "MTD driver for Olympus MAUSB-10 and Fujifilm DPC-R1"
403 depends on MTD_NAND && USB
405 These two (and possibly other) Alauda-based cardreaders for
406 SmartMedia and xD allow raw flash access.
408 config MTD_NAND_ORION
409 tristate "NAND Flash support for Marvell Orion SoC"
410 depends on PLAT_ORION && MTD_NAND
412 This enables the NAND flash controller on Orion machines.
414 No board specific support is done by this driver, each board
415 must advertise a platform_device for the driver to attach.
417 config MTD_NAND_FSL_ELBC
418 tristate "NAND support for Freescale eLBC controllers"
419 depends on MTD_NAND && PPC_OF
421 Various Freescale chips, including the 8313, include a NAND Flash
422 Controller Module with built-in hardware ECC capabilities.
423 Enabling this option will enable you to use this to control
424 external NAND devices.
426 config MTD_NAND_FSL_UPM
427 tristate "Support for NAND on Freescale UPM"
428 depends on MTD_NAND && (PPC_83xx || PPC_85xx)
431 Enables support for NAND Flash chips wired onto Freescale PowerPC
432 processor localbus with User-Programmable Machine support.
435 tristate "MXC NAND support"
438 This enables the driver for the NAND flash controller on the
441 config MTD_NAND_SH_FLCTL
442 tristate "Support for NAND on Renesas SuperH FLCTL"
443 depends on MTD_NAND && SUPERH && CPU_SUBTYPE_SH7723
445 Several Renesas SuperH CPU has FLCTL. This option enables support
446 for NAND Flash using FLCTL. This driver support SH7723.