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_DENALI
45 tristate "Support Denali NAND controller"
47 Enable support for the Denali NAND controller. This should be
48 combined with either the PCI or platform drivers to provide device
51 config MTD_NAND_DENALI_PCI
52 tristate "Support Denali NAND controller on Intel Moorestown"
53 depends on PCI && MTD_NAND_DENALI
55 Enable the driver for NAND flash on Intel Moorestown, using the
56 Denali NAND controller core.
58 config MTD_NAND_DENALI_DT
59 tristate "Support Denali NAND controller as a DT device"
60 depends on HAVE_CLK && MTD_NAND_DENALI
62 Enable the driver for NAND flash on platforms using a Denali NAND
63 controller as a DT device.
65 config MTD_NAND_DENALI_SCRATCH_REG_ADDR
66 hex "Denali NAND size scratch register address"
68 depends on MTD_NAND_DENALI_PCI
70 Some platforms place the NAND chip size in a scratch register
71 because (some versions of) the driver aren't able to automatically
72 determine the size of certain chips. Set the address of the
73 scratch register here to enable this feature. On Intel Moorestown
74 boards, the scratch register is at 0xFF108018.
77 tristate "iPAQ H1900 flash"
78 depends on ARCH_PXA && BROKEN
80 This enables the driver for the iPAQ h1900 flash.
83 tristate "GPIO NAND Flash driver"
84 depends on GENERIC_GPIO && ARM
86 This enables a GPIO based NAND flash driver.
88 config MTD_NAND_AMS_DELTA
89 tristate "NAND Flash device on Amstrad E3"
90 depends on MACH_AMS_DELTA
93 Support for NAND flash on Amstrad E3 (Delta).
96 tristate "NAND Flash device on OMAP2, OMAP3 and OMAP4"
97 depends on ARCH_OMAP2PLUS
99 Support for NAND flash on Texas Instruments OMAP2, OMAP3 and OMAP4
102 config MTD_NAND_OMAP_BCH
103 depends on MTD_NAND && MTD_NAND_OMAP2 && ARCH_OMAP3
104 bool "Enable support for hardware BCH error correction"
107 select BCH_CONST_PARAMS
109 Support for hardware BCH error correction.
112 prompt "BCH error correction capability"
113 depends on MTD_NAND_OMAP_BCH
115 config MTD_NAND_OMAP_BCH8
116 bool "8 bits / 512 bytes (recommended)"
118 Support correcting up to 8 bitflips per 512-byte block.
119 This will use 13 bytes of spare area per 512 bytes of page data.
120 This is the recommended mode, as 4-bit mode does not work
121 on some OMAP3 revisions, due to a hardware bug.
123 config MTD_NAND_OMAP_BCH4
124 bool "4 bits / 512 bytes"
126 Support correcting up to 4 bitflips per 512-byte block.
127 This will use 7 bytes of spare area per 512 bytes of page data.
128 Note that this mode does not work on some OMAP3 revisions, due to a
129 hardware bug. Please check your OMAP datasheet before selecting this
138 default 4 if MTD_NAND_OMAP_BCH4
139 default 8 if MTD_NAND_OMAP_BCH8
145 config MTD_NAND_RICOH
146 tristate "Ricoh xD card reader"
151 Enable support for Ricoh R5C852 xD card reader
152 You also need to enable ether
153 NAND SSFDC (SmartMedia) read only translation layer' or new
154 expermental, readwrite
155 'SmartMedia/xD new translation layer'
157 config MTD_NAND_AU1550
158 tristate "Au1550/1200 NAND support"
159 depends on MIPS_ALCHEMY
161 This enables the driver for the NAND flash controller on the
162 AMD/Alchemy 1550 SOC.
164 config MTD_NAND_BF5XX
165 tristate "Blackfin on-chip NAND Flash Controller driver"
166 depends on BF54x || BF52x
168 This enables the Blackfin on-chip NAND flash controller
170 No board specific support is done by this driver, each board
171 must advertise a platform_device for the driver to attach.
173 This driver can also be built as a module. If so, the module
174 will be called bf5xx-nand.
176 config MTD_NAND_BF5XX_HWECC
177 bool "BF5XX NAND Hardware ECC"
179 depends on MTD_NAND_BF5XX
181 Enable the use of the BF5XX's internal ECC generator when
184 config MTD_NAND_BF5XX_BOOTROM_ECC
185 bool "Use Blackfin BootROM ECC Layout"
187 depends on MTD_NAND_BF5XX_HWECC
189 If you wish to modify NAND pages and allow the Blackfin on-chip
190 BootROM to boot from them, say Y here. This is only necessary
191 if you are booting U-Boot out of NAND and you wish to update
192 U-Boot from Linux' userspace. Otherwise, you should say N here.
196 config MTD_NAND_S3C2410
197 tristate "NAND Flash support for Samsung S3C SoCs"
198 depends on ARCH_S3C24XX || ARCH_S3C64XX
200 This enables the NAND flash controller on the S3C24xx and S3C64xx
203 No board specific support is done by this driver, each board
204 must advertise a platform_device for the driver to attach.
206 config MTD_NAND_S3C2410_DEBUG
207 bool "Samsung S3C NAND driver debug"
208 depends on MTD_NAND_S3C2410
210 Enable debugging of the S3C NAND driver
212 config MTD_NAND_S3C2410_HWECC
213 bool "Samsung S3C NAND Hardware ECC"
214 depends on MTD_NAND_S3C2410
216 Enable the use of the controller's internal ECC generator when
217 using NAND. Early versions of the chips have had problems with
218 incorrect ECC generation, and if using these, the default of
219 software ECC is preferable.
222 tristate "NDFC NanD Flash Controller"
224 select MTD_NAND_ECC_SMC
226 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
228 config MTD_NAND_S3C2410_CLKSTOP
229 bool "Samsung S3C NAND IDLE clock stop"
230 depends on MTD_NAND_S3C2410
233 Stop the clock to the NAND controller when there is no chip
234 selected to save power. This will mean there is a small delay
235 when the is NAND chip selected or released, but will save
236 approximately 5mA of power when there is nothing happening.
238 config MTD_NAND_DISKONCHIP
239 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation)"
242 select REED_SOLOMON_DEC16
244 This is a reimplementation of M-Systems DiskOnChip 2000,
245 Millennium and Millennium Plus as a standard NAND device driver,
246 as opposed to the earlier self-contained MTD device drivers.
247 This should enable, among other things, proper JFFS2 operation on
250 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
251 bool "Advanced detection options for DiskOnChip"
252 depends on MTD_NAND_DISKONCHIP
254 This option allows you to specify nonstandard address at which to
255 probe for a DiskOnChip, or to change the detection options. You
256 are unlikely to need any of this unless you are using LinuxBIOS.
259 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
260 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
261 depends on MTD_NAND_DISKONCHIP
264 By default, the probe for DiskOnChip devices will look for a
265 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
266 This option allows you to specify a single address at which to probe
267 for the device, which is useful if you have other devices in that
268 range which get upset when they are probed.
270 (Note that on PowerPC, the normal probe will only check at
273 Normally, you should leave this set to zero, to allow the probe at
274 the normal addresses.
276 config MTD_NAND_DISKONCHIP_PROBE_HIGH
277 bool "Probe high addresses"
278 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
280 By default, the probe for DiskOnChip devices will look for a
281 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
282 This option changes to make it probe between 0xFFFC8000 and
283 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
284 useful to you. Say 'N'.
286 config MTD_NAND_DISKONCHIP_BBTWRITE
287 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
288 depends on MTD_NAND_DISKONCHIP
290 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
291 and 2000 TSOP/Alon), Linux reserves some space at the end of the
292 device for the Bad Block Table (BBT). If you have existing INFTL
293 data on your device (created by non-Linux tools such as M-Systems'
294 DOS drivers), your data might overlap the area Linux wants to use for
295 the BBT. If this is a concern for you, leave this option disabled and
296 Linux will not write BBT data into this area.
297 The downside of leaving this option disabled is that if bad blocks
298 are detected by Linux, they will not be recorded in the BBT, which
299 could cause future problems.
300 Once you enable this option, new filesystems (INFTL or others, created
301 in Linux or other operating systems) will not use the reserved area.
302 The only reason not to enable this option is to prevent damage to
303 preexisting filesystems.
304 Even if you leave this disabled, you can enable BBT writes at module
305 load time (assuming you build diskonchip as a module) with the module
306 parameter "inftl_bbt_write=1".
308 config MTD_NAND_DOCG4
309 tristate "Support for DiskOnChip G4"
314 Support for diskonchip G4 nand flash, found in various smartphones and
315 PDAs, among them the Palm Treo680, HTC Prophet and Wizard, Toshiba
316 Portege G900, Asus P526, and O2 XDA Zinc.
318 With this driver you will be able to use UBI and create a ubifs on the
319 device, so you may wish to consider enabling UBI and UBIFS as well.
321 These devices ship with the Mys/Sandisk SAFTL formatting, for which
322 there is currently no mtd parser, so you may want to use command line
323 partitioning to segregate write-protected blocks. On the Treo680, the
324 first five erase blocks (256KiB each) are write-protected, followed
325 by the block containing the saftl partition table. This is probably
328 config MTD_NAND_SHARPSL
329 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
333 tristate "NAND support for OLPC CAFÉ chip"
336 select REED_SOLOMON_DEC16
338 Use NAND flash attached to the CAFÉ chip designed for the OLPC
341 config MTD_NAND_CS553X
342 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
345 The CS553x companion chips for the AMD Geode processor
346 include NAND flash controllers with built-in hardware ECC
347 capabilities; enabling this option will allow you to use
348 these. The driver will check the MSRs to verify that the
349 controller is enabled for NAND, and currently requires that
350 the controller be in MMIO mode.
352 If you say "m", the module will be called cs553x_nand.
354 config MTD_NAND_ATMEL
355 tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
356 depends on ARCH_AT91 || AVR32
358 Enables support for NAND Flash / Smart Media Card interface
359 on Atmel AT91 and AVR32 processors.
361 config MTD_NAND_PXA3xx
362 tristate "Support for NAND flash devices on PXA3xx"
363 depends on PXA3xx || ARCH_MMP
365 This enables the driver for the NAND flash device found on
368 config MTD_NAND_SLC_LPC32XX
369 tristate "NXP LPC32xx SLC Controller"
370 depends on ARCH_LPC32XX
372 Enables support for NXP's LPC32XX SLC (i.e. for Single Level Cell
373 chips) NAND controller. This is the default for the PHYTEC 3250
374 reference board which contains a NAND256R3A2CZA6 chip.
376 Please check the actual NAND chip connected and its support
377 by the SLC NAND controller.
379 config MTD_NAND_MLC_LPC32XX
380 tristate "NXP LPC32xx MLC Controller"
381 depends on ARCH_LPC32XX
383 Uses the LPC32XX MLC (i.e. for Multi Level Cell chips) NAND
384 controller. This is the default for the WORK92105 controller
387 Please check the actual NAND chip connected and its support
388 by the MLC NAND controller.
390 config MTD_NAND_CM_X270
391 tristate "Support for NAND Flash on CM-X270 modules"
392 depends on MACH_ARMCORE
394 config MTD_NAND_PASEMI
395 tristate "NAND support for PA Semi PWRficient"
396 depends on PPC_PASEMI
398 Enables support for NAND Flash interface on PA Semi PWRficient
402 tristate "NAND Flash device on Toshiba Mobile IO Controller"
405 Support for NAND flash connected to a Toshiba Mobile IO
406 Controller in some PDAs, including the Sharp SL6000x.
408 config MTD_NAND_NANDSIM
409 tristate "Support for NAND Flash Simulator"
411 The simulator may simulate various NAND flash chips for the
414 config MTD_NAND_GPMI_NAND
415 tristate "GPMI NAND Flash Controller driver"
416 depends on MTD_NAND && MXS_DMA
418 Enables NAND Flash support for IMX23, IMX28 or IMX6.
419 The GPMI controller is very powerful, with the help of BCH
420 module, it can do the hardware ECC. The GPMI supports several
421 NAND flashs at the same time. The GPMI may conflicts with other
422 block, such as SD card. So pay attention to it when you enable
425 config MTD_NAND_BCM47XXNFLASH
426 tristate "Support for NAND flash on BCM4706 BCMA bus"
427 depends on BCMA_NFLASH
429 BCMA bus can have various flash memories attached, they are
430 registered by bcma as platform devices. This enables driver for
431 NAND flash memories. For now only BCM4706 is supported.
433 config MTD_NAND_PLATFORM
434 tristate "Support for generic platform NAND driver"
437 This implements a generic NAND driver for on-SOC platform
438 devices. You will need to provide platform-specific functions
442 tristate "MTD driver for Olympus MAUSB-10 and Fujifilm DPC-R1"
445 These two (and possibly other) Alauda-based cardreaders for
446 SmartMedia and xD allow raw flash access.
448 config MTD_NAND_ORION
449 tristate "NAND Flash support for Marvell Orion SoC"
450 depends on PLAT_ORION
452 This enables the NAND flash controller on Orion machines.
454 No board specific support is done by this driver, each board
455 must advertise a platform_device for the driver to attach.
457 config MTD_NAND_FSL_ELBC
458 tristate "NAND support for Freescale eLBC controllers"
462 Various Freescale chips, including the 8313, include a NAND Flash
463 Controller Module with built-in hardware ECC capabilities.
464 Enabling this option will enable you to use this to control
465 external NAND devices.
467 config MTD_NAND_FSL_IFC
468 tristate "NAND support for Freescale IFC controller"
469 depends on MTD_NAND && FSL_SOC
472 Various Freescale chips e.g P1010, include a NAND Flash machine
473 with built-in hardware ECC capabilities.
474 Enabling this option will enable you to use this to control
475 external NAND devices.
477 config MTD_NAND_FSL_UPM
478 tristate "Support for NAND on Freescale UPM"
479 depends on PPC_83xx || PPC_85xx
482 Enables support for NAND Flash chips wired onto Freescale PowerPC
483 processor localbus with User-Programmable Machine support.
485 config MTD_NAND_MPC5121_NFC
486 tristate "MPC5121 built-in NAND Flash Controller support"
487 depends on PPC_MPC512x
489 This enables the driver for the NAND flash controller on the
493 tristate "MXC NAND support"
496 This enables the driver for the NAND flash controller on the
499 config MTD_NAND_SH_FLCTL
500 tristate "Support for NAND on Renesas SuperH FLCTL"
501 depends on SUPERH || ARCH_SHMOBILE
503 Several Renesas SuperH CPU has FLCTL. This option enables support
504 for NAND Flash using FLCTL.
506 config MTD_NAND_DAVINCI
507 tristate "Support NAND on DaVinci SoC"
508 depends on ARCH_DAVINCI
510 Enable the driver for NAND flash chips on Texas Instruments
513 config MTD_NAND_TXX9NDFMC
514 tristate "NAND Flash support for TXx9 SoC"
515 depends on SOC_TX4938 || SOC_TX4939
517 This enables the NAND flash controller on the TXx9 SoCs.
519 config MTD_NAND_SOCRATES
520 tristate "Support for NAND on Socrates board"
523 Enables support for NAND Flash chips wired onto Socrates board.
525 config MTD_NAND_NUC900
526 tristate "Support for NAND on Nuvoton NUC9xx/w90p910 evaluation boards."
527 depends on ARCH_W90X900
529 This enables the driver for the NAND Flash on evaluation board based
532 config MTD_NAND_JZ4740
533 tristate "Support for JZ4740 SoC NAND controller"
534 depends on MACH_JZ4740
536 Enables support for NAND Flash on JZ4740 SoC based boards.
539 tristate "Support for NAND on ST Micros FSMC"
540 depends on PLAT_SPEAR || ARCH_NOMADIK || ARCH_U8500 || MACH_U300
542 Enables support for NAND Flash chips on the ST Microelectronics
543 Flexible Static Memory Controller (FSMC)
546 tristate "Support for NAND on Lantiq XWAY SoC"
547 depends on LANTIQ && SOC_TYPE_XWAY
548 select MTD_NAND_PLATFORM
550 Enables support for NAND Flash chips on Lantiq XWAY SoCs. NAND is attached
551 to the External Bus Unit (EBU).