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_AUTCPU12
53 tristate "SmartMediaCard on autronix autcpu12 board"
54 depends on ARCH_AUTCPU12
56 This enables the driver for the autronix autcpu12 board to
57 access the SmartMediaCard.
59 config MTD_NAND_DENALI
60 tristate "Support Denali NAND controller"
62 Enable support for the Denali NAND controller. This should be
63 combined with either the PCI or platform drivers to provide device
66 config MTD_NAND_DENALI_PCI
67 tristate "Support Denali NAND controller on Intel Moorestown"
68 depends on PCI && MTD_NAND_DENALI
70 Enable the driver for NAND flash on Intel Moorestown, using the
71 Denali NAND controller core.
73 config MTD_NAND_DENALI_DT
74 tristate "Support Denali NAND controller as a DT device"
75 depends on HAVE_CLK && MTD_NAND_DENALI
77 Enable the driver for NAND flash on platforms using a Denali NAND
78 controller as a DT device.
80 config MTD_NAND_DENALI_SCRATCH_REG_ADDR
81 hex "Denali NAND size scratch register address"
83 depends on MTD_NAND_DENALI_PCI
85 Some platforms place the NAND chip size in a scratch register
86 because (some versions of) the driver aren't able to automatically
87 determine the size of certain chips. Set the address of the
88 scratch register here to enable this feature. On Intel Moorestown
89 boards, the scratch register is at 0xFF108018.
92 tristate "iPAQ H1900 flash"
93 depends on ARCH_PXA && BROKEN
95 This enables the driver for the iPAQ h1900 flash.
98 tristate "GPIO NAND Flash driver"
99 depends on GENERIC_GPIO && ARM
101 This enables a GPIO based NAND flash driver.
104 tristate "NAND Flash device on SPIA board"
105 depends on ARCH_P720T
107 If you had to ask, you don't have one. Say 'N'.
109 config MTD_NAND_AMS_DELTA
110 tristate "NAND Flash device on Amstrad E3"
111 depends on MACH_AMS_DELTA
114 Support for NAND flash on Amstrad E3 (Delta).
116 config MTD_NAND_OMAP2
117 tristate "NAND Flash device on OMAP2, OMAP3 and OMAP4"
118 depends on ARCH_OMAP2PLUS
120 Support for NAND flash on Texas Instruments OMAP2, OMAP3 and OMAP4
123 config MTD_NAND_OMAP_BCH
124 depends on MTD_NAND && MTD_NAND_OMAP2 && ARCH_OMAP3
125 bool "Enable support for hardware BCH error correction"
128 select BCH_CONST_PARAMS
130 Support for hardware BCH error correction.
133 prompt "BCH error correction capability"
134 depends on MTD_NAND_OMAP_BCH
136 config MTD_NAND_OMAP_BCH8
137 bool "8 bits / 512 bytes (recommended)"
139 Support correcting up to 8 bitflips per 512-byte block.
140 This will use 13 bytes of spare area per 512 bytes of page data.
141 This is the recommended mode, as 4-bit mode does not work
142 on some OMAP3 revisions, due to a hardware bug.
144 config MTD_NAND_OMAP_BCH4
145 bool "4 bits / 512 bytes"
147 Support correcting up to 4 bitflips per 512-byte block.
148 This will use 7 bytes of spare area per 512 bytes of page data.
149 Note that this mode does not work on some OMAP3 revisions, due to a
150 hardware bug. Please check your OMAP datasheet before selecting this
159 default 4 if MTD_NAND_OMAP_BCH4
160 default 8 if MTD_NAND_OMAP_BCH8
166 config MTD_NAND_RICOH
167 tristate "Ricoh xD card reader"
172 Enable support for Ricoh R5C852 xD card reader
173 You also need to enable ether
174 NAND SSFDC (SmartMedia) read only translation layer' or new
175 expermental, readwrite
176 'SmartMedia/xD new translation layer'
178 config MTD_NAND_AU1550
179 tristate "Au1550/1200 NAND support"
180 depends on MIPS_ALCHEMY
182 This enables the driver for the NAND flash controller on the
183 AMD/Alchemy 1550 SOC.
185 config MTD_NAND_BF5XX
186 tristate "Blackfin on-chip NAND Flash Controller driver"
187 depends on BF54x || BF52x
189 This enables the Blackfin on-chip NAND flash controller
191 No board specific support is done by this driver, each board
192 must advertise a platform_device for the driver to attach.
194 This driver can also be built as a module. If so, the module
195 will be called bf5xx-nand.
197 config MTD_NAND_BF5XX_HWECC
198 bool "BF5XX NAND Hardware ECC"
200 depends on MTD_NAND_BF5XX
202 Enable the use of the BF5XX's internal ECC generator when
205 config MTD_NAND_BF5XX_BOOTROM_ECC
206 bool "Use Blackfin BootROM ECC Layout"
208 depends on MTD_NAND_BF5XX_HWECC
210 If you wish to modify NAND pages and allow the Blackfin on-chip
211 BootROM to boot from them, say Y here. This is only necessary
212 if you are booting U-Boot out of NAND and you wish to update
213 U-Boot from Linux' userspace. Otherwise, you should say N here.
217 config MTD_NAND_RTC_FROM4
218 tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
219 depends on SH_SOLUTION_ENGINE
221 select REED_SOLOMON_DEC8
224 This enables the driver for the Renesas Technology AG-AND
225 flash interface board (FROM_BOARD4)
227 config MTD_NAND_PPCHAMELEONEVB
228 tristate "NAND Flash device on PPChameleonEVB board"
229 depends on PPCHAMELEONEVB && BROKEN
231 This enables the NAND flash driver on the PPChameleon EVB Board.
233 config MTD_NAND_S3C2410
234 tristate "NAND Flash support for Samsung S3C SoCs"
235 depends on ARCH_S3C24XX || ARCH_S3C64XX
237 This enables the NAND flash controller on the S3C24xx and S3C64xx
240 No board specific support is done by this driver, each board
241 must advertise a platform_device for the driver to attach.
243 config MTD_NAND_S3C2410_DEBUG
244 bool "Samsung S3C NAND driver debug"
245 depends on MTD_NAND_S3C2410
247 Enable debugging of the S3C NAND driver
249 config MTD_NAND_S3C2410_HWECC
250 bool "Samsung S3C NAND Hardware ECC"
251 depends on MTD_NAND_S3C2410
253 Enable the use of the controller's internal ECC generator when
254 using NAND. Early versions of the chips have had problems with
255 incorrect ECC generation, and if using these, the default of
256 software ECC is preferable.
259 tristate "NDFC NanD Flash Controller"
261 select MTD_NAND_ECC_SMC
263 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
265 config MTD_NAND_S3C2410_CLKSTOP
266 bool "Samsung S3C NAND IDLE clock stop"
267 depends on MTD_NAND_S3C2410
270 Stop the clock to the NAND controller when there is no chip
271 selected to save power. This will mean there is a small delay
272 when the is NAND chip selected or released, but will save
273 approximately 5mA of power when there is nothing happening.
275 config MTD_NAND_DISKONCHIP
276 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
277 depends on EXPERIMENTAL
280 select REED_SOLOMON_DEC16
282 This is a reimplementation of M-Systems DiskOnChip 2000,
283 Millennium and Millennium Plus as a standard NAND device driver,
284 as opposed to the earlier self-contained MTD device drivers.
285 This should enable, among other things, proper JFFS2 operation on
288 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
289 bool "Advanced detection options for DiskOnChip"
290 depends on MTD_NAND_DISKONCHIP
292 This option allows you to specify nonstandard address at which to
293 probe for a DiskOnChip, or to change the detection options. You
294 are unlikely to need any of this unless you are using LinuxBIOS.
297 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
298 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
299 depends on MTD_NAND_DISKONCHIP
302 By default, the probe for DiskOnChip devices will look for a
303 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
304 This option allows you to specify a single address at which to probe
305 for the device, which is useful if you have other devices in that
306 range which get upset when they are probed.
308 (Note that on PowerPC, the normal probe will only check at
311 Normally, you should leave this set to zero, to allow the probe at
312 the normal addresses.
314 config MTD_NAND_DISKONCHIP_PROBE_HIGH
315 bool "Probe high addresses"
316 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
318 By default, the probe for DiskOnChip devices will look for a
319 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
320 This option changes to make it probe between 0xFFFC8000 and
321 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
322 useful to you. Say 'N'.
324 config MTD_NAND_DISKONCHIP_BBTWRITE
325 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
326 depends on MTD_NAND_DISKONCHIP
328 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
329 and 2000 TSOP/Alon), Linux reserves some space at the end of the
330 device for the Bad Block Table (BBT). If you have existing INFTL
331 data on your device (created by non-Linux tools such as M-Systems'
332 DOS drivers), your data might overlap the area Linux wants to use for
333 the BBT. If this is a concern for you, leave this option disabled and
334 Linux will not write BBT data into this area.
335 The downside of leaving this option disabled is that if bad blocks
336 are detected by Linux, they will not be recorded in the BBT, which
337 could cause future problems.
338 Once you enable this option, new filesystems (INFTL or others, created
339 in Linux or other operating systems) will not use the reserved area.
340 The only reason not to enable this option is to prevent damage to
341 preexisting filesystems.
342 Even if you leave this disabled, you can enable BBT writes at module
343 load time (assuming you build diskonchip as a module) with the module
344 parameter "inftl_bbt_write=1".
346 config MTD_NAND_DOCG4
347 tristate "Support for DiskOnChip G4 (EXPERIMENTAL)"
348 depends on EXPERIMENTAL && HAS_IOMEM
352 Support for diskonchip G4 nand flash, found in various smartphones and
353 PDAs, among them the Palm Treo680, HTC Prophet and Wizard, Toshiba
354 Portege G900, Asus P526, and O2 XDA Zinc.
356 With this driver you will be able to use UBI and create a ubifs on the
357 device, so you may wish to consider enabling UBI and UBIFS as well.
359 These devices ship with the Mys/Sandisk SAFTL formatting, for which
360 there is currently no mtd parser, so you may want to use command line
361 partitioning to segregate write-protected blocks. On the Treo680, the
362 first five erase blocks (256KiB each) are write-protected, followed
363 by the block containing the saftl partition table. This is probably
366 config MTD_NAND_SHARPSL
367 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
371 tristate "NAND support for OLPC CAFÉ chip"
374 select REED_SOLOMON_DEC16
376 Use NAND flash attached to the CAFÉ chip designed for the OLPC
379 config MTD_NAND_CS553X
380 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
383 The CS553x companion chips for the AMD Geode processor
384 include NAND flash controllers with built-in hardware ECC
385 capabilities; enabling this option will allow you to use
386 these. The driver will check the MSRs to verify that the
387 controller is enabled for NAND, and currently requires that
388 the controller be in MMIO mode.
390 If you say "m", the module will be called cs553x_nand.
392 config MTD_NAND_ATMEL
393 tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
394 depends on ARCH_AT91 || AVR32
396 Enables support for NAND Flash / Smart Media Card interface
397 on Atmel AT91 and AVR32 processors.
399 config MTD_NAND_PXA3xx
400 tristate "Support for NAND flash devices on PXA3xx"
401 depends on PXA3xx || ARCH_MMP
403 This enables the driver for the NAND flash device found on
406 config MTD_NAND_SLC_LPC32XX
407 tristate "NXP LPC32xx SLC Controller"
408 depends on ARCH_LPC32XX
410 Enables support for NXP's LPC32XX SLC (i.e. for Single Level Cell
411 chips) NAND controller. This is the default for the PHYTEC 3250
412 reference board which contains a NAND256R3A2CZA6 chip.
414 Please check the actual NAND chip connected and its support
415 by the SLC NAND controller.
417 config MTD_NAND_MLC_LPC32XX
418 tristate "NXP LPC32xx MLC Controller"
419 depends on ARCH_LPC32XX
421 Uses the LPC32XX MLC (i.e. for Multi Level Cell chips) NAND
422 controller. This is the default for the WORK92105 controller
425 Please check the actual NAND chip connected and its support
426 by the MLC NAND controller.
428 config MTD_NAND_CM_X270
429 tristate "Support for NAND Flash on CM-X270 modules"
430 depends on MACH_ARMCORE
432 config MTD_NAND_PASEMI
433 tristate "NAND support for PA Semi PWRficient"
434 depends on PPC_PASEMI
436 Enables support for NAND Flash interface on PA Semi PWRficient
440 tristate "NAND Flash device on Toshiba Mobile IO Controller"
443 Support for NAND flash connected to a Toshiba Mobile IO
444 Controller in some PDAs, including the Sharp SL6000x.
446 config MTD_NAND_NANDSIM
447 tristate "Support for NAND Flash Simulator"
449 The simulator may simulate various NAND flash chips for the
452 config MTD_NAND_GPMI_NAND
453 tristate "GPMI NAND Flash Controller driver"
454 depends on MTD_NAND && MXS_DMA
456 Enables NAND Flash support for IMX23, IMX28 or IMX6.
457 The GPMI controller is very powerful, with the help of BCH
458 module, it can do the hardware ECC. The GPMI supports several
459 NAND flashs at the same time. The GPMI may conflicts with other
460 block, such as SD card. So pay attention to it when you enable
463 config MTD_NAND_BCM47XXNFLASH
464 tristate "Support for NAND flash on BCM4706 BCMA bus"
465 depends on BCMA_NFLASH
467 BCMA bus can have various flash memories attached, they are
468 registered by bcma as platform devices. This enables driver for
469 NAND flash memories. For now only BCM4706 is supported.
471 config MTD_NAND_PLATFORM
472 tristate "Support for generic platform NAND driver"
475 This implements a generic NAND driver for on-SOC platform
476 devices. You will need to provide platform-specific functions
480 tristate "MTD driver for Olympus MAUSB-10 and Fujifilm DPC-R1"
483 These two (and possibly other) Alauda-based cardreaders for
484 SmartMedia and xD allow raw flash access.
486 config MTD_NAND_ORION
487 tristate "NAND Flash support for Marvell Orion SoC"
488 depends on PLAT_ORION
490 This enables the NAND flash controller on Orion machines.
492 No board specific support is done by this driver, each board
493 must advertise a platform_device for the driver to attach.
495 config MTD_NAND_FSL_ELBC
496 tristate "NAND support for Freescale eLBC controllers"
500 Various Freescale chips, including the 8313, include a NAND Flash
501 Controller Module with built-in hardware ECC capabilities.
502 Enabling this option will enable you to use this to control
503 external NAND devices.
505 config MTD_NAND_FSL_IFC
506 tristate "NAND support for Freescale IFC controller"
507 depends on MTD_NAND && FSL_SOC
510 Various Freescale chips e.g P1010, include a NAND Flash machine
511 with built-in hardware ECC capabilities.
512 Enabling this option will enable you to use this to control
513 external NAND devices.
515 config MTD_NAND_FSL_UPM
516 tristate "Support for NAND on Freescale UPM"
517 depends on PPC_83xx || PPC_85xx
520 Enables support for NAND Flash chips wired onto Freescale PowerPC
521 processor localbus with User-Programmable Machine support.
523 config MTD_NAND_MPC5121_NFC
524 tristate "MPC5121 built-in NAND Flash Controller support"
525 depends on PPC_MPC512x
527 This enables the driver for the NAND flash controller on the
531 tristate "MXC NAND support"
534 This enables the driver for the NAND flash controller on the
537 config MTD_NAND_SH_FLCTL
538 tristate "Support for NAND on Renesas SuperH FLCTL"
539 depends on SUPERH || ARCH_SHMOBILE
541 Several Renesas SuperH CPU has FLCTL. This option enables support
542 for NAND Flash using FLCTL.
544 config MTD_NAND_DAVINCI
545 tristate "Support NAND on DaVinci SoC"
546 depends on ARCH_DAVINCI
548 Enable the driver for NAND flash chips on Texas Instruments
551 config MTD_NAND_TXX9NDFMC
552 tristate "NAND Flash support for TXx9 SoC"
553 depends on SOC_TX4938 || SOC_TX4939
555 This enables the NAND flash controller on the TXx9 SoCs.
557 config MTD_NAND_SOCRATES
558 tristate "Support for NAND on Socrates board"
561 Enables support for NAND Flash chips wired onto Socrates board.
563 config MTD_NAND_NUC900
564 tristate "Support for NAND on Nuvoton NUC9xx/w90p910 evaluation boards."
565 depends on ARCH_W90X900
567 This enables the driver for the NAND Flash on evaluation board based
570 config MTD_NAND_JZ4740
571 tristate "Support for JZ4740 SoC NAND controller"
572 depends on MACH_JZ4740
574 Enables support for NAND Flash on JZ4740 SoC based boards.
577 tristate "Support for NAND on ST Micros FSMC"
578 depends on PLAT_SPEAR || PLAT_NOMADIK || MACH_U300
580 Enables support for NAND Flash chips on the ST Microelectronics
581 Flexible Static Memory Controller (FSMC)
584 tristate "Support for NAND on Lantiq XWAY SoC"
585 depends on LANTIQ && SOC_TYPE_XWAY
586 select MTD_NAND_PLATFORM
588 Enables support for NAND Flash chips on Lantiq XWAY SoCs. NAND is attached
589 to the External Bus Unit (EBU).