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
53 tristate "Support Denali NAND controller"
55 Enable support for the Denali NAND controller. This should be
56 combined with either the PCI or platform drivers to provide device
59 config MTD_NAND_DENALI_PCI
60 tristate "Support Denali NAND controller on Intel Moorestown"
61 depends on PCI && MTD_NAND_DENALI
63 Enable the driver for NAND flash on Intel Moorestown, using the
64 Denali NAND controller core.
66 config MTD_NAND_DENALI_DT
67 tristate "Support Denali NAND controller as a DT device"
68 depends on HAVE_CLK && MTD_NAND_DENALI
70 Enable the driver for NAND flash on platforms using a Denali NAND
71 controller as a DT device.
73 config MTD_NAND_DENALI_SCRATCH_REG_ADDR
74 hex "Denali NAND size scratch register address"
76 depends on MTD_NAND_DENALI_PCI
78 Some platforms place the NAND chip size in a scratch register
79 because (some versions of) the driver aren't able to automatically
80 determine the size of certain chips. Set the address of the
81 scratch register here to enable this feature. On Intel Moorestown
82 boards, the scratch register is at 0xFF108018.
85 tristate "iPAQ H1900 flash"
86 depends on ARCH_PXA && BROKEN
88 This enables the driver for the iPAQ h1900 flash.
91 tristate "GPIO NAND Flash driver"
92 depends on GENERIC_GPIO && ARM
94 This enables a GPIO based NAND flash driver.
96 config MTD_NAND_AMS_DELTA
97 tristate "NAND Flash device on Amstrad E3"
98 depends on MACH_AMS_DELTA
101 Support for NAND flash on Amstrad E3 (Delta).
103 config MTD_NAND_OMAP2
104 tristate "NAND Flash device on OMAP2, OMAP3 and OMAP4"
105 depends on ARCH_OMAP2PLUS
107 Support for NAND flash on Texas Instruments OMAP2, OMAP3 and OMAP4
110 config MTD_NAND_OMAP_BCH
111 depends on MTD_NAND && MTD_NAND_OMAP2 && ARCH_OMAP3
112 bool "Enable support for hardware BCH error correction"
115 select BCH_CONST_PARAMS
117 Support for hardware BCH error correction.
120 prompt "BCH error correction capability"
121 depends on MTD_NAND_OMAP_BCH
123 config MTD_NAND_OMAP_BCH8
124 bool "8 bits / 512 bytes (recommended)"
126 Support correcting up to 8 bitflips per 512-byte block.
127 This will use 13 bytes of spare area per 512 bytes of page data.
128 This is the recommended mode, as 4-bit mode does not work
129 on some OMAP3 revisions, due to a hardware bug.
131 config MTD_NAND_OMAP_BCH4
132 bool "4 bits / 512 bytes"
134 Support correcting up to 4 bitflips per 512-byte block.
135 This will use 7 bytes of spare area per 512 bytes of page data.
136 Note that this mode does not work on some OMAP3 revisions, due to a
137 hardware bug. Please check your OMAP datasheet before selecting this
146 default 4 if MTD_NAND_OMAP_BCH4
147 default 8 if MTD_NAND_OMAP_BCH8
153 config MTD_NAND_RICOH
154 tristate "Ricoh xD card reader"
159 Enable support for Ricoh R5C852 xD card reader
160 You also need to enable ether
161 NAND SSFDC (SmartMedia) read only translation layer' or new
162 expermental, readwrite
163 'SmartMedia/xD new translation layer'
165 config MTD_NAND_AU1550
166 tristate "Au1550/1200 NAND support"
167 depends on MIPS_ALCHEMY
169 This enables the driver for the NAND flash controller on the
170 AMD/Alchemy 1550 SOC.
172 config MTD_NAND_BF5XX
173 tristate "Blackfin on-chip NAND Flash Controller driver"
174 depends on BF54x || BF52x
176 This enables the Blackfin on-chip NAND flash controller
178 No board specific support is done by this driver, each board
179 must advertise a platform_device for the driver to attach.
181 This driver can also be built as a module. If so, the module
182 will be called bf5xx-nand.
184 config MTD_NAND_BF5XX_HWECC
185 bool "BF5XX NAND Hardware ECC"
187 depends on MTD_NAND_BF5XX
189 Enable the use of the BF5XX's internal ECC generator when
192 config MTD_NAND_BF5XX_BOOTROM_ECC
193 bool "Use Blackfin BootROM ECC Layout"
195 depends on MTD_NAND_BF5XX_HWECC
197 If you wish to modify NAND pages and allow the Blackfin on-chip
198 BootROM to boot from them, say Y here. This is only necessary
199 if you are booting U-Boot out of NAND and you wish to update
200 U-Boot from Linux' userspace. Otherwise, you should say N here.
204 config MTD_NAND_RTC_FROM4
205 tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
206 depends on SH_SOLUTION_ENGINE
208 select REED_SOLOMON_DEC8
211 This enables the driver for the Renesas Technology AG-AND
212 flash interface board (FROM_BOARD4)
214 config MTD_NAND_PPCHAMELEONEVB
215 tristate "NAND Flash device on PPChameleonEVB board"
216 depends on PPCHAMELEONEVB && BROKEN
218 This enables the NAND flash driver on the PPChameleon EVB Board.
220 config MTD_NAND_S3C2410
221 tristate "NAND Flash support for Samsung S3C SoCs"
222 depends on ARCH_S3C24XX || ARCH_S3C64XX
224 This enables the NAND flash controller on the S3C24xx and S3C64xx
227 No board specific support is done by this driver, each board
228 must advertise a platform_device for the driver to attach.
230 config MTD_NAND_S3C2410_DEBUG
231 bool "Samsung S3C NAND driver debug"
232 depends on MTD_NAND_S3C2410
234 Enable debugging of the S3C NAND driver
236 config MTD_NAND_S3C2410_HWECC
237 bool "Samsung S3C NAND Hardware ECC"
238 depends on MTD_NAND_S3C2410
240 Enable the use of the controller's internal ECC generator when
241 using NAND. Early versions of the chips have had problems with
242 incorrect ECC generation, and if using these, the default of
243 software ECC is preferable.
246 tristate "NDFC NanD Flash Controller"
248 select MTD_NAND_ECC_SMC
250 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
252 config MTD_NAND_S3C2410_CLKSTOP
253 bool "Samsung S3C NAND IDLE clock stop"
254 depends on MTD_NAND_S3C2410
257 Stop the clock to the NAND controller when there is no chip
258 selected to save power. This will mean there is a small delay
259 when the is NAND chip selected or released, but will save
260 approximately 5mA of power when there is nothing happening.
262 config MTD_NAND_DISKONCHIP
263 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
264 depends on EXPERIMENTAL
267 select REED_SOLOMON_DEC16
269 This is a reimplementation of M-Systems DiskOnChip 2000,
270 Millennium and Millennium Plus as a standard NAND device driver,
271 as opposed to the earlier self-contained MTD device drivers.
272 This should enable, among other things, proper JFFS2 operation on
275 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
276 bool "Advanced detection options for DiskOnChip"
277 depends on MTD_NAND_DISKONCHIP
279 This option allows you to specify nonstandard address at which to
280 probe for a DiskOnChip, or to change the detection options. You
281 are unlikely to need any of this unless you are using LinuxBIOS.
284 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
285 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
286 depends on MTD_NAND_DISKONCHIP
289 By default, the probe for DiskOnChip devices will look for a
290 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
291 This option allows you to specify a single address at which to probe
292 for the device, which is useful if you have other devices in that
293 range which get upset when they are probed.
295 (Note that on PowerPC, the normal probe will only check at
298 Normally, you should leave this set to zero, to allow the probe at
299 the normal addresses.
301 config MTD_NAND_DISKONCHIP_PROBE_HIGH
302 bool "Probe high addresses"
303 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
305 By default, the probe for DiskOnChip devices will look for a
306 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
307 This option changes to make it probe between 0xFFFC8000 and
308 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
309 useful to you. Say 'N'.
311 config MTD_NAND_DISKONCHIP_BBTWRITE
312 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
313 depends on MTD_NAND_DISKONCHIP
315 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
316 and 2000 TSOP/Alon), Linux reserves some space at the end of the
317 device for the Bad Block Table (BBT). If you have existing INFTL
318 data on your device (created by non-Linux tools such as M-Systems'
319 DOS drivers), your data might overlap the area Linux wants to use for
320 the BBT. If this is a concern for you, leave this option disabled and
321 Linux will not write BBT data into this area.
322 The downside of leaving this option disabled is that if bad blocks
323 are detected by Linux, they will not be recorded in the BBT, which
324 could cause future problems.
325 Once you enable this option, new filesystems (INFTL or others, created
326 in Linux or other operating systems) will not use the reserved area.
327 The only reason not to enable this option is to prevent damage to
328 preexisting filesystems.
329 Even if you leave this disabled, you can enable BBT writes at module
330 load time (assuming you build diskonchip as a module) with the module
331 parameter "inftl_bbt_write=1".
333 config MTD_NAND_DOCG4
334 tristate "Support for DiskOnChip G4 (EXPERIMENTAL)"
335 depends on EXPERIMENTAL && HAS_IOMEM
339 Support for diskonchip G4 nand flash, found in various smartphones and
340 PDAs, among them the Palm Treo680, HTC Prophet and Wizard, Toshiba
341 Portege G900, Asus P526, and O2 XDA Zinc.
343 With this driver you will be able to use UBI and create a ubifs on the
344 device, so you may wish to consider enabling UBI and UBIFS as well.
346 These devices ship with the Mys/Sandisk SAFTL formatting, for which
347 there is currently no mtd parser, so you may want to use command line
348 partitioning to segregate write-protected blocks. On the Treo680, the
349 first five erase blocks (256KiB each) are write-protected, followed
350 by the block containing the saftl partition table. This is probably
353 config MTD_NAND_SHARPSL
354 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
358 tristate "NAND support for OLPC CAFÉ chip"
361 select REED_SOLOMON_DEC16
363 Use NAND flash attached to the CAFÉ chip designed for the OLPC
366 config MTD_NAND_CS553X
367 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
370 The CS553x companion chips for the AMD Geode processor
371 include NAND flash controllers with built-in hardware ECC
372 capabilities; enabling this option will allow you to use
373 these. The driver will check the MSRs to verify that the
374 controller is enabled for NAND, and currently requires that
375 the controller be in MMIO mode.
377 If you say "m", the module will be called cs553x_nand.
379 config MTD_NAND_ATMEL
380 tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
381 depends on ARCH_AT91 || AVR32
383 Enables support for NAND Flash / Smart Media Card interface
384 on Atmel AT91 and AVR32 processors.
386 config MTD_NAND_PXA3xx
387 tristate "Support for NAND flash devices on PXA3xx"
388 depends on PXA3xx || ARCH_MMP
390 This enables the driver for the NAND flash device found on
393 config MTD_NAND_SLC_LPC32XX
394 tristate "NXP LPC32xx SLC Controller"
395 depends on ARCH_LPC32XX
397 Enables support for NXP's LPC32XX SLC (i.e. for Single Level Cell
398 chips) NAND controller. This is the default for the PHYTEC 3250
399 reference board which contains a NAND256R3A2CZA6 chip.
401 Please check the actual NAND chip connected and its support
402 by the SLC NAND controller.
404 config MTD_NAND_MLC_LPC32XX
405 tristate "NXP LPC32xx MLC Controller"
406 depends on ARCH_LPC32XX
408 Uses the LPC32XX MLC (i.e. for Multi Level Cell chips) NAND
409 controller. This is the default for the WORK92105 controller
412 Please check the actual NAND chip connected and its support
413 by the MLC NAND controller.
415 config MTD_NAND_CM_X270
416 tristate "Support for NAND Flash on CM-X270 modules"
417 depends on MACH_ARMCORE
419 config MTD_NAND_PASEMI
420 tristate "NAND support for PA Semi PWRficient"
421 depends on PPC_PASEMI
423 Enables support for NAND Flash interface on PA Semi PWRficient
427 tristate "NAND Flash device on Toshiba Mobile IO Controller"
430 Support for NAND flash connected to a Toshiba Mobile IO
431 Controller in some PDAs, including the Sharp SL6000x.
433 config MTD_NAND_NANDSIM
434 tristate "Support for NAND Flash Simulator"
436 The simulator may simulate various NAND flash chips for the
439 config MTD_NAND_GPMI_NAND
440 tristate "GPMI NAND Flash Controller driver"
441 depends on MTD_NAND && MXS_DMA
443 Enables NAND Flash support for IMX23, IMX28 or IMX6.
444 The GPMI controller is very powerful, with the help of BCH
445 module, it can do the hardware ECC. The GPMI supports several
446 NAND flashs at the same time. The GPMI may conflicts with other
447 block, such as SD card. So pay attention to it when you enable
450 config MTD_NAND_BCM47XXNFLASH
451 tristate "Support for NAND flash on BCM4706 BCMA bus"
452 depends on BCMA_NFLASH
454 BCMA bus can have various flash memories attached, they are
455 registered by bcma as platform devices. This enables driver for
456 NAND flash memories. For now only BCM4706 is supported.
458 config MTD_NAND_PLATFORM
459 tristate "Support for generic platform NAND driver"
462 This implements a generic NAND driver for on-SOC platform
463 devices. You will need to provide platform-specific functions
467 tristate "MTD driver for Olympus MAUSB-10 and Fujifilm DPC-R1"
470 These two (and possibly other) Alauda-based cardreaders for
471 SmartMedia and xD allow raw flash access.
473 config MTD_NAND_ORION
474 tristate "NAND Flash support for Marvell Orion SoC"
475 depends on PLAT_ORION
477 This enables the NAND flash controller on Orion machines.
479 No board specific support is done by this driver, each board
480 must advertise a platform_device for the driver to attach.
482 config MTD_NAND_FSL_ELBC
483 tristate "NAND support for Freescale eLBC controllers"
487 Various Freescale chips, including the 8313, include a NAND Flash
488 Controller Module with built-in hardware ECC capabilities.
489 Enabling this option will enable you to use this to control
490 external NAND devices.
492 config MTD_NAND_FSL_IFC
493 tristate "NAND support for Freescale IFC controller"
494 depends on MTD_NAND && FSL_SOC
497 Various Freescale chips e.g P1010, include a NAND Flash machine
498 with built-in hardware ECC capabilities.
499 Enabling this option will enable you to use this to control
500 external NAND devices.
502 config MTD_NAND_FSL_UPM
503 tristate "Support for NAND on Freescale UPM"
504 depends on PPC_83xx || PPC_85xx
507 Enables support for NAND Flash chips wired onto Freescale PowerPC
508 processor localbus with User-Programmable Machine support.
510 config MTD_NAND_MPC5121_NFC
511 tristate "MPC5121 built-in NAND Flash Controller support"
512 depends on PPC_MPC512x
514 This enables the driver for the NAND flash controller on the
518 tristate "MXC NAND support"
521 This enables the driver for the NAND flash controller on the
524 config MTD_NAND_SH_FLCTL
525 tristate "Support for NAND on Renesas SuperH FLCTL"
526 depends on SUPERH || ARCH_SHMOBILE
528 Several Renesas SuperH CPU has FLCTL. This option enables support
529 for NAND Flash using FLCTL.
531 config MTD_NAND_DAVINCI
532 tristate "Support NAND on DaVinci SoC"
533 depends on ARCH_DAVINCI
535 Enable the driver for NAND flash chips on Texas Instruments
538 config MTD_NAND_TXX9NDFMC
539 tristate "NAND Flash support for TXx9 SoC"
540 depends on SOC_TX4938 || SOC_TX4939
542 This enables the NAND flash controller on the TXx9 SoCs.
544 config MTD_NAND_SOCRATES
545 tristate "Support for NAND on Socrates board"
548 Enables support for NAND Flash chips wired onto Socrates board.
550 config MTD_NAND_NUC900
551 tristate "Support for NAND on Nuvoton NUC9xx/w90p910 evaluation boards."
552 depends on ARCH_W90X900
554 This enables the driver for the NAND Flash on evaluation board based
557 config MTD_NAND_JZ4740
558 tristate "Support for JZ4740 SoC NAND controller"
559 depends on MACH_JZ4740
561 Enables support for NAND Flash on JZ4740 SoC based boards.
564 tristate "Support for NAND on ST Micros FSMC"
565 depends on PLAT_SPEAR || ARCH_NOMADIK || ARCH_U8500 || MACH_U300
567 Enables support for NAND Flash chips on the ST Microelectronics
568 Flexible Static Memory Controller (FSMC)
571 tristate "Support for NAND on Lantiq XWAY SoC"
572 depends on LANTIQ && SOC_TYPE_XWAY
573 select MTD_NAND_PLATFORM
575 Enables support for NAND Flash chips on Lantiq XWAY SoCs. NAND is attached
576 to the External Bus Unit (EBU).