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>.
28 depends on MTD_NAND_ECC_BCH
31 config MTD_NAND_ECC_BCH
32 bool "Support software BCH ECC"
35 This enables support for software BCH error correction. Binary BCH
36 codes are more powerful and cpu intensive than traditional Hamming
37 ECC codes. They are used with NAND devices requiring more than 1 bit
44 config MTD_NAND_MUSEUM_IDS
45 bool "Enable chip ids for obsolete ancient NAND devices"
48 Enable this option only when your board has first generation
49 NAND chips (page size 256 byte, erase size 4-8KiB). The IDs
50 of these chips were reused by later, larger chips.
52 config MTD_NAND_DENALI
54 tristate "Support Denali NAND controller on Intel Moorestown"
56 Enable the driver for NAND flash on Intel Moorestown, using the
57 Denali NAND controller core.
59 config MTD_NAND_DENALI_SCRATCH_REG_ADDR
60 hex "Denali NAND size scratch register address"
62 depends on MTD_NAND_DENALI
64 Some platforms place the NAND chip size in a scratch register
65 because (some versions of) the driver aren't able to automatically
66 determine the size of certain chips. Set the address of the
67 scratch register here to enable this feature. On Intel Moorestown
68 boards, the scratch register is at 0xFF108018.
71 tristate "iPAQ H1900 flash"
72 depends on ARCH_PXA && BROKEN
74 This enables the driver for the iPAQ h1900 flash.
77 tristate "GPIO NAND Flash driver"
78 depends on GENERIC_GPIO && ARM
80 This enables a GPIO based NAND flash driver.
82 config MTD_NAND_AMS_DELTA
83 tristate "NAND Flash device on Amstrad E3"
84 depends on MACH_AMS_DELTA
87 Support for NAND flash on Amstrad E3 (Delta).
90 tristate "NAND Flash device on OMAP2, OMAP3 and OMAP4"
91 depends on ARCH_OMAP2PLUS
93 Support for NAND flash on Texas Instruments OMAP2, OMAP3 and OMAP4
96 config MTD_NAND_OMAP_BCH
97 depends on MTD_NAND && MTD_NAND_OMAP2 && ARCH_OMAP3
98 bool "Enable support for hardware BCH error correction"
101 select BCH_CONST_PARAMS
103 Support for hardware BCH error correction.
106 prompt "BCH error correction capability"
107 depends on MTD_NAND_OMAP_BCH
109 config MTD_NAND_OMAP_BCH8
110 bool "8 bits / 512 bytes (recommended)"
112 Support correcting up to 8 bitflips per 512-byte block.
113 This will use 13 bytes of spare area per 512 bytes of page data.
114 This is the recommended mode, as 4-bit mode does not work
115 on some OMAP3 revisions, due to a hardware bug.
117 config MTD_NAND_OMAP_BCH4
118 bool "4 bits / 512 bytes"
120 Support correcting up to 4 bitflips per 512-byte block.
121 This will use 7 bytes of spare area per 512 bytes of page data.
122 Note that this mode does not work on some OMAP3 revisions, due to a
123 hardware bug. Please check your OMAP datasheet before selecting this
132 default 4 if MTD_NAND_OMAP_BCH4
133 default 8 if MTD_NAND_OMAP_BCH8
139 config MTD_NAND_RICOH
140 tristate "Ricoh xD card reader"
145 Enable support for Ricoh R5C852 xD card reader
146 You also need to enable ether
147 NAND SSFDC (SmartMedia) read only translation layer' or new
148 expermental, readwrite
149 'SmartMedia/xD new translation layer'
151 config MTD_NAND_AU1550
152 tristate "Au1550/1200 NAND support"
153 depends on MIPS_ALCHEMY
155 This enables the driver for the NAND flash controller on the
156 AMD/Alchemy 1550 SOC.
158 config MTD_NAND_BF5XX
159 tristate "Blackfin on-chip NAND Flash Controller driver"
160 depends on BF54x || BF52x
162 This enables the Blackfin on-chip NAND flash controller
164 No board specific support is done by this driver, each board
165 must advertise a platform_device for the driver to attach.
167 This driver can also be built as a module. If so, the module
168 will be called bf5xx-nand.
170 config MTD_NAND_BF5XX_HWECC
171 bool "BF5XX NAND Hardware ECC"
173 depends on MTD_NAND_BF5XX
175 Enable the use of the BF5XX's internal ECC generator when
178 config MTD_NAND_BF5XX_BOOTROM_ECC
179 bool "Use Blackfin BootROM ECC Layout"
181 depends on MTD_NAND_BF5XX_HWECC
183 If you wish to modify NAND pages and allow the Blackfin on-chip
184 BootROM to boot from them, say Y here. This is only necessary
185 if you are booting U-Boot out of NAND and you wish to update
186 U-Boot from Linux' userspace. Otherwise, you should say N here.
190 config MTD_NAND_RTC_FROM4
191 tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
192 depends on SH_SOLUTION_ENGINE
194 select REED_SOLOMON_DEC8
197 This enables the driver for the Renesas Technology AG-AND
198 flash interface board (FROM_BOARD4)
200 config MTD_NAND_PPCHAMELEONEVB
201 tristate "NAND Flash device on PPChameleonEVB board"
202 depends on PPCHAMELEONEVB && BROKEN
204 This enables the NAND flash driver on the PPChameleon EVB Board.
206 config MTD_NAND_S3C2410
207 tristate "NAND Flash support for Samsung S3C SoCs"
208 depends on ARCH_S3C24XX || ARCH_S3C64XX
210 This enables the NAND flash controller on the S3C24xx and S3C64xx
213 No board specific support is done by this driver, each board
214 must advertise a platform_device for the driver to attach.
216 config MTD_NAND_S3C2410_DEBUG
217 bool "Samsung S3C NAND driver debug"
218 depends on MTD_NAND_S3C2410
220 Enable debugging of the S3C NAND driver
222 config MTD_NAND_S3C2410_HWECC
223 bool "Samsung S3C NAND Hardware ECC"
224 depends on MTD_NAND_S3C2410
226 Enable the use of the controller's internal ECC generator when
227 using NAND. Early versions of the chips have had problems with
228 incorrect ECC generation, and if using these, the default of
229 software ECC is preferable.
232 tristate "NDFC NanD Flash Controller"
234 select MTD_NAND_ECC_SMC
236 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
238 config MTD_NAND_S3C2410_CLKSTOP
239 bool "Samsung S3C NAND IDLE clock stop"
240 depends on MTD_NAND_S3C2410
243 Stop the clock to the NAND controller when there is no chip
244 selected to save power. This will mean there is a small delay
245 when the is NAND chip selected or released, but will save
246 approximately 5mA of power when there is nothing happening.
248 config MTD_NAND_DISKONCHIP
249 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
250 depends on EXPERIMENTAL
253 select REED_SOLOMON_DEC16
255 This is a reimplementation of M-Systems DiskOnChip 2000,
256 Millennium and Millennium Plus as a standard NAND device driver,
257 as opposed to the earlier self-contained MTD device drivers.
258 This should enable, among other things, proper JFFS2 operation on
261 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
262 bool "Advanced detection options for DiskOnChip"
263 depends on MTD_NAND_DISKONCHIP
265 This option allows you to specify nonstandard address at which to
266 probe for a DiskOnChip, or to change the detection options. You
267 are unlikely to need any of this unless you are using LinuxBIOS.
270 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
271 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
272 depends on MTD_NAND_DISKONCHIP
275 By default, the probe for DiskOnChip devices will look for a
276 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
277 This option allows you to specify a single address at which to probe
278 for the device, which is useful if you have other devices in that
279 range which get upset when they are probed.
281 (Note that on PowerPC, the normal probe will only check at
284 Normally, you should leave this set to zero, to allow the probe at
285 the normal addresses.
287 config MTD_NAND_DISKONCHIP_PROBE_HIGH
288 bool "Probe high addresses"
289 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
291 By default, the probe for DiskOnChip devices will look for a
292 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
293 This option changes to make it probe between 0xFFFC8000 and
294 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
295 useful to you. Say 'N'.
297 config MTD_NAND_DISKONCHIP_BBTWRITE
298 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
299 depends on MTD_NAND_DISKONCHIP
301 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
302 and 2000 TSOP/Alon), Linux reserves some space at the end of the
303 device for the Bad Block Table (BBT). If you have existing INFTL
304 data on your device (created by non-Linux tools such as M-Systems'
305 DOS drivers), your data might overlap the area Linux wants to use for
306 the BBT. If this is a concern for you, leave this option disabled and
307 Linux will not write BBT data into this area.
308 The downside of leaving this option disabled is that if bad blocks
309 are detected by Linux, they will not be recorded in the BBT, which
310 could cause future problems.
311 Once you enable this option, new filesystems (INFTL or others, created
312 in Linux or other operating systems) will not use the reserved area.
313 The only reason not to enable this option is to prevent damage to
314 preexisting filesystems.
315 Even if you leave this disabled, you can enable BBT writes at module
316 load time (assuming you build diskonchip as a module) with the module
317 parameter "inftl_bbt_write=1".
319 config MTD_NAND_DOCG4
320 tristate "Support for DiskOnChip G4 (EXPERIMENTAL)"
321 depends on EXPERIMENTAL && HAS_IOMEM
325 Support for diskonchip G4 nand flash, found in various smartphones and
326 PDAs, among them the Palm Treo680, HTC Prophet and Wizard, Toshiba
327 Portege G900, Asus P526, and O2 XDA Zinc.
329 With this driver you will be able to use UBI and create a ubifs on the
330 device, so you may wish to consider enabling UBI and UBIFS as well.
332 These devices ship with the Mys/Sandisk SAFTL formatting, for which
333 there is currently no mtd parser, so you may want to use command line
334 partitioning to segregate write-protected blocks. On the Treo680, the
335 first five erase blocks (256KiB each) are write-protected, followed
336 by the block containing the saftl partition table. This is probably
339 config MTD_NAND_SHARPSL
340 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
344 tristate "NAND support for OLPC CAFÉ chip"
347 select REED_SOLOMON_DEC16
349 Use NAND flash attached to the CAFÉ chip designed for the OLPC
352 config MTD_NAND_CS553X
353 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
356 The CS553x companion chips for the AMD Geode processor
357 include NAND flash controllers with built-in hardware ECC
358 capabilities; enabling this option will allow you to use
359 these. The driver will check the MSRs to verify that the
360 controller is enabled for NAND, and currently requires that
361 the controller be in MMIO mode.
363 If you say "m", the module will be called cs553x_nand.
365 config MTD_NAND_ATMEL
366 tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
367 depends on ARCH_AT91 || AVR32
369 Enables support for NAND Flash / Smart Media Card interface
370 on Atmel AT91 and AVR32 processors.
372 config MTD_NAND_PXA3xx
373 tristate "Support for NAND flash devices on PXA3xx"
374 depends on PXA3xx || ARCH_MMP
376 This enables the driver for the NAND flash device found on
379 config MTD_NAND_SLC_LPC32XX
380 tristate "NXP LPC32xx SLC Controller"
381 depends on ARCH_LPC32XX
383 Enables support for NXP's LPC32XX SLC (i.e. for Single Level Cell
384 chips) NAND controller. This is the default for the PHYTEC 3250
385 reference board which contains a NAND256R3A2CZA6 chip.
387 Please check the actual NAND chip connected and its support
388 by the SLC NAND controller.
390 config MTD_NAND_MLC_LPC32XX
391 tristate "NXP LPC32xx MLC Controller"
392 depends on ARCH_LPC32XX
394 Uses the LPC32XX MLC (i.e. for Multi Level Cell chips) NAND
395 controller. This is the default for the WORK92105 controller
398 Please check the actual NAND chip connected and its support
399 by the MLC NAND controller.
401 config MTD_NAND_CM_X270
402 tristate "Support for NAND Flash on CM-X270 modules"
403 depends on MACH_ARMCORE
405 config MTD_NAND_PASEMI
406 tristate "NAND support for PA Semi PWRficient"
407 depends on PPC_PASEMI
409 Enables support for NAND Flash interface on PA Semi PWRficient
413 tristate "NAND Flash device on Toshiba Mobile IO Controller"
416 Support for NAND flash connected to a Toshiba Mobile IO
417 Controller in some PDAs, including the Sharp SL6000x.
419 config MTD_NAND_NANDSIM
420 tristate "Support for NAND Flash Simulator"
422 The simulator may simulate various NAND flash chips for the
425 config MTD_NAND_GPMI_NAND
426 tristate "GPMI NAND Flash Controller driver"
427 depends on MTD_NAND && MXS_DMA
429 Enables NAND Flash support for IMX23, IMX28 or IMX6.
430 The GPMI controller is very powerful, with the help of BCH
431 module, it can do the hardware ECC. The GPMI supports several
432 NAND flashs at the same time. The GPMI may conflicts with other
433 block, such as SD card. So pay attention to it when you enable
436 config MTD_NAND_PLATFORM
437 tristate "Support for generic platform NAND driver"
440 This implements a generic NAND driver for on-SOC platform
441 devices. You will need to provide platform-specific functions
445 tristate "MTD driver for Olympus MAUSB-10 and Fujifilm DPC-R1"
448 These two (and possibly other) Alauda-based cardreaders for
449 SmartMedia and xD allow raw flash access.
451 config MTD_NAND_ORION
452 tristate "NAND Flash support for Marvell Orion SoC"
453 depends on PLAT_ORION
455 This enables the NAND flash controller on Orion machines.
457 No board specific support is done by this driver, each board
458 must advertise a platform_device for the driver to attach.
460 config MTD_NAND_FSL_ELBC
461 tristate "NAND support for Freescale eLBC controllers"
465 Various Freescale chips, including the 8313, include a NAND Flash
466 Controller Module with built-in hardware ECC capabilities.
467 Enabling this option will enable you to use this to control
468 external NAND devices.
470 config MTD_NAND_FSL_IFC
471 tristate "NAND support for Freescale IFC controller"
472 depends on MTD_NAND && FSL_SOC
475 Various Freescale chips e.g P1010, include a NAND Flash machine
476 with built-in hardware ECC capabilities.
477 Enabling this option will enable you to use this to control
478 external NAND devices.
480 config MTD_NAND_FSL_UPM
481 tristate "Support for NAND on Freescale UPM"
482 depends on PPC_83xx || PPC_85xx
485 Enables support for NAND Flash chips wired onto Freescale PowerPC
486 processor localbus with User-Programmable Machine support.
488 config MTD_NAND_MPC5121_NFC
489 tristate "MPC5121 built-in NAND Flash Controller support"
490 depends on PPC_MPC512x
492 This enables the driver for the NAND flash controller on the
496 tristate "MXC NAND support"
499 This enables the driver for the NAND flash controller on the
502 config MTD_NAND_NOMADIK
503 tristate "ST Nomadik 8815 NAND support"
504 depends on ARCH_NOMADIK
506 Driver for the NAND flash controller on the Nomadik, with ECC.
508 config MTD_NAND_SH_FLCTL
509 tristate "Support for NAND on Renesas SuperH FLCTL"
510 depends on SUPERH || ARCH_SHMOBILE
512 Several Renesas SuperH CPU has FLCTL. This option enables support
513 for NAND Flash using FLCTL.
515 config MTD_NAND_DAVINCI
516 tristate "Support NAND on DaVinci SoC"
517 depends on ARCH_DAVINCI
519 Enable the driver for NAND flash chips on Texas Instruments
522 config MTD_NAND_TXX9NDFMC
523 tristate "NAND Flash support for TXx9 SoC"
524 depends on SOC_TX4938 || SOC_TX4939
526 This enables the NAND flash controller on the TXx9 SoCs.
528 config MTD_NAND_SOCRATES
529 tristate "Support for NAND on Socrates board"
532 Enables support for NAND Flash chips wired onto Socrates board.
534 config MTD_NAND_NUC900
535 tristate "Support for NAND on Nuvoton NUC9xx/w90p910 evaluation boards."
536 depends on ARCH_W90X900
538 This enables the driver for the NAND Flash on evaluation board based
541 config MTD_NAND_JZ4740
542 tristate "Support for JZ4740 SoC NAND controller"
543 depends on MACH_JZ4740
545 Enables support for NAND Flash on JZ4740 SoC based boards.
548 tristate "Support for NAND on ST Micros FSMC"
549 depends on PLAT_SPEAR || PLAT_NOMADIK || MACH_U300
551 Enables support for NAND Flash chips on the ST Microelectronics
552 Flexible Static Memory Controller (FSMC)
555 tristate "Support for NAND on Lantiq XWAY SoC"
556 depends on LANTIQ && SOC_TYPE_XWAY
557 select MTD_NAND_PLATFORM
559 Enables support for NAND Flash chips on Lantiq XWAY SoCs. NAND is attached
560 to the External Bus Unit (EBU).