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
121 config MTD_NAND_RICOH
122 tristate "Ricoh xD card reader"
127 Enable support for Ricoh R5C852 xD card reader
128 You also need to enable ether
129 NAND SSFDC (SmartMedia) read only translation layer' or new
130 expermental, readwrite
131 'SmartMedia/xD new translation layer'
133 config MTD_NAND_AU1550
134 tristate "Au1550/1200 NAND support"
135 depends on MIPS_ALCHEMY
137 This enables the driver for the NAND flash controller on the
138 AMD/Alchemy 1550 SOC.
140 config MTD_NAND_BF5XX
141 tristate "Blackfin on-chip NAND Flash Controller driver"
142 depends on BF54x || BF52x
144 This enables the Blackfin on-chip NAND flash controller
146 No board specific support is done by this driver, each board
147 must advertise a platform_device for the driver to attach.
149 This driver can also be built as a module. If so, the module
150 will be called bf5xx-nand.
152 config MTD_NAND_BF5XX_HWECC
153 bool "BF5XX NAND Hardware ECC"
155 depends on MTD_NAND_BF5XX
157 Enable the use of the BF5XX's internal ECC generator when
160 config MTD_NAND_BF5XX_BOOTROM_ECC
161 bool "Use Blackfin BootROM ECC Layout"
163 depends on MTD_NAND_BF5XX_HWECC
165 If you wish to modify NAND pages and allow the Blackfin on-chip
166 BootROM to boot from them, say Y here. This is only necessary
167 if you are booting U-Boot out of NAND and you wish to update
168 U-Boot from Linux' userspace. Otherwise, you should say N here.
172 config MTD_NAND_RTC_FROM4
173 tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
174 depends on SH_SOLUTION_ENGINE
176 select REED_SOLOMON_DEC8
179 This enables the driver for the Renesas Technology AG-AND
180 flash interface board (FROM_BOARD4)
182 config MTD_NAND_PPCHAMELEONEVB
183 tristate "NAND Flash device on PPChameleonEVB board"
184 depends on PPCHAMELEONEVB && BROKEN
186 This enables the NAND flash driver on the PPChameleon EVB Board.
188 config MTD_NAND_S3C2410
189 tristate "NAND Flash support for Samsung S3C SoCs"
190 depends on ARCH_S3C24XX || ARCH_S3C64XX
192 This enables the NAND flash controller on the S3C24xx and S3C64xx
195 No board specific support is done by this driver, each board
196 must advertise a platform_device for the driver to attach.
198 config MTD_NAND_S3C2410_DEBUG
199 bool "Samsung S3C NAND driver debug"
200 depends on MTD_NAND_S3C2410
202 Enable debugging of the S3C NAND driver
204 config MTD_NAND_S3C2410_HWECC
205 bool "Samsung S3C NAND Hardware ECC"
206 depends on MTD_NAND_S3C2410
208 Enable the use of the controller's internal ECC generator when
209 using NAND. Early versions of the chips have had problems with
210 incorrect ECC generation, and if using these, the default of
211 software ECC is preferable.
214 tristate "NDFC NanD Flash Controller"
216 select MTD_NAND_ECC_SMC
218 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
220 config MTD_NAND_S3C2410_CLKSTOP
221 bool "Samsung S3C NAND IDLE clock stop"
222 depends on MTD_NAND_S3C2410
225 Stop the clock to the NAND controller when there is no chip
226 selected to save power. This will mean there is a small delay
227 when the is NAND chip selected or released, but will save
228 approximately 5mA of power when there is nothing happening.
230 config MTD_NAND_BCM_UMI
231 tristate "NAND Flash support for BCM Reference Boards"
232 depends on ARCH_BCMRING
234 This enables the NAND flash controller on the BCM UMI block.
236 No board specific support is done by this driver, each board
237 must advertise a platform_device for the driver to attach.
239 config MTD_NAND_BCM_UMI_HWCS
240 bool "BCM UMI NAND Hardware CS"
241 depends on MTD_NAND_BCM_UMI
243 Enable the use of the BCM UMI block's internal CS using NAND.
244 This should only be used if you know the external NAND CS can toggle.
246 config MTD_NAND_DISKONCHIP
247 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
248 depends on EXPERIMENTAL
251 select REED_SOLOMON_DEC16
253 This is a reimplementation of M-Systems DiskOnChip 2000,
254 Millennium and Millennium Plus as a standard NAND device driver,
255 as opposed to the earlier self-contained MTD device drivers.
256 This should enable, among other things, proper JFFS2 operation on
259 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
260 bool "Advanced detection options for DiskOnChip"
261 depends on MTD_NAND_DISKONCHIP
263 This option allows you to specify nonstandard address at which to
264 probe for a DiskOnChip, or to change the detection options. You
265 are unlikely to need any of this unless you are using LinuxBIOS.
268 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
269 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
270 depends on MTD_NAND_DISKONCHIP
273 By default, the probe for DiskOnChip devices will look for a
274 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
275 This option allows you to specify a single address at which to probe
276 for the device, which is useful if you have other devices in that
277 range which get upset when they are probed.
279 (Note that on PowerPC, the normal probe will only check at
282 Normally, you should leave this set to zero, to allow the probe at
283 the normal addresses.
285 config MTD_NAND_DISKONCHIP_PROBE_HIGH
286 bool "Probe high addresses"
287 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
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 changes to make it probe between 0xFFFC8000 and
292 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
293 useful to you. Say 'N'.
295 config MTD_NAND_DISKONCHIP_BBTWRITE
296 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
297 depends on MTD_NAND_DISKONCHIP
299 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
300 and 2000 TSOP/Alon), Linux reserves some space at the end of the
301 device for the Bad Block Table (BBT). If you have existing INFTL
302 data on your device (created by non-Linux tools such as M-Systems'
303 DOS drivers), your data might overlap the area Linux wants to use for
304 the BBT. If this is a concern for you, leave this option disabled and
305 Linux will not write BBT data into this area.
306 The downside of leaving this option disabled is that if bad blocks
307 are detected by Linux, they will not be recorded in the BBT, which
308 could cause future problems.
309 Once you enable this option, new filesystems (INFTL or others, created
310 in Linux or other operating systems) will not use the reserved area.
311 The only reason not to enable this option is to prevent damage to
312 preexisting filesystems.
313 Even if you leave this disabled, you can enable BBT writes at module
314 load time (assuming you build diskonchip as a module) with the module
315 parameter "inftl_bbt_write=1".
317 config MTD_NAND_SHARPSL
318 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
322 tristate "NAND support for OLPC CAFÉ chip"
325 select REED_SOLOMON_DEC16
327 Use NAND flash attached to the CAFÉ chip designed for the OLPC
330 config MTD_NAND_CS553X
331 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
334 The CS553x companion chips for the AMD Geode processor
335 include NAND flash controllers with built-in hardware ECC
336 capabilities; enabling this option will allow you to use
337 these. The driver will check the MSRs to verify that the
338 controller is enabled for NAND, and currently requires that
339 the controller be in MMIO mode.
341 If you say "m", the module will be called cs553x_nand.
343 config MTD_NAND_ATMEL
344 tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
345 depends on ARCH_AT91 || AVR32
347 Enables support for NAND Flash / Smart Media Card interface
348 on Atmel AT91 and AVR32 processors.
350 prompt "ECC management for NAND Flash / SmartMedia on AT91 / AVR32"
351 depends on MTD_NAND_ATMEL
353 config MTD_NAND_ATMEL_ECC_HW
355 depends on ARCH_AT91SAM9263 || ARCH_AT91SAM9260 || AVR32
357 Use hardware ECC instead of software ECC when the chip
360 The hardware ECC controller is capable of single bit error
361 correction and 2-bit random detection per page.
363 NB : hardware and software ECC schemes are incompatible.
364 If you switch from one to another, you'll have to erase your
369 config MTD_NAND_ATMEL_ECC_SOFT
374 NB : hardware and software ECC schemes are incompatible.
375 If you switch from one to another, you'll have to erase your
378 config MTD_NAND_ATMEL_ECC_NONE
379 bool "No ECC (testing only, DANGEROUS)"
380 depends on DEBUG_KERNEL
383 It's not a good idea and it should be reserved for testing
390 config MTD_NAND_PXA3xx
391 tristate "Support for NAND flash devices on PXA3xx"
392 depends on PXA3xx || ARCH_MMP
394 This enables the driver for the NAND flash device found on
397 config MTD_NAND_CM_X270
398 tristate "Support for NAND Flash on CM-X270 modules"
399 depends on MACH_ARMCORE
401 config MTD_NAND_PASEMI
402 tristate "NAND support for PA Semi PWRficient"
403 depends on PPC_PASEMI
405 Enables support for NAND Flash interface on PA Semi PWRficient
409 tristate "NAND Flash device on Toshiba Mobile IO Controller"
412 Support for NAND flash connected to a Toshiba Mobile IO
413 Controller in some PDAs, including the Sharp SL6000x.
415 config MTD_NAND_NANDSIM
416 tristate "Support for NAND Flash Simulator"
418 The simulator may simulate various NAND flash chips for the
421 config MTD_NAND_GPMI_NAND
422 bool "GPMI NAND Flash Controller driver"
423 depends on MTD_NAND && (SOC_IMX23 || SOC_IMX28)
424 select MTD_CMDLINE_PARTS
426 Enables NAND Flash support for IMX23 or IMX28.
427 The GPMI controller is very powerful, with the help of BCH
428 module, it can do the hardware ECC. The GPMI supports several
429 NAND flashs at the same time. The GPMI may conflicts with other
430 block, such as SD card. So pay attention to it when you enable
433 config MTD_NAND_PLATFORM
434 tristate "Support for generic platform NAND driver"
437 This implements a generic NAND driver for on-SOC platform
438 devices. You will need to provide platform-specific functions
442 tristate "MTD driver for Olympus MAUSB-10 and Fujifilm DPC-R1"
445 These two (and possibly other) Alauda-based cardreaders for
446 SmartMedia and xD allow raw flash access.
448 config MTD_NAND_ORION
449 tristate "NAND Flash support for Marvell Orion SoC"
450 depends on PLAT_ORION
452 This enables the NAND flash controller on Orion machines.
454 No board specific support is done by this driver, each board
455 must advertise a platform_device for the driver to attach.
457 config MTD_NAND_FSL_ELBC
458 tristate "NAND support for Freescale eLBC controllers"
462 Various Freescale chips, including the 8313, include a NAND Flash
463 Controller Module with built-in hardware ECC capabilities.
464 Enabling this option will enable you to use this to control
465 external NAND devices.
467 config MTD_NAND_FSL_IFC
468 tristate "NAND support for Freescale IFC controller"
469 depends on MTD_NAND && FSL_SOC
472 Various Freescale chips e.g P1010, include a NAND Flash machine
473 with built-in hardware ECC capabilities.
474 Enabling this option will enable you to use this to control
475 external NAND devices.
477 config MTD_NAND_FSL_UPM
478 tristate "Support for NAND on Freescale UPM"
479 depends on PPC_83xx || PPC_85xx
482 Enables support for NAND Flash chips wired onto Freescale PowerPC
483 processor localbus with User-Programmable Machine support.
485 config MTD_NAND_MPC5121_NFC
486 tristate "MPC5121 built-in NAND Flash Controller support"
487 depends on PPC_MPC512x
489 This enables the driver for the NAND flash controller on the
493 tristate "MXC NAND support"
494 depends on IMX_HAVE_PLATFORM_MXC_NAND
496 This enables the driver for the NAND flash controller on the
499 config MTD_NAND_NOMADIK
500 tristate "ST Nomadik 8815 NAND support"
501 depends on ARCH_NOMADIK
503 Driver for the NAND flash controller on the Nomadik, with ECC.
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 || PLAT_NOMADIK || MACH_U300
548 Enables support for NAND Flash chips on the ST Microelectronics
549 Flexible Static Memory Controller (FSMC)