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>.
25 config MTD_NAND_VERIFY_WRITE
26 bool "Verify NAND page writes"
28 This adds an extra check when data is written to the flash. The
29 NAND flash device internally checks only bits transitioning
30 from 1 to 0. There is a rare possibility that even though the
31 device thinks the write was successful, a bit could have been
32 flipped accidentally due to device wear or something else.
37 depends on MTD_NAND_ECC_BCH
40 config MTD_NAND_ECC_BCH
41 bool "Support software BCH ECC"
44 This enables support for software BCH error correction. Binary BCH
45 codes are more powerful and cpu intensive than traditional Hamming
46 ECC codes. They are used with NAND devices requiring more than 1 bit
53 config MTD_NAND_MUSEUM_IDS
54 bool "Enable chip ids for obsolete ancient NAND devices"
57 Enable this option only when your board has first generation
58 NAND chips (page size 256 byte, erase size 4-8KiB). The IDs
59 of these chips were reused by later, larger chips.
61 config MTD_NAND_AUTCPU12
62 tristate "SmartMediaCard on autronix autcpu12 board"
63 depends on ARCH_AUTCPU12
65 This enables the driver for the autronix autcpu12 board to
66 access the SmartMediaCard.
68 config MTD_NAND_DENALI
70 tristate "Support Denali NAND controller on Intel Moorestown"
72 Enable the driver for NAND flash on Intel Moorestown, using the
73 Denali NAND controller core.
75 config MTD_NAND_DENALI_SCRATCH_REG_ADDR
76 hex "Denali NAND size scratch register address"
78 depends on MTD_NAND_DENALI
80 Some platforms place the NAND chip size in a scratch register
81 because (some versions of) the driver aren't able to automatically
82 determine the size of certain chips. Set the address of the
83 scratch register here to enable this feature. On Intel Moorestown
84 boards, the scratch register is at 0xFF108018.
87 tristate "iPAQ H1900 flash"
88 depends on ARCH_PXA && BROKEN
90 This enables the driver for the iPAQ h1900 flash.
93 tristate "GPIO NAND Flash driver"
94 depends on GENERIC_GPIO && ARM
96 This enables a GPIO based NAND flash driver.
99 tristate "NAND Flash device on SPIA board"
100 depends on ARCH_P720T
102 If you had to ask, you don't have one. Say 'N'.
104 config MTD_NAND_AMS_DELTA
105 tristate "NAND Flash device on Amstrad E3"
106 depends on MACH_AMS_DELTA
109 Support for NAND flash on Amstrad E3 (Delta).
111 config MTD_NAND_OMAP2
112 tristate "NAND Flash device on OMAP2, OMAP3 and OMAP4"
113 depends on ARCH_OMAP2PLUS
115 Support for NAND flash on Texas Instruments OMAP2, OMAP3 and OMAP4
118 config MTD_NAND_OMAP_BCH
119 depends on MTD_NAND && MTD_NAND_OMAP2 && ARCH_OMAP3
120 bool "Enable support for hardware BCH error correction"
123 select BCH_CONST_PARAMS
125 Support for hardware BCH error correction.
128 prompt "BCH error correction capability"
129 depends on MTD_NAND_OMAP_BCH
131 config MTD_NAND_OMAP_BCH8
132 bool "8 bits / 512 bytes (recommended)"
134 Support correcting up to 8 bitflips per 512-byte block.
135 This will use 13 bytes of spare area per 512 bytes of page data.
136 This is the recommended mode, as 4-bit mode does not work
137 on some OMAP3 revisions, due to a hardware bug.
139 config MTD_NAND_OMAP_BCH4
140 bool "4 bits / 512 bytes"
142 Support correcting up to 4 bitflips per 512-byte block.
143 This will use 7 bytes of spare area per 512 bytes of page data.
144 Note that this mode does not work on some OMAP3 revisions, due to a
145 hardware bug. Please check your OMAP datasheet before selecting this
154 default 4 if MTD_NAND_OMAP_BCH4
155 default 8 if MTD_NAND_OMAP_BCH8
161 config MTD_NAND_RICOH
162 tristate "Ricoh xD card reader"
167 Enable support for Ricoh R5C852 xD card reader
168 You also need to enable ether
169 NAND SSFDC (SmartMedia) read only translation layer' or new
170 expermental, readwrite
171 'SmartMedia/xD new translation layer'
173 config MTD_NAND_AU1550
174 tristate "Au1550/1200 NAND support"
175 depends on MIPS_ALCHEMY
177 This enables the driver for the NAND flash controller on the
178 AMD/Alchemy 1550 SOC.
180 config MTD_NAND_BF5XX
181 tristate "Blackfin on-chip NAND Flash Controller driver"
182 depends on BF54x || BF52x
184 This enables the Blackfin on-chip NAND flash controller
186 No board specific support is done by this driver, each board
187 must advertise a platform_device for the driver to attach.
189 This driver can also be built as a module. If so, the module
190 will be called bf5xx-nand.
192 config MTD_NAND_BF5XX_HWECC
193 bool "BF5XX NAND Hardware ECC"
195 depends on MTD_NAND_BF5XX
197 Enable the use of the BF5XX's internal ECC generator when
200 config MTD_NAND_BF5XX_BOOTROM_ECC
201 bool "Use Blackfin BootROM ECC Layout"
203 depends on MTD_NAND_BF5XX_HWECC
205 If you wish to modify NAND pages and allow the Blackfin on-chip
206 BootROM to boot from them, say Y here. This is only necessary
207 if you are booting U-Boot out of NAND and you wish to update
208 U-Boot from Linux' userspace. Otherwise, you should say N here.
212 config MTD_NAND_RTC_FROM4
213 tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
214 depends on SH_SOLUTION_ENGINE
216 select REED_SOLOMON_DEC8
219 This enables the driver for the Renesas Technology AG-AND
220 flash interface board (FROM_BOARD4)
222 config MTD_NAND_PPCHAMELEONEVB
223 tristate "NAND Flash device on PPChameleonEVB board"
224 depends on PPCHAMELEONEVB && BROKEN
226 This enables the NAND flash driver on the PPChameleon EVB Board.
228 config MTD_NAND_S3C2410
229 tristate "NAND Flash support for Samsung S3C SoCs"
230 depends on ARCH_S3C24XX || ARCH_S3C64XX
232 This enables the NAND flash controller on the S3C24xx and S3C64xx
235 No board specific support is done by this driver, each board
236 must advertise a platform_device for the driver to attach.
238 config MTD_NAND_S3C2410_DEBUG
239 bool "Samsung S3C NAND driver debug"
240 depends on MTD_NAND_S3C2410
242 Enable debugging of the S3C NAND driver
244 config MTD_NAND_S3C2410_HWECC
245 bool "Samsung S3C NAND Hardware ECC"
246 depends on MTD_NAND_S3C2410
248 Enable the use of the controller's internal ECC generator when
249 using NAND. Early versions of the chips have had problems with
250 incorrect ECC generation, and if using these, the default of
251 software ECC is preferable.
254 tristate "NDFC NanD Flash Controller"
256 select MTD_NAND_ECC_SMC
258 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
260 config MTD_NAND_S3C2410_CLKSTOP
261 bool "Samsung S3C NAND IDLE clock stop"
262 depends on MTD_NAND_S3C2410
265 Stop the clock to the NAND controller when there is no chip
266 selected to save power. This will mean there is a small delay
267 when the is NAND chip selected or released, but will save
268 approximately 5mA of power when there is nothing happening.
270 config MTD_NAND_BCM_UMI
271 tristate "NAND Flash support for BCM Reference Boards"
272 depends on ARCH_BCMRING
274 This enables the NAND flash controller on the BCM UMI block.
276 No board specific support is done by this driver, each board
277 must advertise a platform_device for the driver to attach.
279 config MTD_NAND_BCM_UMI_HWCS
280 bool "BCM UMI NAND Hardware CS"
281 depends on MTD_NAND_BCM_UMI
283 Enable the use of the BCM UMI block's internal CS using NAND.
284 This should only be used if you know the external NAND CS can toggle.
286 config MTD_NAND_DISKONCHIP
287 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
288 depends on EXPERIMENTAL
291 select REED_SOLOMON_DEC16
293 This is a reimplementation of M-Systems DiskOnChip 2000,
294 Millennium and Millennium Plus as a standard NAND device driver,
295 as opposed to the earlier self-contained MTD device drivers.
296 This should enable, among other things, proper JFFS2 operation on
299 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
300 bool "Advanced detection options for DiskOnChip"
301 depends on MTD_NAND_DISKONCHIP
303 This option allows you to specify nonstandard address at which to
304 probe for a DiskOnChip, or to change the detection options. You
305 are unlikely to need any of this unless you are using LinuxBIOS.
308 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
309 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
310 depends on MTD_NAND_DISKONCHIP
313 By default, the probe for DiskOnChip devices will look for a
314 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
315 This option allows you to specify a single address at which to probe
316 for the device, which is useful if you have other devices in that
317 range which get upset when they are probed.
319 (Note that on PowerPC, the normal probe will only check at
322 Normally, you should leave this set to zero, to allow the probe at
323 the normal addresses.
325 config MTD_NAND_DISKONCHIP_PROBE_HIGH
326 bool "Probe high addresses"
327 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
329 By default, the probe for DiskOnChip devices will look for a
330 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
331 This option changes to make it probe between 0xFFFC8000 and
332 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
333 useful to you. Say 'N'.
335 config MTD_NAND_DISKONCHIP_BBTWRITE
336 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
337 depends on MTD_NAND_DISKONCHIP
339 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
340 and 2000 TSOP/Alon), Linux reserves some space at the end of the
341 device for the Bad Block Table (BBT). If you have existing INFTL
342 data on your device (created by non-Linux tools such as M-Systems'
343 DOS drivers), your data might overlap the area Linux wants to use for
344 the BBT. If this is a concern for you, leave this option disabled and
345 Linux will not write BBT data into this area.
346 The downside of leaving this option disabled is that if bad blocks
347 are detected by Linux, they will not be recorded in the BBT, which
348 could cause future problems.
349 Once you enable this option, new filesystems (INFTL or others, created
350 in Linux or other operating systems) will not use the reserved area.
351 The only reason not to enable this option is to prevent damage to
352 preexisting filesystems.
353 Even if you leave this disabled, you can enable BBT writes at module
354 load time (assuming you build diskonchip as a module) with the module
355 parameter "inftl_bbt_write=1".
357 config MTD_NAND_DOCG4
358 tristate "Support for DiskOnChip G4 (EXPERIMENTAL)"
359 depends on EXPERIMENTAL
363 Support for diskonchip G4 nand flash, found in various smartphones and
364 PDAs, among them the Palm Treo680, HTC Prophet and Wizard, Toshiba
365 Portege G900, Asus P526, and O2 XDA Zinc.
367 With this driver you will be able to use UBI and create a ubifs on the
368 device, so you may wish to consider enabling UBI and UBIFS as well.
370 These devices ship with the Mys/Sandisk SAFTL formatting, for which
371 there is currently no mtd parser, so you may want to use command line
372 partitioning to segregate write-protected blocks. On the Treo680, the
373 first five erase blocks (256KiB each) are write-protected, followed
374 by the block containing the saftl partition table. This is probably
377 config MTD_NAND_SHARPSL
378 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
382 tristate "NAND support for OLPC CAFÉ chip"
385 select REED_SOLOMON_DEC16
387 Use NAND flash attached to the CAFÉ chip designed for the OLPC
390 config MTD_NAND_CS553X
391 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
394 The CS553x companion chips for the AMD Geode processor
395 include NAND flash controllers with built-in hardware ECC
396 capabilities; enabling this option will allow you to use
397 these. The driver will check the MSRs to verify that the
398 controller is enabled for NAND, and currently requires that
399 the controller be in MMIO mode.
401 If you say "m", the module will be called cs553x_nand.
403 config MTD_NAND_ATMEL
404 tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
405 depends on ARCH_AT91 || AVR32
407 Enables support for NAND Flash / Smart Media Card interface
408 on Atmel AT91 and AVR32 processors.
410 config MTD_NAND_PXA3xx
411 tristate "Support for NAND flash devices on PXA3xx"
412 depends on PXA3xx || ARCH_MMP
414 This enables the driver for the NAND flash device found on
417 config MTD_NAND_SLC_LPC32XX
418 tristate "NXP LPC32xx SLC Controller"
419 depends on ARCH_LPC32XX
421 Enables support for NXP's LPC32XX SLC (i.e. for Single Level Cell
422 chips) NAND controller. This is the default for the PHYTEC 3250
423 reference board which contains a NAND256R3A2CZA6 chip.
425 Please check the actual NAND chip connected and its support
426 by the SLC NAND controller.
428 config MTD_NAND_MLC_LPC32XX
429 tristate "NXP LPC32xx MLC Controller"
430 depends on ARCH_LPC32XX
432 Uses the LPC32XX MLC (i.e. for Multi Level Cell chips) NAND
433 controller. This is the default for the WORK92105 controller
436 Please check the actual NAND chip connected and its support
437 by the MLC NAND controller.
439 config MTD_NAND_CM_X270
440 tristate "Support for NAND Flash on CM-X270 modules"
441 depends on MACH_ARMCORE
443 config MTD_NAND_PASEMI
444 tristate "NAND support for PA Semi PWRficient"
445 depends on PPC_PASEMI
447 Enables support for NAND Flash interface on PA Semi PWRficient
451 tristate "NAND Flash device on Toshiba Mobile IO Controller"
454 Support for NAND flash connected to a Toshiba Mobile IO
455 Controller in some PDAs, including the Sharp SL6000x.
457 config MTD_NAND_NANDSIM
458 tristate "Support for NAND Flash Simulator"
460 The simulator may simulate various NAND flash chips for the
463 config MTD_NAND_GPMI_NAND
464 bool "GPMI NAND Flash Controller driver"
465 depends on MTD_NAND && MXS_DMA
467 Enables NAND Flash support for IMX23 or IMX28.
468 The GPMI controller is very powerful, with the help of BCH
469 module, it can do the hardware ECC. The GPMI supports several
470 NAND flashs at the same time. The GPMI may conflicts with other
471 block, such as SD card. So pay attention to it when you enable
474 config MTD_NAND_PLATFORM
475 tristate "Support for generic platform NAND driver"
478 This implements a generic NAND driver for on-SOC platform
479 devices. You will need to provide platform-specific functions
483 tristate "MTD driver for Olympus MAUSB-10 and Fujifilm DPC-R1"
486 These two (and possibly other) Alauda-based cardreaders for
487 SmartMedia and xD allow raw flash access.
489 config MTD_NAND_ORION
490 tristate "NAND Flash support for Marvell Orion SoC"
491 depends on PLAT_ORION
493 This enables the NAND flash controller on Orion machines.
495 No board specific support is done by this driver, each board
496 must advertise a platform_device for the driver to attach.
498 config MTD_NAND_FSL_ELBC
499 tristate "NAND support for Freescale eLBC controllers"
503 Various Freescale chips, including the 8313, include a NAND Flash
504 Controller Module with built-in hardware ECC capabilities.
505 Enabling this option will enable you to use this to control
506 external NAND devices.
508 config MTD_NAND_FSL_IFC
509 tristate "NAND support for Freescale IFC controller"
510 depends on MTD_NAND && FSL_SOC
513 Various Freescale chips e.g P1010, include a NAND Flash machine
514 with built-in hardware ECC capabilities.
515 Enabling this option will enable you to use this to control
516 external NAND devices.
518 config MTD_NAND_FSL_UPM
519 tristate "Support for NAND on Freescale UPM"
520 depends on PPC_83xx || PPC_85xx
523 Enables support for NAND Flash chips wired onto Freescale PowerPC
524 processor localbus with User-Programmable Machine support.
526 config MTD_NAND_MPC5121_NFC
527 tristate "MPC5121 built-in NAND Flash Controller support"
528 depends on PPC_MPC512x
530 This enables the driver for the NAND flash controller on the
534 tristate "MXC NAND support"
537 This enables the driver for the NAND flash controller on the
540 config MTD_NAND_NOMADIK
541 tristate "ST Nomadik 8815 NAND support"
542 depends on ARCH_NOMADIK
544 Driver for the NAND flash controller on the Nomadik, with ECC.
546 config MTD_NAND_SH_FLCTL
547 tristate "Support for NAND on Renesas SuperH FLCTL"
548 depends on SUPERH || ARCH_SHMOBILE
550 Several Renesas SuperH CPU has FLCTL. This option enables support
551 for NAND Flash using FLCTL.
553 config MTD_NAND_DAVINCI
554 tristate "Support NAND on DaVinci SoC"
555 depends on ARCH_DAVINCI
557 Enable the driver for NAND flash chips on Texas Instruments
560 config MTD_NAND_TXX9NDFMC
561 tristate "NAND Flash support for TXx9 SoC"
562 depends on SOC_TX4938 || SOC_TX4939
564 This enables the NAND flash controller on the TXx9 SoCs.
566 config MTD_NAND_SOCRATES
567 tristate "Support for NAND on Socrates board"
570 Enables support for NAND Flash chips wired onto Socrates board.
572 config MTD_NAND_NUC900
573 tristate "Support for NAND on Nuvoton NUC9xx/w90p910 evaluation boards."
574 depends on ARCH_W90X900
576 This enables the driver for the NAND Flash on evaluation board based
579 config MTD_NAND_JZ4740
580 tristate "Support for JZ4740 SoC NAND controller"
581 depends on MACH_JZ4740
583 Enables support for NAND Flash on JZ4740 SoC based boards.
586 tristate "Support for NAND on ST Micros FSMC"
587 depends on PLAT_SPEAR || PLAT_NOMADIK || MACH_U300
589 Enables support for NAND Flash chips on the ST Microelectronics
590 Flexible Static Memory Controller (FSMC)