2 tristate "Include chip ids for known NAND devices."
5 Useful for NAND drivers that do not use the NAND subsystem but
6 still like to take advantage of the known chip information.
11 config MTD_NAND_ECC_SMC
12 bool "NAND ECC Smart Media byte order"
13 depends on MTD_NAND_ECC
16 Software ECC according to the Smart Media Specification.
17 The original Linux implementation had byte 0 and 1 swapped.
21 tristate "NAND Device Support"
26 This enables support for accessing all type of NAND flash
27 devices. For further information see
28 <http://www.linux-mtd.infradead.org/doc/nand.html>.
35 depends on MTD_NAND_ECC_BCH
38 config MTD_NAND_ECC_BCH
39 bool "Support software BCH ECC"
42 This enables support for software BCH error correction. Binary BCH
43 codes are more powerful and cpu intensive than traditional Hamming
44 ECC codes. They are used with NAND devices requiring more than 1 bit
51 config MTD_NAND_DENALI
52 tristate "Support Denali NAND controller"
54 Enable support for the Denali NAND controller. This should be
55 combined with either the PCI or platform drivers to provide device
58 config MTD_NAND_DENALI_PCI
59 tristate "Support Denali NAND controller on Intel Moorestown"
60 depends on PCI && MTD_NAND_DENALI
62 Enable the driver for NAND flash on Intel Moorestown, using the
63 Denali NAND controller core.
65 config MTD_NAND_DENALI_DT
66 tristate "Support Denali NAND controller as a DT device"
67 depends on HAVE_CLK && MTD_NAND_DENALI
69 Enable the driver for NAND flash on platforms using a Denali NAND
70 controller as a DT device.
72 config MTD_NAND_DENALI_SCRATCH_REG_ADDR
73 hex "Denali NAND size scratch register address"
75 depends on MTD_NAND_DENALI_PCI
77 Some platforms place the NAND chip size in a scratch register
78 because (some versions of) the driver aren't able to automatically
79 determine the size of certain chips. Set the address of the
80 scratch register here to enable this feature. On Intel Moorestown
81 boards, the scratch register is at 0xFF108018.
84 tristate "GPIO NAND Flash driver"
85 depends on GPIOLIB && ARM
87 This enables a GPIO based NAND flash driver.
89 config MTD_NAND_AMS_DELTA
90 tristate "NAND Flash device on Amstrad E3"
91 depends on MACH_AMS_DELTA
94 Support for NAND flash on Amstrad E3 (Delta).
97 tristate "NAND Flash device on OMAP2, OMAP3 and OMAP4"
98 depends on ARCH_OMAP2PLUS
100 Support for NAND flash on Texas Instruments OMAP2, OMAP3 and OMAP4
103 config MTD_NAND_OMAP_BCH
104 depends on MTD_NAND && MTD_NAND_OMAP2 && ARCH_OMAP3
105 tristate "Enable support for hardware BCH error correction"
108 select BCH_CONST_PARAMS
110 Support for hardware BCH error correction.
113 prompt "BCH error correction capability"
114 depends on MTD_NAND_OMAP_BCH
116 config MTD_NAND_OMAP_BCH8
117 bool "8 bits / 512 bytes (recommended)"
119 Support correcting up to 8 bitflips per 512-byte block.
120 This will use 13 bytes of spare area per 512 bytes of page data.
121 This is the recommended mode, as 4-bit mode does not work
122 on some OMAP3 revisions, due to a hardware bug.
124 config MTD_NAND_OMAP_BCH4
125 bool "4 bits / 512 bytes"
127 Support correcting up to 4 bitflips per 512-byte block.
128 This will use 7 bytes of spare area per 512 bytes of page data.
129 Note that this mode does not work on some OMAP3 revisions, due to a
130 hardware bug. Please check your OMAP datasheet before selecting this
139 default 4 if MTD_NAND_OMAP_BCH4
140 default 8 if MTD_NAND_OMAP_BCH8
143 config MTD_NAND_RICOH
144 tristate "Ricoh xD card reader"
149 Enable support for Ricoh R5C852 xD card reader
150 You also need to enable ether
151 NAND SSFDC (SmartMedia) read only translation layer' or new
152 expermental, readwrite
153 'SmartMedia/xD new translation layer'
155 config MTD_NAND_AU1550
156 tristate "Au1550/1200 NAND support"
157 depends on MIPS_ALCHEMY
159 This enables the driver for the NAND flash controller on the
160 AMD/Alchemy 1550 SOC.
162 config MTD_NAND_BF5XX
163 tristate "Blackfin on-chip NAND Flash Controller driver"
164 depends on BF54x || BF52x
166 This enables the Blackfin on-chip NAND flash controller
168 No board specific support is done by this driver, each board
169 must advertise a platform_device for the driver to attach.
171 This driver can also be built as a module. If so, the module
172 will be called bf5xx-nand.
174 config MTD_NAND_BF5XX_HWECC
175 bool "BF5XX NAND Hardware ECC"
177 depends on MTD_NAND_BF5XX
179 Enable the use of the BF5XX's internal ECC generator when
182 config MTD_NAND_BF5XX_BOOTROM_ECC
183 bool "Use Blackfin BootROM ECC Layout"
185 depends on MTD_NAND_BF5XX_HWECC
187 If you wish to modify NAND pages and allow the Blackfin on-chip
188 BootROM to boot from them, say Y here. This is only necessary
189 if you are booting U-Boot out of NAND and you wish to update
190 U-Boot from Linux' userspace. Otherwise, you should say N here.
194 config MTD_NAND_S3C2410
195 tristate "NAND Flash support for Samsung S3C SoCs"
196 depends on ARCH_S3C24XX || 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_DISKONCHIP
237 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation)"
240 select REED_SOLOMON_DEC16
242 This is a reimplementation of M-Systems DiskOnChip 2000,
243 Millennium and Millennium Plus as a standard NAND device driver,
244 as opposed to the earlier self-contained MTD device drivers.
245 This should enable, among other things, proper JFFS2 operation on
248 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
249 bool "Advanced detection options for DiskOnChip"
250 depends on MTD_NAND_DISKONCHIP
252 This option allows you to specify nonstandard address at which to
253 probe for a DiskOnChip, or to change the detection options. You
254 are unlikely to need any of this unless you are using LinuxBIOS.
257 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
258 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
259 depends on MTD_NAND_DISKONCHIP
262 By default, the probe for DiskOnChip devices will look for a
263 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
264 This option allows you to specify a single address at which to probe
265 for the device, which is useful if you have other devices in that
266 range which get upset when they are probed.
268 (Note that on PowerPC, the normal probe will only check at
271 Normally, you should leave this set to zero, to allow the probe at
272 the normal addresses.
274 config MTD_NAND_DISKONCHIP_PROBE_HIGH
275 bool "Probe high addresses"
276 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
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 changes to make it probe between 0xFFFC8000 and
281 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
282 useful to you. Say 'N'.
284 config MTD_NAND_DISKONCHIP_BBTWRITE
285 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
286 depends on MTD_NAND_DISKONCHIP
288 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
289 and 2000 TSOP/Alon), Linux reserves some space at the end of the
290 device for the Bad Block Table (BBT). If you have existing INFTL
291 data on your device (created by non-Linux tools such as M-Systems'
292 DOS drivers), your data might overlap the area Linux wants to use for
293 the BBT. If this is a concern for you, leave this option disabled and
294 Linux will not write BBT data into this area.
295 The downside of leaving this option disabled is that if bad blocks
296 are detected by Linux, they will not be recorded in the BBT, which
297 could cause future problems.
298 Once you enable this option, new filesystems (INFTL or others, created
299 in Linux or other operating systems) will not use the reserved area.
300 The only reason not to enable this option is to prevent damage to
301 preexisting filesystems.
302 Even if you leave this disabled, you can enable BBT writes at module
303 load time (assuming you build diskonchip as a module) with the module
304 parameter "inftl_bbt_write=1".
306 config MTD_NAND_DOCG4
307 tristate "Support for DiskOnChip G4"
312 Support for diskonchip G4 nand flash, found in various smartphones and
313 PDAs, among them the Palm Treo680, HTC Prophet and Wizard, Toshiba
314 Portege G900, Asus P526, and O2 XDA Zinc.
316 With this driver you will be able to use UBI and create a ubifs on the
317 device, so you may wish to consider enabling UBI and UBIFS as well.
319 These devices ship with the Mys/Sandisk SAFTL formatting, for which
320 there is currently no mtd parser, so you may want to use command line
321 partitioning to segregate write-protected blocks. On the Treo680, the
322 first five erase blocks (256KiB each) are write-protected, followed
323 by the block containing the saftl partition table. This is probably
326 config MTD_NAND_SHARPSL
327 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
331 tristate "NAND support for OLPC CAFÉ chip"
334 select REED_SOLOMON_DEC16
336 Use NAND flash attached to the CAFÉ chip designed for the OLPC
339 config MTD_NAND_CS553X
340 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
343 The CS553x companion chips for the AMD Geode processor
344 include NAND flash controllers with built-in hardware ECC
345 capabilities; enabling this option will allow you to use
346 these. The driver will check the MSRs to verify that the
347 controller is enabled for NAND, and currently requires that
348 the controller be in MMIO mode.
350 If you say "m", the module will be called cs553x_nand.
352 config MTD_NAND_ATMEL
353 tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
354 depends on ARCH_AT91 || AVR32
356 Enables support for NAND Flash / Smart Media Card interface
357 on Atmel AT91 and AVR32 processors.
359 config MTD_NAND_PXA3xx
360 tristate "Support for NAND flash devices on PXA3xx"
361 depends on PXA3xx || ARCH_MMP
363 This enables the driver for the NAND flash device found on
366 config MTD_NAND_SLC_LPC32XX
367 tristate "NXP LPC32xx SLC Controller"
368 depends on ARCH_LPC32XX
370 Enables support for NXP's LPC32XX SLC (i.e. for Single Level Cell
371 chips) NAND controller. This is the default for the PHYTEC 3250
372 reference board which contains a NAND256R3A2CZA6 chip.
374 Please check the actual NAND chip connected and its support
375 by the SLC NAND controller.
377 config MTD_NAND_MLC_LPC32XX
378 tristate "NXP LPC32xx MLC Controller"
379 depends on ARCH_LPC32XX
381 Uses the LPC32XX MLC (i.e. for Multi Level Cell chips) NAND
382 controller. This is the default for the WORK92105 controller
385 Please check the actual NAND chip connected and its support
386 by the MLC NAND controller.
388 config MTD_NAND_CM_X270
389 tristate "Support for NAND Flash on CM-X270 modules"
390 depends on MACH_ARMCORE
392 config MTD_NAND_PASEMI
393 tristate "NAND support for PA Semi PWRficient"
394 depends on PPC_PASEMI
396 Enables support for NAND Flash interface on PA Semi PWRficient
400 tristate "NAND Flash device on Toshiba Mobile IO Controller"
403 Support for NAND flash connected to a Toshiba Mobile IO
404 Controller in some PDAs, including the Sharp SL6000x.
406 config MTD_NAND_NANDSIM
407 tristate "Support for NAND Flash Simulator"
409 The simulator may simulate various NAND flash chips for the
412 config MTD_NAND_GPMI_NAND
413 tristate "GPMI NAND Flash Controller driver"
414 depends on MTD_NAND && MXS_DMA
416 Enables NAND Flash support for IMX23, IMX28 or IMX6.
417 The GPMI controller is very powerful, with the help of BCH
418 module, it can do the hardware ECC. The GPMI supports several
419 NAND flashs at the same time. The GPMI may conflicts with other
420 block, such as SD card. So pay attention to it when you enable
423 config MTD_NAND_BCM47XXNFLASH
424 tristate "Support for NAND flash on BCM4706 BCMA bus"
425 depends on BCMA_NFLASH
427 BCMA bus can have various flash memories attached, they are
428 registered by bcma as platform devices. This enables driver for
429 NAND flash memories. For now only BCM4706 is supported.
431 config MTD_NAND_PLATFORM
432 tristate "Support for generic platform NAND driver"
435 This implements a generic NAND driver for on-SOC platform
436 devices. You will need to provide platform-specific functions
440 tristate "MTD driver for Olympus MAUSB-10 and Fujifilm DPC-R1"
443 These two (and possibly other) Alauda-based cardreaders for
444 SmartMedia and xD allow raw flash access.
446 config MTD_NAND_ORION
447 tristate "NAND Flash support for Marvell Orion SoC"
448 depends on PLAT_ORION
450 This enables the NAND flash controller on Orion machines.
452 No board specific support is done by this driver, each board
453 must advertise a platform_device for the driver to attach.
455 config MTD_NAND_FSL_ELBC
456 tristate "NAND support for Freescale eLBC controllers"
460 Various Freescale chips, including the 8313, include a NAND Flash
461 Controller Module with built-in hardware ECC capabilities.
462 Enabling this option will enable you to use this to control
463 external NAND devices.
465 config MTD_NAND_FSL_IFC
466 tristate "NAND support for Freescale IFC controller"
467 depends on MTD_NAND && FSL_SOC
470 Various Freescale chips e.g P1010, include a NAND Flash machine
471 with built-in hardware ECC capabilities.
472 Enabling this option will enable you to use this to control
473 external NAND devices.
475 config MTD_NAND_FSL_UPM
476 tristate "Support for NAND on Freescale UPM"
477 depends on PPC_83xx || PPC_85xx
480 Enables support for NAND Flash chips wired onto Freescale PowerPC
481 processor localbus with User-Programmable Machine support.
483 config MTD_NAND_MPC5121_NFC
484 tristate "MPC5121 built-in NAND Flash Controller support"
485 depends on PPC_MPC512x
487 This enables the driver for the NAND flash controller on the
491 tristate "MXC NAND support"
494 This enables the driver for the NAND flash controller on the
497 config MTD_NAND_SH_FLCTL
498 tristate "Support for NAND on Renesas SuperH FLCTL"
499 depends on SUPERH || ARCH_SHMOBILE
501 Several Renesas SuperH CPU has FLCTL. This option enables support
502 for NAND Flash using FLCTL.
504 config MTD_NAND_DAVINCI
505 tristate "Support NAND on DaVinci SoC"
506 depends on ARCH_DAVINCI
508 Enable the driver for NAND flash chips on Texas Instruments
511 config MTD_NAND_TXX9NDFMC
512 tristate "NAND Flash support for TXx9 SoC"
513 depends on SOC_TX4938 || SOC_TX4939
515 This enables the NAND flash controller on the TXx9 SoCs.
517 config MTD_NAND_SOCRATES
518 tristate "Support for NAND on Socrates board"
521 Enables support for NAND Flash chips wired onto Socrates board.
523 config MTD_NAND_NUC900
524 tristate "Support for NAND on Nuvoton NUC9xx/w90p910 evaluation boards."
525 depends on ARCH_W90X900
527 This enables the driver for the NAND Flash on evaluation board based
530 config MTD_NAND_JZ4740
531 tristate "Support for JZ4740 SoC NAND controller"
532 depends on MACH_JZ4740
534 Enables support for NAND Flash on JZ4740 SoC based boards.
537 tristate "Support for NAND on ST Micros FSMC"
538 depends on PLAT_SPEAR || ARCH_NOMADIK || ARCH_U8500 || MACH_U300
540 Enables support for NAND Flash chips on the ST Microelectronics
541 Flexible Static Memory Controller (FSMC)
544 tristate "Support for NAND on Lantiq XWAY SoC"
545 depends on LANTIQ && SOC_TYPE_XWAY
546 select MTD_NAND_PLATFORM
548 Enables support for NAND Flash chips on Lantiq XWAY SoCs. NAND is attached
549 to the External Bus Unit (EBU).
551 config MTD_NAND_SC8810
552 tristate "NAND Flash support for SpreadTrum SC8810 phone board"
553 depends on ARCH_SC8810
555 This enables the NAND flash controller with hardware ecc on the SC8810 phone board
557 config MTD_NAND_SC8825
558 tristate "NAND Flash support for SpreadTrum SC8825 phone board"
559 depends on ARCH_SC8825
561 This enables the NAND flash controller with hardware ecc on the SC8825 phone board
563 config MTD_NAND_DOLPHIN
564 tristate "NAND Flash support for SpreadTrum DOLPHIN phone board"
565 depends on ARCH_SCX15
567 This enables the NAND flash controller with hardware ecc on the DOLPHIN phone board
568 config MTD_NAND_SC8830
569 tristate "NAND Flash support for SpreadTrum SC8830 phone board"
570 depends on ARCH_SCX35
572 This enables the NAND flash controller with hardware ecc on the SC8830 phone board