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
61 tristate "Support Denali NAND controller on Intel Moorestown"
63 Enable the driver for NAND flash on Intel Moorestown, using the
64 Denali NAND controller core.
66 config MTD_NAND_DENALI_SCRATCH_REG_ADDR
67 hex "Denali NAND size scratch register address"
69 depends on MTD_NAND_DENALI
71 Some platforms place the NAND chip size in a scratch register
72 because (some versions of) the driver aren't able to automatically
73 determine the size of certain chips. Set the address of the
74 scratch register here to enable this feature. On Intel Moorestown
75 boards, the scratch register is at 0xFF108018.
78 tristate "iPAQ H1900 flash"
79 depends on ARCH_PXA && BROKEN
81 This enables the driver for the iPAQ h1900 flash.
84 tristate "GPIO NAND Flash driver"
85 depends on GENERIC_GPIO && ARM
87 This enables a GPIO based NAND flash driver.
90 tristate "NAND Flash device on SPIA board"
93 If you had to ask, you don't have one. Say 'N'.
95 config MTD_NAND_AMS_DELTA
96 tristate "NAND Flash device on Amstrad E3"
97 depends on MACH_AMS_DELTA
100 Support for NAND flash on Amstrad E3 (Delta).
102 config MTD_NAND_OMAP2
103 tristate "NAND Flash device on OMAP2, OMAP3 and OMAP4"
104 depends on ARCH_OMAP2PLUS
106 Support for NAND flash on Texas Instruments OMAP2, OMAP3 and OMAP4
109 config MTD_NAND_OMAP_BCH
110 depends on MTD_NAND && MTD_NAND_OMAP2 && ARCH_OMAP3
111 bool "Enable support for hardware BCH error correction"
114 select BCH_CONST_PARAMS
116 Support for hardware BCH error correction.
119 prompt "BCH error correction capability"
120 depends on MTD_NAND_OMAP_BCH
122 config MTD_NAND_OMAP_BCH8
123 bool "8 bits / 512 bytes (recommended)"
125 Support correcting up to 8 bitflips per 512-byte block.
126 This will use 13 bytes of spare area per 512 bytes of page data.
127 This is the recommended mode, as 4-bit mode does not work
128 on some OMAP3 revisions, due to a hardware bug.
130 config MTD_NAND_OMAP_BCH4
131 bool "4 bits / 512 bytes"
133 Support correcting up to 4 bitflips per 512-byte block.
134 This will use 7 bytes of spare area per 512 bytes of page data.
135 Note that this mode does not work on some OMAP3 revisions, due to a
136 hardware bug. Please check your OMAP datasheet before selecting this
145 default 4 if MTD_NAND_OMAP_BCH4
146 default 8 if MTD_NAND_OMAP_BCH8
152 config MTD_NAND_RICOH
153 tristate "Ricoh xD card reader"
158 Enable support for Ricoh R5C852 xD card reader
159 You also need to enable ether
160 NAND SSFDC (SmartMedia) read only translation layer' or new
161 expermental, readwrite
162 'SmartMedia/xD new translation layer'
164 config MTD_NAND_AU1550
165 tristate "Au1550/1200 NAND support"
166 depends on MIPS_ALCHEMY
168 This enables the driver for the NAND flash controller on the
169 AMD/Alchemy 1550 SOC.
171 config MTD_NAND_BF5XX
172 tristate "Blackfin on-chip NAND Flash Controller driver"
173 depends on BF54x || BF52x
175 This enables the Blackfin on-chip NAND flash controller
177 No board specific support is done by this driver, each board
178 must advertise a platform_device for the driver to attach.
180 This driver can also be built as a module. If so, the module
181 will be called bf5xx-nand.
183 config MTD_NAND_BF5XX_HWECC
184 bool "BF5XX NAND Hardware ECC"
186 depends on MTD_NAND_BF5XX
188 Enable the use of the BF5XX's internal ECC generator when
191 config MTD_NAND_BF5XX_BOOTROM_ECC
192 bool "Use Blackfin BootROM ECC Layout"
194 depends on MTD_NAND_BF5XX_HWECC
196 If you wish to modify NAND pages and allow the Blackfin on-chip
197 BootROM to boot from them, say Y here. This is only necessary
198 if you are booting U-Boot out of NAND and you wish to update
199 U-Boot from Linux' userspace. Otherwise, you should say N here.
203 config MTD_NAND_RTC_FROM4
204 tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
205 depends on SH_SOLUTION_ENGINE
207 select REED_SOLOMON_DEC8
210 This enables the driver for the Renesas Technology AG-AND
211 flash interface board (FROM_BOARD4)
213 config MTD_NAND_PPCHAMELEONEVB
214 tristate "NAND Flash device on PPChameleonEVB board"
215 depends on PPCHAMELEONEVB && BROKEN
217 This enables the NAND flash driver on the PPChameleon EVB Board.
219 config MTD_NAND_S3C2410
220 tristate "NAND Flash support for Samsung S3C SoCs"
221 depends on ARCH_S3C24XX || ARCH_S3C64XX
223 This enables the NAND flash controller on the S3C24xx and S3C64xx
226 No board specific support is done by this driver, each board
227 must advertise a platform_device for the driver to attach.
229 config MTD_NAND_S3C2410_DEBUG
230 bool "Samsung S3C NAND driver debug"
231 depends on MTD_NAND_S3C2410
233 Enable debugging of the S3C NAND driver
235 config MTD_NAND_S3C2410_HWECC
236 bool "Samsung S3C NAND Hardware ECC"
237 depends on MTD_NAND_S3C2410
239 Enable the use of the controller's internal ECC generator when
240 using NAND. Early versions of the chips have had problems with
241 incorrect ECC generation, and if using these, the default of
242 software ECC is preferable.
245 tristate "NDFC NanD Flash Controller"
247 select MTD_NAND_ECC_SMC
249 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
251 config MTD_NAND_S3C2410_CLKSTOP
252 bool "Samsung S3C NAND IDLE clock stop"
253 depends on MTD_NAND_S3C2410
256 Stop the clock to the NAND controller when there is no chip
257 selected to save power. This will mean there is a small delay
258 when the is NAND chip selected or released, but will save
259 approximately 5mA of power when there is nothing happening.
261 config MTD_NAND_DISKONCHIP
262 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
263 depends on EXPERIMENTAL
266 select REED_SOLOMON_DEC16
268 This is a reimplementation of M-Systems DiskOnChip 2000,
269 Millennium and Millennium Plus as a standard NAND device driver,
270 as opposed to the earlier self-contained MTD device drivers.
271 This should enable, among other things, proper JFFS2 operation on
274 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
275 bool "Advanced detection options for DiskOnChip"
276 depends on MTD_NAND_DISKONCHIP
278 This option allows you to specify nonstandard address at which to
279 probe for a DiskOnChip, or to change the detection options. You
280 are unlikely to need any of this unless you are using LinuxBIOS.
283 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
284 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
285 depends on MTD_NAND_DISKONCHIP
288 By default, the probe for DiskOnChip devices will look for a
289 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
290 This option allows you to specify a single address at which to probe
291 for the device, which is useful if you have other devices in that
292 range which get upset when they are probed.
294 (Note that on PowerPC, the normal probe will only check at
297 Normally, you should leave this set to zero, to allow the probe at
298 the normal addresses.
300 config MTD_NAND_DISKONCHIP_PROBE_HIGH
301 bool "Probe high addresses"
302 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
304 By default, the probe for DiskOnChip devices will look for a
305 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
306 This option changes to make it probe between 0xFFFC8000 and
307 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
308 useful to you. Say 'N'.
310 config MTD_NAND_DISKONCHIP_BBTWRITE
311 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
312 depends on MTD_NAND_DISKONCHIP
314 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
315 and 2000 TSOP/Alon), Linux reserves some space at the end of the
316 device for the Bad Block Table (BBT). If you have existing INFTL
317 data on your device (created by non-Linux tools such as M-Systems'
318 DOS drivers), your data might overlap the area Linux wants to use for
319 the BBT. If this is a concern for you, leave this option disabled and
320 Linux will not write BBT data into this area.
321 The downside of leaving this option disabled is that if bad blocks
322 are detected by Linux, they will not be recorded in the BBT, which
323 could cause future problems.
324 Once you enable this option, new filesystems (INFTL or others, created
325 in Linux or other operating systems) will not use the reserved area.
326 The only reason not to enable this option is to prevent damage to
327 preexisting filesystems.
328 Even if you leave this disabled, you can enable BBT writes at module
329 load time (assuming you build diskonchip as a module) with the module
330 parameter "inftl_bbt_write=1".
332 config MTD_NAND_DOCG4
333 tristate "Support for DiskOnChip G4 (EXPERIMENTAL)"
334 depends on EXPERIMENTAL && HAS_IOMEM
338 Support for diskonchip G4 nand flash, found in various smartphones and
339 PDAs, among them the Palm Treo680, HTC Prophet and Wizard, Toshiba
340 Portege G900, Asus P526, and O2 XDA Zinc.
342 With this driver you will be able to use UBI and create a ubifs on the
343 device, so you may wish to consider enabling UBI and UBIFS as well.
345 These devices ship with the Mys/Sandisk SAFTL formatting, for which
346 there is currently no mtd parser, so you may want to use command line
347 partitioning to segregate write-protected blocks. On the Treo680, the
348 first five erase blocks (256KiB each) are write-protected, followed
349 by the block containing the saftl partition table. This is probably
352 config MTD_NAND_SHARPSL
353 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
357 tristate "NAND support for OLPC CAFÉ chip"
360 select REED_SOLOMON_DEC16
362 Use NAND flash attached to the CAFÉ chip designed for the OLPC
365 config MTD_NAND_CS553X
366 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
369 The CS553x companion chips for the AMD Geode processor
370 include NAND flash controllers with built-in hardware ECC
371 capabilities; enabling this option will allow you to use
372 these. The driver will check the MSRs to verify that the
373 controller is enabled for NAND, and currently requires that
374 the controller be in MMIO mode.
376 If you say "m", the module will be called cs553x_nand.
378 config MTD_NAND_ATMEL
379 tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
380 depends on ARCH_AT91 || AVR32
382 Enables support for NAND Flash / Smart Media Card interface
383 on Atmel AT91 and AVR32 processors.
385 config MTD_NAND_PXA3xx
386 tristate "Support for NAND flash devices on PXA3xx"
387 depends on PXA3xx || ARCH_MMP
389 This enables the driver for the NAND flash device found on
392 config MTD_NAND_SLC_LPC32XX
393 tristate "NXP LPC32xx SLC Controller"
394 depends on ARCH_LPC32XX
396 Enables support for NXP's LPC32XX SLC (i.e. for Single Level Cell
397 chips) NAND controller. This is the default for the PHYTEC 3250
398 reference board which contains a NAND256R3A2CZA6 chip.
400 Please check the actual NAND chip connected and its support
401 by the SLC NAND controller.
403 config MTD_NAND_MLC_LPC32XX
404 tristate "NXP LPC32xx MLC Controller"
405 depends on ARCH_LPC32XX
407 Uses the LPC32XX MLC (i.e. for Multi Level Cell chips) NAND
408 controller. This is the default for the WORK92105 controller
411 Please check the actual NAND chip connected and its support
412 by the MLC NAND controller.
414 config MTD_NAND_CM_X270
415 tristate "Support for NAND Flash on CM-X270 modules"
416 depends on MACH_ARMCORE
418 config MTD_NAND_PASEMI
419 tristate "NAND support for PA Semi PWRficient"
420 depends on PPC_PASEMI
422 Enables support for NAND Flash interface on PA Semi PWRficient
426 tristate "NAND Flash device on Toshiba Mobile IO Controller"
429 Support for NAND flash connected to a Toshiba Mobile IO
430 Controller in some PDAs, including the Sharp SL6000x.
432 config MTD_NAND_NANDSIM
433 tristate "Support for NAND Flash Simulator"
435 The simulator may simulate various NAND flash chips for the
438 config MTD_NAND_GPMI_NAND
439 tristate "GPMI NAND Flash Controller driver"
440 depends on MTD_NAND && MXS_DMA
442 Enables NAND Flash support for IMX23, IMX28 or IMX6.
443 The GPMI controller is very powerful, with the help of BCH
444 module, it can do the hardware ECC. The GPMI supports several
445 NAND flashs at the same time. The GPMI may conflicts with other
446 block, such as SD card. So pay attention to it when you enable
449 config MTD_NAND_PLATFORM
450 tristate "Support for generic platform NAND driver"
453 This implements a generic NAND driver for on-SOC platform
454 devices. You will need to provide platform-specific functions
458 tristate "MTD driver for Olympus MAUSB-10 and Fujifilm DPC-R1"
461 These two (and possibly other) Alauda-based cardreaders for
462 SmartMedia and xD allow raw flash access.
464 config MTD_NAND_ORION
465 tristate "NAND Flash support for Marvell Orion SoC"
466 depends on PLAT_ORION
468 This enables the NAND flash controller on Orion machines.
470 No board specific support is done by this driver, each board
471 must advertise a platform_device for the driver to attach.
473 config MTD_NAND_FSL_ELBC
474 tristate "NAND support for Freescale eLBC controllers"
478 Various Freescale chips, including the 8313, include a NAND Flash
479 Controller Module 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_IFC
484 tristate "NAND support for Freescale IFC controller"
485 depends on MTD_NAND && FSL_SOC
488 Various Freescale chips e.g P1010, include a NAND Flash machine
489 with built-in hardware ECC capabilities.
490 Enabling this option will enable you to use this to control
491 external NAND devices.
493 config MTD_NAND_FSL_UPM
494 tristate "Support for NAND on Freescale UPM"
495 depends on PPC_83xx || PPC_85xx
498 Enables support for NAND Flash chips wired onto Freescale PowerPC
499 processor localbus with User-Programmable Machine support.
501 config MTD_NAND_MPC5121_NFC
502 tristate "MPC5121 built-in NAND Flash Controller support"
503 depends on PPC_MPC512x
505 This enables the driver for the NAND flash controller on the
509 tristate "MXC NAND support"
512 This enables the driver for the NAND flash controller on the
515 config MTD_NAND_NOMADIK
516 tristate "ST Nomadik 8815 NAND support"
517 depends on ARCH_NOMADIK
519 Driver for the NAND flash controller on the Nomadik, with ECC.
521 config MTD_NAND_SH_FLCTL
522 tristate "Support for NAND on Renesas SuperH FLCTL"
523 depends on SUPERH || ARCH_SHMOBILE
525 Several Renesas SuperH CPU has FLCTL. This option enables support
526 for NAND Flash using FLCTL.
528 config MTD_NAND_DAVINCI
529 tristate "Support NAND on DaVinci SoC"
530 depends on ARCH_DAVINCI
532 Enable the driver for NAND flash chips on Texas Instruments
535 config MTD_NAND_TXX9NDFMC
536 tristate "NAND Flash support for TXx9 SoC"
537 depends on SOC_TX4938 || SOC_TX4939
539 This enables the NAND flash controller on the TXx9 SoCs.
541 config MTD_NAND_SOCRATES
542 tristate "Support for NAND on Socrates board"
545 Enables support for NAND Flash chips wired onto Socrates board.
547 config MTD_NAND_NUC900
548 tristate "Support for NAND on Nuvoton NUC9xx/w90p910 evaluation boards."
549 depends on ARCH_W90X900
551 This enables the driver for the NAND Flash on evaluation board based
554 config MTD_NAND_JZ4740
555 tristate "Support for JZ4740 SoC NAND controller"
556 depends on MACH_JZ4740
558 Enables support for NAND Flash on JZ4740 SoC based boards.
561 tristate "Support for NAND on ST Micros FSMC"
562 depends on PLAT_SPEAR || PLAT_NOMADIK || MACH_U300
564 Enables support for NAND Flash chips on the ST Microelectronics
565 Flexible Static Memory Controller (FSMC)
568 tristate "Support for NAND on Lantiq XWAY SoC"
569 depends on LANTIQ && SOC_TYPE_XWAY
570 select MTD_NAND_PLATFORM
572 Enables support for NAND Flash chips on Lantiq XWAY SoCs. NAND is attached
573 to the External Bus Unit (EBU).