4 config MTD_NAND_ECC_SMC
5 bool "NAND ECC Smart Media byte order"
6 depends on MTD_NAND_ECC
9 Software ECC according to the Smart Media Specification.
10 The original Linux implementation had byte 0 and 1 swapped.
14 tristate "NAND Device Support"
19 This enables support for accessing all type of NAND flash
20 devices. For further information see
21 <http://www.linux-mtd.infradead.org/doc/nand.html>.
25 config MTD_NAND_VERIFY_WRITE
26 bool "Verify NAND page writes"
28 This adds an extra check when data is written to the flash. The
29 NAND flash device internally checks only bits transitioning
30 from 1 to 0. There is a rare possibility that even though the
31 device thinks the write was successful, a bit could have been
32 flipped accidentally due to device wear or something else.
37 depends on MTD_NAND_ECC_BCH
40 config MTD_NAND_ECC_BCH
41 bool "Support software BCH ECC"
44 This enables support for software BCH error correction. Binary BCH
45 codes are more powerful and cpu intensive than traditional Hamming
46 ECC codes. They are used with NAND devices requiring more than 1 bit
53 config MTD_NAND_MUSEUM_IDS
54 bool "Enable chip ids for obsolete ancient NAND devices"
57 Enable this option only when your board has first generation
58 NAND chips (page size 256 byte, erase size 4-8KiB). The IDs
59 of these chips were reused by later, larger chips.
61 config MTD_NAND_AUTCPU12
62 tristate "SmartMediaCard on autronix autcpu12 board"
63 depends on ARCH_AUTCPU12
65 This enables the driver for the autronix autcpu12 board to
66 access the SmartMediaCard.
68 config MTD_NAND_DENALI
70 tristate "Support Denali NAND controller on Intel Moorestown"
72 Enable the driver for NAND flash on Intel Moorestown, using the
73 Denali NAND controller core.
75 config MTD_NAND_DENALI_SCRATCH_REG_ADDR
76 hex "Denali NAND size scratch register address"
78 depends on MTD_NAND_DENALI
80 Some platforms place the NAND chip size in a scratch register
81 because (some versions of) the driver aren't able to automatically
82 determine the size of certain chips. Set the address of the
83 scratch register here to enable this feature. On Intel Moorestown
84 boards, the scratch register is at 0xFF108018.
86 config MTD_NAND_EDB7312
87 tristate "Support for Cirrus Logic EBD7312 evaluation board"
88 depends on ARCH_EDB7312
90 This enables the driver for the Cirrus Logic EBD7312 evaluation
91 board to access the onboard NAND Flash.
94 tristate "iPAQ H1900 flash"
95 depends on ARCH_PXA && MTD_PARTITIONS
97 This enables the driver for the iPAQ h1900 flash.
100 tristate "GPIO NAND Flash driver"
101 depends on GENERIC_GPIO && ARM
103 This enables a GPIO based NAND flash driver.
106 tristate "NAND Flash device on SPIA board"
107 depends on ARCH_P720T
109 If you had to ask, you don't have one. Say 'N'.
111 config MTD_NAND_AMS_DELTA
112 tristate "NAND Flash device on Amstrad E3"
113 depends on MACH_AMS_DELTA
116 Support for NAND flash on Amstrad E3 (Delta).
118 config MTD_NAND_OMAP2
119 tristate "NAND Flash device on OMAP2 and OMAP3"
120 depends on ARM && (ARCH_OMAP2 || ARCH_OMAP3)
122 Support for NAND flash on Texas Instruments OMAP2 and OMAP3 platforms.
127 config MTD_NAND_RICOH
128 tristate "Ricoh xD card reader"
133 Enable support for Ricoh R5C852 xD card reader
134 You also need to enable ether
135 NAND SSFDC (SmartMedia) read only translation layer' or new
136 expermental, readwrite
137 'SmartMedia/xD new translation layer'
139 config MTD_NAND_AU1550
140 tristate "Au1550/1200 NAND support"
141 depends on SOC_AU1200 || SOC_AU1550
143 This enables the driver for the NAND flash controller on the
144 AMD/Alchemy 1550 SOC.
146 config MTD_NAND_BF5XX
147 tristate "Blackfin on-chip NAND Flash Controller driver"
148 depends on BF54x || BF52x
150 This enables the Blackfin on-chip NAND flash controller
152 No board specific support is done by this driver, each board
153 must advertise a platform_device for the driver to attach.
155 This driver can also be built as a module. If so, the module
156 will be called bf5xx-nand.
158 config MTD_NAND_BF5XX_HWECC
159 bool "BF5XX NAND Hardware ECC"
161 depends on MTD_NAND_BF5XX
163 Enable the use of the BF5XX's internal ECC generator when
166 config MTD_NAND_BF5XX_BOOTROM_ECC
167 bool "Use Blackfin BootROM ECC Layout"
169 depends on MTD_NAND_BF5XX_HWECC
171 If you wish to modify NAND pages and allow the Blackfin on-chip
172 BootROM to boot from them, say Y here. This is only necessary
173 if you are booting U-Boot out of NAND and you wish to update
174 U-Boot from Linux' userspace. Otherwise, you should say N here.
178 config MTD_NAND_RTC_FROM4
179 tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
180 depends on SH_SOLUTION_ENGINE
182 select REED_SOLOMON_DEC8
185 This enables the driver for the Renesas Technology AG-AND
186 flash interface board (FROM_BOARD4)
188 config MTD_NAND_PPCHAMELEONEVB
189 tristate "NAND Flash device on PPChameleonEVB board"
190 depends on PPCHAMELEONEVB && BROKEN
192 This enables the NAND flash driver on the PPChameleon EVB Board.
194 config MTD_NAND_S3C2410
195 tristate "NAND Flash support for Samsung S3C SoCs"
196 depends on ARCH_S3C2410 || ARCH_S3C64XX
198 This enables the NAND flash controller on the S3C24xx and S3C64xx
201 No board specific support is done by this driver, each board
202 must advertise a platform_device for the driver to attach.
204 config MTD_NAND_S3C2410_DEBUG
205 bool "Samsung S3C NAND driver debug"
206 depends on MTD_NAND_S3C2410
208 Enable debugging of the S3C NAND driver
210 config MTD_NAND_S3C2410_HWECC
211 bool "Samsung S3C NAND Hardware ECC"
212 depends on MTD_NAND_S3C2410
214 Enable the use of the controller's internal ECC generator when
215 using NAND. Early versions of the chips have had problems with
216 incorrect ECC generation, and if using these, the default of
217 software ECC is preferable.
220 tristate "NDFC NanD Flash Controller"
222 select MTD_NAND_ECC_SMC
224 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
226 config MTD_NAND_S3C2410_CLKSTOP
227 bool "Samsung S3C NAND IDLE clock stop"
228 depends on MTD_NAND_S3C2410
231 Stop the clock to the NAND controller when there is no chip
232 selected to save power. This will mean there is a small delay
233 when the is NAND chip selected or released, but will save
234 approximately 5mA of power when there is nothing happening.
236 config MTD_NAND_BCM_UMI
237 tristate "NAND Flash support for BCM Reference Boards"
238 depends on ARCH_BCMRING
240 This enables the NAND flash controller on the BCM UMI block.
242 No board specific support is done by this driver, each board
243 must advertise a platform_device for the driver to attach.
245 config MTD_NAND_BCM_UMI_HWCS
246 bool "BCM UMI NAND Hardware CS"
247 depends on MTD_NAND_BCM_UMI
249 Enable the use of the BCM UMI block's internal CS using NAND.
250 This should only be used if you know the external NAND CS can toggle.
252 config MTD_NAND_DISKONCHIP
253 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
254 depends on EXPERIMENTAL
256 select REED_SOLOMON_DEC16
258 This is a reimplementation of M-Systems DiskOnChip 2000,
259 Millennium and Millennium Plus as a standard NAND device driver,
260 as opposed to the earlier self-contained MTD device drivers.
261 This should enable, among other things, proper JFFS2 operation on
264 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
265 bool "Advanced detection options for DiskOnChip"
266 depends on MTD_NAND_DISKONCHIP
268 This option allows you to specify nonstandard address at which to
269 probe for a DiskOnChip, or to change the detection options. You
270 are unlikely to need any of this unless you are using LinuxBIOS.
273 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
274 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
275 depends on MTD_NAND_DISKONCHIP
278 By default, the probe for DiskOnChip devices will look for a
279 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
280 This option allows you to specify a single address at which to probe
281 for the device, which is useful if you have other devices in that
282 range which get upset when they are probed.
284 (Note that on PowerPC, the normal probe will only check at
287 Normally, you should leave this set to zero, to allow the probe at
288 the normal addresses.
290 config MTD_NAND_DISKONCHIP_PROBE_HIGH
291 bool "Probe high addresses"
292 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
294 By default, the probe for DiskOnChip devices will look for a
295 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
296 This option changes to make it probe between 0xFFFC8000 and
297 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
298 useful to you. Say 'N'.
300 config MTD_NAND_DISKONCHIP_BBTWRITE
301 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
302 depends on MTD_NAND_DISKONCHIP
304 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
305 and 2000 TSOP/Alon), Linux reserves some space at the end of the
306 device for the Bad Block Table (BBT). If you have existing INFTL
307 data on your device (created by non-Linux tools such as M-Systems'
308 DOS drivers), your data might overlap the area Linux wants to use for
309 the BBT. If this is a concern for you, leave this option disabled and
310 Linux will not write BBT data into this area.
311 The downside of leaving this option disabled is that if bad blocks
312 are detected by Linux, they will not be recorded in the BBT, which
313 could cause future problems.
314 Once you enable this option, new filesystems (INFTL or others, created
315 in Linux or other operating systems) will not use the reserved area.
316 The only reason not to enable this option is to prevent damage to
317 preexisting filesystems.
318 Even if you leave this disabled, you can enable BBT writes at module
319 load time (assuming you build diskonchip as a module) with the module
320 parameter "inftl_bbt_write=1".
322 config MTD_NAND_SHARPSL
323 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
327 tristate "NAND support for OLPC CAFÉ chip"
330 select REED_SOLOMON_DEC16
332 Use NAND flash attached to the CAFÉ chip designed for the OLPC
335 config MTD_NAND_CS553X
336 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
339 The CS553x companion chips for the AMD Geode processor
340 include NAND flash controllers with built-in hardware ECC
341 capabilities; enabling this option will allow you to use
342 these. The driver will check the MSRs to verify that the
343 controller is enabled for NAND, and currently requires that
344 the controller be in MMIO mode.
346 If you say "m", the module will be called cs553x_nand.
348 config MTD_NAND_ATMEL
349 tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
350 depends on ARCH_AT91 || AVR32
352 Enables support for NAND Flash / Smart Media Card interface
353 on Atmel AT91 and AVR32 processors.
355 prompt "ECC management for NAND Flash / SmartMedia on AT91 / AVR32"
356 depends on MTD_NAND_ATMEL
358 config MTD_NAND_ATMEL_ECC_HW
360 depends on ARCH_AT91SAM9263 || ARCH_AT91SAM9260 || AVR32
362 Use hardware ECC instead of software ECC when the chip
365 The hardware ECC controller is capable of single bit error
366 correction and 2-bit random detection per page.
368 NB : hardware and software ECC schemes are incompatible.
369 If you switch from one to another, you'll have to erase your
374 config MTD_NAND_ATMEL_ECC_SOFT
379 NB : hardware and software ECC schemes are incompatible.
380 If you switch from one to another, you'll have to erase your
383 config MTD_NAND_ATMEL_ECC_NONE
384 bool "No ECC (testing only, DANGEROUS)"
385 depends on DEBUG_KERNEL
388 It's not a good idea and it should be reserved for testing
395 config MTD_NAND_PXA3xx
396 tristate "Support for NAND flash devices on PXA3xx"
397 depends on PXA3xx || ARCH_MMP
399 This enables the driver for the NAND flash device found on
402 config MTD_NAND_CM_X270
403 tristate "Support for NAND Flash on CM-X270 modules"
404 depends on MACH_ARMCORE
406 config MTD_NAND_PASEMI
407 tristate "NAND support for PA Semi PWRficient"
408 depends on PPC_PASEMI
410 Enables support for NAND Flash interface on PA Semi PWRficient
414 tristate "NAND Flash device on Toshiba Mobile IO Controller"
417 Support for NAND flash connected to a Toshiba Mobile IO
418 Controller in some PDAs, including the Sharp SL6000x.
420 config MTD_NAND_NANDSIM
421 tristate "Support for NAND Flash Simulator"
422 depends on MTD_PARTITIONS
424 The simulator may simulate various NAND flash chips for the
427 config MTD_NAND_PLATFORM
428 tristate "Support for generic platform NAND driver"
430 This implements a generic NAND driver for on-SOC platform
431 devices. You will need to provide platform-specific functions
435 tristate "MTD driver for Olympus MAUSB-10 and Fujifilm DPC-R1"
438 These two (and possibly other) Alauda-based cardreaders for
439 SmartMedia and xD allow raw flash access.
441 config MTD_NAND_ORION
442 tristate "NAND Flash support for Marvell Orion SoC"
443 depends on PLAT_ORION
445 This enables the NAND flash controller on Orion machines.
447 No board specific support is done by this driver, each board
448 must advertise a platform_device for the driver to attach.
450 config MTD_NAND_FSL_ELBC
451 tristate "NAND support for Freescale eLBC controllers"
455 Various Freescale chips, including the 8313, include a NAND Flash
456 Controller Module with built-in hardware ECC capabilities.
457 Enabling this option will enable you to use this to control
458 external NAND devices.
460 config MTD_NAND_FSL_UPM
461 tristate "Support for NAND on Freescale UPM"
462 depends on PPC_83xx || PPC_85xx
465 Enables support for NAND Flash chips wired onto Freescale PowerPC
466 processor localbus with User-Programmable Machine support.
468 config MTD_NAND_MPC5121_NFC
469 tristate "MPC5121 built-in NAND Flash Controller support"
470 depends on PPC_MPC512x
472 This enables the driver for the NAND flash controller on the
476 tristate "MXC NAND support"
477 depends on IMX_HAVE_PLATFORM_MXC_NAND
479 This enables the driver for the NAND flash controller on the
482 config MTD_NAND_NOMADIK
483 tristate "ST Nomadik 8815 NAND support"
484 depends on ARCH_NOMADIK
486 Driver for the NAND flash controller on the Nomadik, with ECC.
488 config MTD_NAND_SH_FLCTL
489 tristate "Support for NAND on Renesas SuperH FLCTL"
490 depends on SUPERH || ARCH_SHMOBILE
492 Several Renesas SuperH CPU has FLCTL. This option enables support
493 for NAND Flash using FLCTL.
495 config MTD_NAND_DAVINCI
496 tristate "Support NAND on DaVinci SoC"
497 depends on ARCH_DAVINCI
499 Enable the driver for NAND flash chips on Texas Instruments
502 config MTD_NAND_TXX9NDFMC
503 tristate "NAND Flash support for TXx9 SoC"
504 depends on SOC_TX4938 || SOC_TX4939
506 This enables the NAND flash controller on the TXx9 SoCs.
508 config MTD_NAND_SOCRATES
509 tristate "Support for NAND on Socrates board"
512 Enables support for NAND Flash chips wired onto Socrates board.
514 config MTD_NAND_NUC900
515 tristate "Support for NAND on Nuvoton NUC9xx/w90p910 evaluation boards."
516 depends on ARCH_W90X900 && MTD_PARTITIONS
518 This enables the driver for the NAND Flash on evaluation board based
521 config MTD_NAND_JZ4740
522 tristate "Support for JZ4740 SoC NAND controller"
523 depends on MACH_JZ4740
525 Enables support for NAND Flash on JZ4740 SoC based boards.
528 tristate "Support for NAND on ST Micros FSMC"
529 depends on PLAT_SPEAR || PLAT_NOMADIK || MACH_U300
531 Enables support for NAND Flash chips on the ST Microelectronics
532 Flexible Static Memory Controller (FSMC)