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 OMAP2 and OMAP3"
73 depends on ARM && MTD_NAND && (ARCH_OMAP2 || ARCH_OMAP3)
75 Support for NAND flash on Texas Instruments OMAP2 and OMAP3 platforms.
78 tristate "NAND Flash device on OMAP H3/H2/P2 boards"
79 depends on ARM && ARCH_OMAP1 && MTD_NAND && (MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_PERSEUS2)
81 Support for NAND flash on Texas Instruments H3/H2/P2 platforms.
83 config MTD_NAND_OMAP_HW
84 bool "OMAP HW NAND Flash controller support"
85 depends on ARM && ARCH_OMAP16XX && MTD_NAND
88 Driver for TI OMAP16xx hardware NAND flash controller.
91 tristate "NAND Flash device on TOTO board"
92 depends on ARCH_OMAP && BROKEN
94 Support for NAND flash on Texas Instruments Toto platform.
96 config MTD_NAND_TS7250
97 tristate "NAND Flash device on TS-7250 board"
98 depends on MACH_TS72XX
100 Support for NAND flash on Technologic Systems TS-7250 platform.
105 config MTD_NAND_AU1550
106 tristate "Au1550/1200 NAND support"
107 depends on SOC_AU1200 || SOC_AU1550
109 This enables the driver for the NAND flash controller on the
110 AMD/Alchemy 1550 SOC.
112 config MTD_NAND_BF5XX
113 tristate "Blackfin on-chip NAND Flash Controller driver"
114 depends on (BF54x || BF52x) && MTD_NAND
116 This enables the Blackfin on-chip NAND flash controller
118 No board specific support is done by this driver, each board
119 must advertise a platform_device for the driver to attach.
121 This driver can also be built as a module. If so, the module
122 will be called bf5xx-nand.
124 config MTD_NAND_BF5XX_HWECC
125 bool "BF5XX NAND Hardware ECC"
127 depends on MTD_NAND_BF5XX
129 Enable the use of the BF5XX's internal ECC generator when
132 config MTD_NAND_BF5XX_BOOTROM_ECC
133 bool "Use Blackfin BootROM ECC Layout"
135 depends on MTD_NAND_BF5XX_HWECC
137 If you wish to modify NAND pages and allow the Blackfin on-chip
138 BootROM to boot from them, say Y here. This is only necessary
139 if you are booting U-Boot out of NAND and you wish to update
140 U-Boot from Linux' userspace. Otherwise, you should say N here.
144 config MTD_NAND_RTC_FROM4
145 tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
146 depends on SH_SOLUTION_ENGINE
148 select REED_SOLOMON_DEC8
151 This enables the driver for the Renesas Technology AG-AND
152 flash interface board (FROM_BOARD4)
154 config MTD_NAND_PPCHAMELEONEVB
155 tristate "NAND Flash device on PPChameleonEVB board"
156 depends on PPCHAMELEONEVB && BROKEN
158 This enables the NAND flash driver on the PPChameleon EVB Board.
160 config MTD_NAND_S3C2410
161 tristate "NAND Flash support for S3C2410/S3C2440 SoC"
162 depends on ARCH_S3C2410
164 This enables the NAND flash controller on the S3C2410 and S3C2440
167 No board specific support is done by this driver, each board
168 must advertise a platform_device for the driver to attach.
170 config MTD_NAND_S3C2410_DEBUG
171 bool "S3C2410 NAND driver debug"
172 depends on MTD_NAND_S3C2410
174 Enable debugging of the S3C2410 NAND driver
176 config MTD_NAND_S3C2410_HWECC
177 bool "S3C2410 NAND Hardware ECC"
178 depends on MTD_NAND_S3C2410
180 Enable the use of the S3C2410's internal ECC generator when
181 using NAND. Early versions of the chip have had problems with
182 incorrect ECC generation, and if using these, the default of
183 software ECC is preferable.
186 tristate "NDFC NanD Flash Controller"
187 depends on 4xx && !PPC_MERGE
188 select MTD_NAND_ECC_SMC
190 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
192 config MTD_NAND_S3C2410_CLKSTOP
193 bool "S3C2410 NAND IDLE clock stop"
194 depends on MTD_NAND_S3C2410
197 Stop the clock to the NAND controller when there is no chip
198 selected to save power. This will mean there is a small delay
199 when the is NAND chip selected or released, but will save
200 approximately 5mA of power when there is nothing happening.
202 config MTD_NAND_DISKONCHIP
203 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
204 depends on EXPERIMENTAL
206 select REED_SOLOMON_DEC16
208 This is a reimplementation of M-Systems DiskOnChip 2000,
209 Millennium and Millennium Plus as a standard NAND device driver,
210 as opposed to the earlier self-contained MTD device drivers.
211 This should enable, among other things, proper JFFS2 operation on
214 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
215 bool "Advanced detection options for DiskOnChip"
216 depends on MTD_NAND_DISKONCHIP
218 This option allows you to specify nonstandard address at which to
219 probe for a DiskOnChip, or to change the detection options. You
220 are unlikely to need any of this unless you are using LinuxBIOS.
223 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
224 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
225 depends on MTD_NAND_DISKONCHIP
228 By default, the probe for DiskOnChip devices will look for a
229 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
230 This option allows you to specify a single address at which to probe
231 for the device, which is useful if you have other devices in that
232 range which get upset when they are probed.
234 (Note that on PowerPC, the normal probe will only check at
237 Normally, you should leave this set to zero, to allow the probe at
238 the normal addresses.
240 config MTD_NAND_DISKONCHIP_PROBE_HIGH
241 bool "Probe high addresses"
242 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
244 By default, the probe for DiskOnChip devices will look for a
245 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
246 This option changes to make it probe between 0xFFFC8000 and
247 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
248 useful to you. Say 'N'.
250 config MTD_NAND_DISKONCHIP_BBTWRITE
251 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
252 depends on MTD_NAND_DISKONCHIP
254 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
255 and 2000 TSOP/Alon), Linux reserves some space at the end of the
256 device for the Bad Block Table (BBT). If you have existing INFTL
257 data on your device (created by non-Linux tools such as M-Systems'
258 DOS drivers), your data might overlap the area Linux wants to use for
259 the BBT. If this is a concern for you, leave this option disabled and
260 Linux will not write BBT data into this area.
261 The downside of leaving this option disabled is that if bad blocks
262 are detected by Linux, they will not be recorded in the BBT, which
263 could cause future problems.
264 Once you enable this option, new filesystems (INFTL or others, created
265 in Linux or other operating systems) will not use the reserved area.
266 The only reason not to enable this option is to prevent damage to
267 preexisting filesystems.
268 Even if you leave this disabled, you can enable BBT writes at module
269 load time (assuming you build diskonchip as a module) with the module
270 parameter "inftl_bbt_write=1".
272 config MTD_NAND_SHARPSL
273 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
276 config MTD_NAND_BASLER_EXCITE
277 tristate "Support for NAND Flash on Basler eXcite"
278 depends on BASLER_EXCITE
280 This enables the driver for the NAND flash device found on the
281 Basler eXcite Smart Camera. If built as a module, the driver
282 will be named "excite_nandflash.ko".
285 tristate "NAND support for OLPC CAFÉ chip"
288 select REED_SOLOMON_DEC16
290 Use NAND flash attached to the CAFÉ chip designed for the OLPC
293 config MTD_NAND_CS553X
294 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
295 depends on X86_32 && (X86_PC || X86_GENERICARCH)
297 The CS553x companion chips for the AMD Geode processor
298 include NAND flash controllers with built-in hardware ECC
299 capabilities; enabling this option will allow you to use
300 these. The driver will check the MSRs to verify that the
301 controller is enabled for NAND, and currently requires that
302 the controller be in MMIO mode.
304 If you say "m", the module will be called "cs553x_nand.ko".
306 config MTD_NAND_ATMEL
307 tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
308 depends on ARCH_AT91 || AVR32
310 Enables support for NAND Flash / Smart Media Card interface
311 on Atmel AT91 and AVR32 processors.
313 prompt "ECC management for NAND Flash / SmartMedia on AT91 / AVR32"
314 depends on MTD_NAND_ATMEL
316 config MTD_NAND_ATMEL_ECC_HW
318 depends on ARCH_AT91SAM9263 || ARCH_AT91SAM9260 || AVR32
320 Use hardware ECC instead of software ECC when the chip
323 The hardware ECC controller is capable of single bit error
324 correction and 2-bit random detection per page.
326 NB : hardware and software ECC schemes are incompatible.
327 If you switch from one to another, you'll have to erase your
332 config MTD_NAND_ATMEL_ECC_SOFT
337 NB : hardware and software ECC schemes are incompatible.
338 If you switch from one to another, you'll have to erase your
341 config MTD_NAND_ATMEL_ECC_NONE
342 bool "No ECC (testing only, DANGEROUS)"
343 depends on DEBUG_KERNEL
346 It's not a good idea and it should be reserved for testing
355 config MTD_NAND_PXA3xx
356 bool "Support for NAND flash devices on PXA3xx"
357 depends on MTD_NAND && PXA3xx
359 This enables the driver for the NAND flash device found on
362 config MTD_NAND_CM_X270
363 tristate "Support for NAND Flash on CM-X270 modules"
364 depends on MTD_NAND && MACH_ARMCORE
366 config MTD_NAND_PASEMI
367 tristate "NAND support for PA Semi PWRficient"
368 depends on MTD_NAND && PPC_PASEMI
370 Enables support for NAND Flash interface on PA Semi PWRficient
373 config MTD_NAND_NANDSIM
374 tristate "Support for NAND Flash Simulator"
375 depends on MTD_PARTITIONS
377 The simulator may simulate various NAND flash chips for the
380 config MTD_NAND_PLATFORM
381 tristate "Support for generic platform NAND driver"
384 This implements a generic NAND driver for on-SOC platform
385 devices. You will need to provide platform-specific functions
389 tristate "MTD driver for Olympus MAUSB-10 and Fujifilm DPC-R1"
390 depends on MTD_NAND && USB
392 These two (and possibly other) Alauda-based cardreaders for
393 SmartMedia and xD allow raw flash access.
395 config MTD_NAND_ORION
396 tristate "NAND Flash support for Marvell Orion SoC"
397 depends on PLAT_ORION && MTD_NAND
399 This enables the NAND flash controller on Orion machines.
401 No board specific support is done by this driver, each board
402 must advertise a platform_device for the driver to attach.
404 config MTD_NAND_FSL_ELBC
405 tristate "NAND support for Freescale eLBC controllers"
406 depends on MTD_NAND && PPC_OF
408 Various Freescale chips, including the 8313, include a NAND Flash
409 Controller Module with built-in hardware ECC capabilities.
410 Enabling this option will enable you to use this to control
411 external NAND devices.
413 config MTD_NAND_FSL_UPM
414 tristate "Support for NAND on Freescale UPM"
415 depends on MTD_NAND && OF_GPIO && (PPC_83xx || PPC_85xx)
418 Enables support for NAND Flash chips wired onto Freescale PowerPC
419 processor localbus with User-Programmable Machine support.