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_PPCHAMELEONEVB
197 tristate "NAND Flash device on PPChameleonEVB board"
198 depends on PPCHAMELEONEVB && BROKEN
200 This enables the NAND flash driver on the PPChameleon EVB Board.
202 config MTD_NAND_S3C2410
203 tristate "NAND Flash support for Samsung S3C SoCs"
204 depends on ARCH_S3C24XX || ARCH_S3C64XX
206 This enables the NAND flash controller on the S3C24xx and S3C64xx
209 No board specific support is done by this driver, each board
210 must advertise a platform_device for the driver to attach.
212 config MTD_NAND_S3C2410_DEBUG
213 bool "Samsung S3C NAND driver debug"
214 depends on MTD_NAND_S3C2410
216 Enable debugging of the S3C NAND driver
218 config MTD_NAND_S3C2410_HWECC
219 bool "Samsung S3C NAND Hardware ECC"
220 depends on MTD_NAND_S3C2410
222 Enable the use of the controller's internal ECC generator when
223 using NAND. Early versions of the chips have had problems with
224 incorrect ECC generation, and if using these, the default of
225 software ECC is preferable.
228 tristate "NDFC NanD Flash Controller"
230 select MTD_NAND_ECC_SMC
232 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
234 config MTD_NAND_S3C2410_CLKSTOP
235 bool "Samsung S3C NAND IDLE clock stop"
236 depends on MTD_NAND_S3C2410
239 Stop the clock to the NAND controller when there is no chip
240 selected to save power. This will mean there is a small delay
241 when the is NAND chip selected or released, but will save
242 approximately 5mA of power when there is nothing happening.
244 config MTD_NAND_DISKONCHIP
245 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation)"
248 select REED_SOLOMON_DEC16
250 This is a reimplementation of M-Systems DiskOnChip 2000,
251 Millennium and Millennium Plus as a standard NAND device driver,
252 as opposed to the earlier self-contained MTD device drivers.
253 This should enable, among other things, proper JFFS2 operation on
256 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
257 bool "Advanced detection options for DiskOnChip"
258 depends on MTD_NAND_DISKONCHIP
260 This option allows you to specify nonstandard address at which to
261 probe for a DiskOnChip, or to change the detection options. You
262 are unlikely to need any of this unless you are using LinuxBIOS.
265 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
266 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
267 depends on MTD_NAND_DISKONCHIP
270 By default, the probe for DiskOnChip devices will look for a
271 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
272 This option allows you to specify a single address at which to probe
273 for the device, which is useful if you have other devices in that
274 range which get upset when they are probed.
276 (Note that on PowerPC, the normal probe will only check at
279 Normally, you should leave this set to zero, to allow the probe at
280 the normal addresses.
282 config MTD_NAND_DISKONCHIP_PROBE_HIGH
283 bool "Probe high addresses"
284 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
286 By default, the probe for DiskOnChip devices will look for a
287 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
288 This option changes to make it probe between 0xFFFC8000 and
289 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
290 useful to you. Say 'N'.
292 config MTD_NAND_DISKONCHIP_BBTWRITE
293 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
294 depends on MTD_NAND_DISKONCHIP
296 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
297 and 2000 TSOP/Alon), Linux reserves some space at the end of the
298 device for the Bad Block Table (BBT). If you have existing INFTL
299 data on your device (created by non-Linux tools such as M-Systems'
300 DOS drivers), your data might overlap the area Linux wants to use for
301 the BBT. If this is a concern for you, leave this option disabled and
302 Linux will not write BBT data into this area.
303 The downside of leaving this option disabled is that if bad blocks
304 are detected by Linux, they will not be recorded in the BBT, which
305 could cause future problems.
306 Once you enable this option, new filesystems (INFTL or others, created
307 in Linux or other operating systems) will not use the reserved area.
308 The only reason not to enable this option is to prevent damage to
309 preexisting filesystems.
310 Even if you leave this disabled, you can enable BBT writes at module
311 load time (assuming you build diskonchip as a module) with the module
312 parameter "inftl_bbt_write=1".
314 config MTD_NAND_DOCG4
315 tristate "Support for DiskOnChip G4"
320 Support for diskonchip G4 nand flash, found in various smartphones and
321 PDAs, among them the Palm Treo680, HTC Prophet and Wizard, Toshiba
322 Portege G900, Asus P526, and O2 XDA Zinc.
324 With this driver you will be able to use UBI and create a ubifs on the
325 device, so you may wish to consider enabling UBI and UBIFS as well.
327 These devices ship with the Mys/Sandisk SAFTL formatting, for which
328 there is currently no mtd parser, so you may want to use command line
329 partitioning to segregate write-protected blocks. On the Treo680, the
330 first five erase blocks (256KiB each) are write-protected, followed
331 by the block containing the saftl partition table. This is probably
334 config MTD_NAND_SHARPSL
335 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
339 tristate "NAND support for OLPC CAFÉ chip"
342 select REED_SOLOMON_DEC16
344 Use NAND flash attached to the CAFÉ chip designed for the OLPC
347 config MTD_NAND_CS553X
348 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
351 The CS553x companion chips for the AMD Geode processor
352 include NAND flash controllers with built-in hardware ECC
353 capabilities; enabling this option will allow you to use
354 these. The driver will check the MSRs to verify that the
355 controller is enabled for NAND, and currently requires that
356 the controller be in MMIO mode.
358 If you say "m", the module will be called cs553x_nand.
360 config MTD_NAND_ATMEL
361 tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
362 depends on ARCH_AT91 || AVR32
364 Enables support for NAND Flash / Smart Media Card interface
365 on Atmel AT91 and AVR32 processors.
367 config MTD_NAND_PXA3xx
368 tristate "Support for NAND flash devices on PXA3xx"
369 depends on PXA3xx || ARCH_MMP
371 This enables the driver for the NAND flash device found on
374 config MTD_NAND_SLC_LPC32XX
375 tristate "NXP LPC32xx SLC Controller"
376 depends on ARCH_LPC32XX
378 Enables support for NXP's LPC32XX SLC (i.e. for Single Level Cell
379 chips) NAND controller. This is the default for the PHYTEC 3250
380 reference board which contains a NAND256R3A2CZA6 chip.
382 Please check the actual NAND chip connected and its support
383 by the SLC NAND controller.
385 config MTD_NAND_MLC_LPC32XX
386 tristate "NXP LPC32xx MLC Controller"
387 depends on ARCH_LPC32XX
389 Uses the LPC32XX MLC (i.e. for Multi Level Cell chips) NAND
390 controller. This is the default for the WORK92105 controller
393 Please check the actual NAND chip connected and its support
394 by the MLC NAND controller.
396 config MTD_NAND_CM_X270
397 tristate "Support for NAND Flash on CM-X270 modules"
398 depends on MACH_ARMCORE
400 config MTD_NAND_PASEMI
401 tristate "NAND support for PA Semi PWRficient"
402 depends on PPC_PASEMI
404 Enables support for NAND Flash interface on PA Semi PWRficient
408 tristate "NAND Flash device on Toshiba Mobile IO Controller"
411 Support for NAND flash connected to a Toshiba Mobile IO
412 Controller in some PDAs, including the Sharp SL6000x.
414 config MTD_NAND_NANDSIM
415 tristate "Support for NAND Flash Simulator"
417 The simulator may simulate various NAND flash chips for the
420 config MTD_NAND_GPMI_NAND
421 tristate "GPMI NAND Flash Controller driver"
422 depends on MTD_NAND && MXS_DMA
424 Enables NAND Flash support for IMX23, IMX28 or IMX6.
425 The GPMI controller is very powerful, with the help of BCH
426 module, it can do the hardware ECC. The GPMI supports several
427 NAND flashs at the same time. The GPMI may conflicts with other
428 block, such as SD card. So pay attention to it when you enable
431 config MTD_NAND_BCM47XXNFLASH
432 tristate "Support for NAND flash on BCM4706 BCMA bus"
433 depends on BCMA_NFLASH
435 BCMA bus can have various flash memories attached, they are
436 registered by bcma as platform devices. This enables driver for
437 NAND flash memories. For now only BCM4706 is supported.
439 config MTD_NAND_PLATFORM
440 tristate "Support for generic platform NAND driver"
443 This implements a generic NAND driver for on-SOC platform
444 devices. You will need to provide platform-specific functions
448 tristate "MTD driver for Olympus MAUSB-10 and Fujifilm DPC-R1"
451 These two (and possibly other) Alauda-based cardreaders for
452 SmartMedia and xD allow raw flash access.
454 config MTD_NAND_ORION
455 tristate "NAND Flash support for Marvell Orion SoC"
456 depends on PLAT_ORION
458 This enables the NAND flash controller on Orion machines.
460 No board specific support is done by this driver, each board
461 must advertise a platform_device for the driver to attach.
463 config MTD_NAND_FSL_ELBC
464 tristate "NAND support for Freescale eLBC controllers"
468 Various Freescale chips, including the 8313, include a NAND Flash
469 Controller Module with built-in hardware ECC capabilities.
470 Enabling this option will enable you to use this to control
471 external NAND devices.
473 config MTD_NAND_FSL_IFC
474 tristate "NAND support for Freescale IFC controller"
475 depends on MTD_NAND && FSL_SOC
478 Various Freescale chips e.g P1010, include a NAND Flash machine
479 with built-in hardware ECC capabilities.
480 Enabling this option will enable you to use this to control
481 external NAND devices.
483 config MTD_NAND_FSL_UPM
484 tristate "Support for NAND on Freescale UPM"
485 depends on PPC_83xx || PPC_85xx
488 Enables support for NAND Flash chips wired onto Freescale PowerPC
489 processor localbus with User-Programmable Machine support.
491 config MTD_NAND_MPC5121_NFC
492 tristate "MPC5121 built-in NAND Flash Controller support"
493 depends on PPC_MPC512x
495 This enables the driver for the NAND flash controller on the
499 tristate "MXC NAND support"
502 This enables the driver for the NAND flash controller on the
505 config MTD_NAND_SH_FLCTL
506 tristate "Support for NAND on Renesas SuperH FLCTL"
507 depends on SUPERH || ARCH_SHMOBILE
509 Several Renesas SuperH CPU has FLCTL. This option enables support
510 for NAND Flash using FLCTL.
512 config MTD_NAND_DAVINCI
513 tristate "Support NAND on DaVinci SoC"
514 depends on ARCH_DAVINCI
516 Enable the driver for NAND flash chips on Texas Instruments
519 config MTD_NAND_TXX9NDFMC
520 tristate "NAND Flash support for TXx9 SoC"
521 depends on SOC_TX4938 || SOC_TX4939
523 This enables the NAND flash controller on the TXx9 SoCs.
525 config MTD_NAND_SOCRATES
526 tristate "Support for NAND on Socrates board"
529 Enables support for NAND Flash chips wired onto Socrates board.
531 config MTD_NAND_NUC900
532 tristate "Support for NAND on Nuvoton NUC9xx/w90p910 evaluation boards."
533 depends on ARCH_W90X900
535 This enables the driver for the NAND Flash on evaluation board based
538 config MTD_NAND_JZ4740
539 tristate "Support for JZ4740 SoC NAND controller"
540 depends on MACH_JZ4740
542 Enables support for NAND Flash on JZ4740 SoC based boards.
545 tristate "Support for NAND on ST Micros FSMC"
546 depends on PLAT_SPEAR || ARCH_NOMADIK || ARCH_U8500 || MACH_U300
548 Enables support for NAND Flash chips on the ST Microelectronics
549 Flexible Static Memory Controller (FSMC)
552 tristate "Support for NAND on Lantiq XWAY SoC"
553 depends on LANTIQ && SOC_TYPE_XWAY
554 select MTD_NAND_PLATFORM
556 Enables support for NAND Flash chips on Lantiq XWAY SoCs. NAND is attached
557 to the External Bus Unit (EBU).