blob: da181ee9fd3d0331ec2227af769df23901eee063 [file] [log] [blame]
yuezonghe824eb0c2024-06-27 02:32:26 -07001config MTD_NAND_IDS
2 tristate "Include chip ids for known NAND devices."
3 depends on MTD
4 help
5 Useful for NAND drivers that do not use the NAND subsystem but
6 still like to take advantage of the known chip information.
7
8config MTD_NAND_ECC
9 tristate
10
11config MTD_NAND_ECC_SMC
12 bool "NAND ECC Smart Media byte order"
13 depends on MTD_NAND_ECC
14 default n
15 help
16 Software ECC according to the Smart Media Specification.
17 The original Linux implementation had byte 0 and 1 swapped.
18
19
20menuconfig MTD_NAND
21 tristate "NAND Device Support"
22 depends on MTD
23 select MTD_NAND_IDS
24 select MTD_NAND_ECC
25 help
26 This enables support for accessing all type of NAND flash
27 devices. For further information see
28 <http://www.linux-mtd.infradead.org/doc/nand.html>.
29
30if MTD_NAND
31
32config MTD_NAND_VERIFY_WRITE
33 bool "Verify NAND page writes"
34 help
35 This adds an extra check when data is written to the flash. The
36 NAND flash device internally checks only bits transitioning
37 from 1 to 0. There is a rare possibility that even though the
38 device thinks the write was successful, a bit could have been
39 flipped accidentally due to device wear or something else.
40
41config MTD_NAND_BCH
42 tristate
43 select BCH
44 depends on MTD_NAND_ECC_BCH
45 default MTD_NAND
46
47config MTD_NAND_ECC_BCH
48 bool "Support software BCH ECC"
49 default n
50 help
51 This enables support for software BCH error correction. Binary BCH
52 codes are more powerful and cpu intensive than traditional Hamming
53 ECC codes. They are used with NAND devices requiring more than 1 bit
54 of error correction.
55
56config MTD_SM_COMMON
57 tristate
58 default n
59
60config MTD_NAND_MUSEUM_IDS
61 bool "Enable chip ids for obsolete ancient NAND devices"
62 default n
63 help
64 Enable this option only when your board has first generation
65 NAND chips (page size 256 byte, erase size 4-8KiB). The IDs
66 of these chips were reused by later, larger chips.
67
68config MTD_NAND_AUTCPU12
69 tristate "SmartMediaCard on autronix autcpu12 board"
70 depends on ARCH_AUTCPU12
71 help
72 This enables the driver for the autronix autcpu12 board to
73 access the SmartMediaCard.
74
75config MTD_NAND_DENALI
76 tristate "Support Denali NAND controller on Intel Moorestown"
77 help
78 Enable the driver for NAND flash on Intel Moorestown, using the
79 Denali NAND controller core.
80
81config MTD_ZXIC_SPIFC
82 tristate "Support SPI NAND controller"
83 help
84 Enable the driver for SPI NAND flash on Intel Moorestown, using the
85 SPI NAND controller core.
86config NAND_INTERFACE_LINUX
87 tristate "Support NAND_INTERFACE_LINUX"
88 help
89 Enable the driver for NAND INTERFACE
90
91config MTD_NAND_DENALI_SCRATCH_REG_ADDR
92 hex "Denali NAND size scratch register address"
93 default "0xFF108018"
94 depends on MTD_NAND_DENALI
95 help
96 Some platforms place the NAND chip size in a scratch register
97 because (some versions of) the driver aren't able to automatically
98 determine the size of certain chips. Set the address of the
99 scratch register here to enable this feature. On Intel Moorestown
100 boards, the scratch register is at 0xFF108018.
101
102config MTD_NAND_H1900
103 tristate "iPAQ H1900 flash"
104 depends on ARCH_PXA && BROKEN
105 help
106 This enables the driver for the iPAQ h1900 flash.
107
108config MTD_NAND_GPIO
109 tristate "GPIO NAND Flash driver"
110 depends on GENERIC_GPIO && ARM
111 help
112 This enables a GPIO based NAND flash driver.
113
114config MTD_NAND_SPIA
115 tristate "NAND Flash device on SPIA board"
116 depends on ARCH_P720T
117 help
118 If you had to ask, you don't have one. Say 'N'.
119
120config MTD_NAND_AMS_DELTA
121 tristate "NAND Flash device on Amstrad E3"
122 depends on MACH_AMS_DELTA
123 default y
124 help
125 Support for NAND flash on Amstrad E3 (Delta).
126
127config MTD_NAND_OMAP2
128 tristate "NAND Flash device on OMAP2, OMAP3 and OMAP4"
129 depends on ARCH_OMAP2PLUS
130 help
131 Support for NAND flash on Texas Instruments OMAP2, OMAP3 and OMAP4
132 platforms.
133
134config MTD_NAND_RICOH
135 tristate "Ricoh xD card reader"
136 default n
137 depends on PCI
138 select MTD_SM_COMMON
139 help
140 Enable support for Ricoh R5C852 xD card reader
141 You also need to enable ether
142 NAND SSFDC (SmartMedia) read only translation layer' or new
143 expermental, readwrite
144 'SmartMedia/xD new translation layer'
145
146config MTD_NAND_AU1550
147 tristate "Au1550/1200 NAND support"
148 depends on MIPS_ALCHEMY
149 help
150 This enables the driver for the NAND flash controller on the
151 AMD/Alchemy 1550 SOC.
152
153config MTD_NAND_BF5XX
154 tristate "Blackfin on-chip NAND Flash Controller driver"
155 depends on BF54x || BF52x
156 help
157 This enables the Blackfin on-chip NAND flash controller
158
159 No board specific support is done by this driver, each board
160 must advertise a platform_device for the driver to attach.
161
162 This driver can also be built as a module. If so, the module
163 will be called bf5xx-nand.
164
165config MTD_NAND_BF5XX_HWECC
166 bool "BF5XX NAND Hardware ECC"
167 default y
168 depends on MTD_NAND_BF5XX
169 help
170 Enable the use of the BF5XX's internal ECC generator when
171 using NAND.
172
173config MTD_NAND_BF5XX_BOOTROM_ECC
174 bool "Use Blackfin BootROM ECC Layout"
175 default n
176 depends on MTD_NAND_BF5XX_HWECC
177 help
178 If you wish to modify NAND pages and allow the Blackfin on-chip
179 BootROM to boot from them, say Y here. This is only necessary
180 if you are booting U-Boot out of NAND and you wish to update
181 U-Boot from Linux' userspace. Otherwise, you should say N here.
182
183 If unsure, say N.
184
185config MTD_NAND_RTC_FROM4
186 tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
187 depends on SH_SOLUTION_ENGINE
188 select REED_SOLOMON
189 select REED_SOLOMON_DEC8
190 select BITREVERSE
191 help
192 This enables the driver for the Renesas Technology AG-AND
193 flash interface board (FROM_BOARD4)
194
195config MTD_NAND_PPCHAMELEONEVB
196 tristate "NAND Flash device on PPChameleonEVB board"
197 depends on PPCHAMELEONEVB && BROKEN
198 help
199 This enables the NAND flash driver on the PPChameleon EVB Board.
200
201config MTD_NAND_S3C2410
202 tristate "NAND Flash support for Samsung S3C SoCs"
203 depends on ARCH_S3C24XX || ARCH_S3C64XX
204 help
205 This enables the NAND flash controller on the S3C24xx and S3C64xx
206 SoCs
207
208 No board specific support is done by this driver, each board
209 must advertise a platform_device for the driver to attach.
210
211config MTD_NAND_S3C2410_DEBUG
212 bool "Samsung S3C NAND driver debug"
213 depends on MTD_NAND_S3C2410
214 help
215 Enable debugging of the S3C NAND driver
216
217config MTD_NAND_S3C2410_HWECC
218 bool "Samsung S3C NAND Hardware ECC"
219 depends on MTD_NAND_S3C2410
220 help
221 Enable the use of the controller's internal ECC generator when
222 using NAND. Early versions of the chips have had problems with
223 incorrect ECC generation, and if using these, the default of
224 software ECC is preferable.
225
226config MTD_NAND_NDFC
227 tristate "NDFC NanD Flash Controller"
228 depends on 4xx
229 select MTD_NAND_ECC_SMC
230 help
231 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
232
233config MTD_NAND_S3C2410_CLKSTOP
234 bool "Samsung S3C NAND IDLE clock stop"
235 depends on MTD_NAND_S3C2410
236 default n
237 help
238 Stop the clock to the NAND controller when there is no chip
239 selected to save power. This will mean there is a small delay
240 when the is NAND chip selected or released, but will save
241 approximately 5mA of power when there is nothing happening.
242
243config MTD_NAND_BCM_UMI
244 tristate "NAND Flash support for BCM Reference Boards"
245 depends on ARCH_BCMRING
246 help
247 This enables the NAND flash controller on the BCM UMI block.
248
249 No board specific support is done by this driver, each board
250 must advertise a platform_device for the driver to attach.
251
252config MTD_NAND_BCM_UMI_HWCS
253 bool "BCM UMI NAND Hardware CS"
254 depends on MTD_NAND_BCM_UMI
255 help
256 Enable the use of the BCM UMI block's internal CS using NAND.
257 This should only be used if you know the external NAND CS can toggle.
258
259config MTD_NAND_DISKONCHIP
260 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
261 depends on EXPERIMENTAL
262 depends on HAS_IOMEM
263 select REED_SOLOMON
264 select REED_SOLOMON_DEC16
265 help
266 This is a reimplementation of M-Systems DiskOnChip 2000,
267 Millennium and Millennium Plus as a standard NAND device driver,
268 as opposed to the earlier self-contained MTD device drivers.
269 This should enable, among other things, proper JFFS2 operation on
270 these devices.
271
272config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
273 bool "Advanced detection options for DiskOnChip"
274 depends on MTD_NAND_DISKONCHIP
275 help
276 This option allows you to specify nonstandard address at which to
277 probe for a DiskOnChip, or to change the detection options. You
278 are unlikely to need any of this unless you are using LinuxBIOS.
279 Say 'N'.
280
281config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
282 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
283 depends on MTD_NAND_DISKONCHIP
284 default "0"
285 ---help---
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 allows you to specify a single address at which to probe
289 for the device, which is useful if you have other devices in that
290 range which get upset when they are probed.
291
292 (Note that on PowerPC, the normal probe will only check at
293 0xE4000000.)
294
295 Normally, you should leave this set to zero, to allow the probe at
296 the normal addresses.
297
298config MTD_NAND_DISKONCHIP_PROBE_HIGH
299 bool "Probe high addresses"
300 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
301 help
302 By default, the probe for DiskOnChip devices will look for a
303 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
304 This option changes to make it probe between 0xFFFC8000 and
305 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
306 useful to you. Say 'N'.
307
308config MTD_NAND_DISKONCHIP_BBTWRITE
309 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
310 depends on MTD_NAND_DISKONCHIP
311 help
312 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
313 and 2000 TSOP/Alon), Linux reserves some space at the end of the
314 device for the Bad Block Table (BBT). If you have existing INFTL
315 data on your device (created by non-Linux tools such as M-Systems'
316 DOS drivers), your data might overlap the area Linux wants to use for
317 the BBT. If this is a concern for you, leave this option disabled and
318 Linux will not write BBT data into this area.
319 The downside of leaving this option disabled is that if bad blocks
320 are detected by Linux, they will not be recorded in the BBT, which
321 could cause future problems.
322 Once you enable this option, new filesystems (INFTL or others, created
323 in Linux or other operating systems) will not use the reserved area.
324 The only reason not to enable this option is to prevent damage to
325 preexisting filesystems.
326 Even if you leave this disabled, you can enable BBT writes at module
327 load time (assuming you build diskonchip as a module) with the module
328 parameter "inftl_bbt_write=1".
329
330config MTD_NAND_DOCG4
331 tristate "Support for DiskOnChip G4 (EXPERIMENTAL)"
332 depends on EXPERIMENTAL
333 select BCH
334 select BITREVERSE
335 help
336 Support for diskonchip G4 nand flash, found in various smartphones and
337 PDAs, among them the Palm Treo680, HTC Prophet and Wizard, Toshiba
338 Portege G900, Asus P526, and O2 XDA Zinc.
339
340 With this driver you will be able to use UBI and create a ubifs on the
341 device, so you may wish to consider enabling UBI and UBIFS as well.
342
343 These devices ship with the Mys/Sandisk SAFTL formatting, for which
344 there is currently no mtd parser, so you may want to use command line
345 partitioning to segregate write-protected blocks. On the Treo680, the
346 first five erase blocks (256KiB each) are write-protected, followed
347 by the block containing the saftl partition table. This is probably
348 typical.
349
350config MTD_NAND_SHARPSL
351 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
352 depends on ARCH_PXA
353
354config MTD_NAND_CAFE
355 tristate "NAND support for OLPC CAFÉ chip"
356 depends on PCI
357 select REED_SOLOMON
358 select REED_SOLOMON_DEC16
359 help
360 Use NAND flash attached to the CAFÉ chip designed for the OLPC
361 laptop.
362
363config MTD_NAND_CS553X
364 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
365 depends on X86_32
366 help
367 The CS553x companion chips for the AMD Geode processor
368 include NAND flash controllers with built-in hardware ECC
369 capabilities; enabling this option will allow you to use
370 these. The driver will check the MSRs to verify that the
371 controller is enabled for NAND, and currently requires that
372 the controller be in MMIO mode.
373
374 If you say "m", the module will be called cs553x_nand.
375
376config MTD_NAND_ATMEL
377 tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
378 depends on ARCH_AT91 || AVR32
379 help
380 Enables support for NAND Flash / Smart Media Card interface
381 on Atmel AT91 and AVR32 processors.
382choice
383 prompt "ECC management for NAND Flash / SmartMedia on AT91 / AVR32"
384 depends on MTD_NAND_ATMEL
385
386config MTD_NAND_ATMEL_ECC_HW
387 bool "Hardware ECC"
388 depends on ARCH_AT91SAM9263 || ARCH_AT91SAM9260 || AVR32
389 help
390 Use hardware ECC instead of software ECC when the chip
391 supports it.
392
393 The hardware ECC controller is capable of single bit error
394 correction and 2-bit random detection per page.
395
396 NB : hardware and software ECC schemes are incompatible.
397 If you switch from one to another, you'll have to erase your
398 mtd partition.
399
400 If unsure, say Y
401
402config MTD_NAND_ATMEL_ECC_SOFT
403 bool "Software ECC"
404 help
405 Use software ECC.
406
407 NB : hardware and software ECC schemes are incompatible.
408 If you switch from one to another, you'll have to erase your
409 mtd partition.
410
411config MTD_NAND_ATMEL_ECC_NONE
412 bool "No ECC (testing only, DANGEROUS)"
413 depends on DEBUG_KERNEL
414 help
415 No ECC will be used.
416 It's not a good idea and it should be reserved for testing
417 purpose only.
418
419 If unsure, say N
420
421endchoice
422
423config MTD_NAND_PXA3xx
424 tristate "Support for NAND flash devices on PXA3xx"
425 depends on PXA3xx || ARCH_MMP
426 help
427 This enables the driver for the NAND flash device found on
428 PXA3xx processors
429
430config MTD_NAND_CM_X270
431 tristate "Support for NAND Flash on CM-X270 modules"
432 depends on MACH_ARMCORE
433
434config MTD_NAND_PASEMI
435 tristate "NAND support for PA Semi PWRficient"
436 depends on PPC_PASEMI
437 help
438 Enables support for NAND Flash interface on PA Semi PWRficient
439 based boards
440
441config MTD_NAND_TMIO
442 tristate "NAND Flash device on Toshiba Mobile IO Controller"
443 depends on MFD_TMIO
444 help
445 Support for NAND flash connected to a Toshiba Mobile IO
446 Controller in some PDAs, including the Sharp SL6000x.
447
448config MTD_NAND_NANDSIM
449 tristate "Support for NAND Flash Simulator"
450 help
451 The simulator may simulate various NAND flash chips for the
452 MTD nand layer.
453
454config MTD_NAND_GPMI_NAND
455 bool "GPMI NAND Flash Controller driver"
456 depends on MTD_NAND && (SOC_IMX23 || SOC_IMX28)
457 help
458 Enables NAND Flash support for IMX23 or IMX28.
459 The GPMI controller is very powerful, with the help of BCH
460 module, it can do the hardware ECC. The GPMI supports several
461 NAND flashs at the same time. The GPMI may conflicts with other
462 block, such as SD card. So pay attention to it when you enable
463 the GPMI.
464
465config MTD_NAND_PLATFORM
466 tristate "Support for generic platform NAND driver"
467 depends on HAS_IOMEM
468 help
469 This implements a generic NAND driver for on-SOC platform
470 devices. You will need to provide platform-specific functions
471 via platform_data.
472
473config MTD_ALAUDA
474 tristate "MTD driver for Olympus MAUSB-10 and Fujifilm DPC-R1"
475 depends on USB
476 help
477 These two (and possibly other) Alauda-based cardreaders for
478 SmartMedia and xD allow raw flash access.
479
480config MTD_NAND_ORION
481 tristate "NAND Flash support for Marvell Orion SoC"
482 depends on PLAT_ORION
483 help
484 This enables the NAND flash controller on Orion machines.
485
486 No board specific support is done by this driver, each board
487 must advertise a platform_device for the driver to attach.
488
489config MTD_NAND_FSL_ELBC
490 tristate "NAND support for Freescale eLBC controllers"
491 depends on PPC_OF
492 select FSL_LBC
493 help
494 Various Freescale chips, including the 8313, include a NAND Flash
495 Controller Module with built-in hardware ECC capabilities.
496 Enabling this option will enable you to use this to control
497 external NAND devices.
498
499config MTD_NAND_FSL_IFC
500 tristate "NAND support for Freescale IFC controller"
501 depends on MTD_NAND && FSL_SOC
502 select FSL_IFC
503 help
504 Various Freescale chips e.g P1010, include a NAND Flash machine
505 with built-in hardware ECC capabilities.
506 Enabling this option will enable you to use this to control
507 external NAND devices.
508
509config MTD_NAND_FSL_UPM
510 tristate "Support for NAND on Freescale UPM"
511 depends on PPC_83xx || PPC_85xx
512 select FSL_LBC
513 help
514 Enables support for NAND Flash chips wired onto Freescale PowerPC
515 processor localbus with User-Programmable Machine support.
516
517config MTD_NAND_MPC5121_NFC
518 tristate "MPC5121 built-in NAND Flash Controller support"
519 depends on PPC_MPC512x
520 help
521 This enables the driver for the NAND flash controller on the
522 MPC5121 SoC.
523
524config MTD_NAND_MXC
525 tristate "MXC NAND support"
526 depends on IMX_HAVE_PLATFORM_MXC_NAND
527 help
528 This enables the driver for the NAND flash controller on the
529 MXC processors.
530
531config MTD_NAND_NOMADIK
532 tristate "ST Nomadik 8815 NAND support"
533 depends on ARCH_NOMADIK
534 help
535 Driver for the NAND flash controller on the Nomadik, with ECC.
536
537config MTD_NAND_SH_FLCTL
538 tristate "Support for NAND on Renesas SuperH FLCTL"
539 depends on SUPERH || ARCH_SHMOBILE
540 help
541 Several Renesas SuperH CPU has FLCTL. This option enables support
542 for NAND Flash using FLCTL.
543
544config MTD_NAND_DAVINCI
545 tristate "Support NAND on DaVinci SoC"
546 depends on ARCH_DAVINCI
547 help
548 Enable the driver for NAND flash chips on Texas Instruments
549 DaVinci processors.
550
551config MTD_NAND_TXX9NDFMC
552 tristate "NAND Flash support for TXx9 SoC"
553 depends on SOC_TX4938 || SOC_TX4939
554 help
555 This enables the NAND flash controller on the TXx9 SoCs.
556
557config MTD_NAND_SOCRATES
558 tristate "Support for NAND on Socrates board"
559 depends on SOCRATES
560 help
561 Enables support for NAND Flash chips wired onto Socrates board.
562
563config MTD_NAND_NUC900
564 tristate "Support for NAND on Nuvoton NUC9xx/w90p910 evaluation boards."
565 depends on ARCH_W90X900
566 help
567 This enables the driver for the NAND Flash on evaluation board based
568 on w90p910 / NUC9xx.
569
570config MTD_NAND_JZ4740
571 tristate "Support for JZ4740 SoC NAND controller"
572 depends on MACH_JZ4740
573 help
574 Enables support for NAND Flash on JZ4740 SoC based boards.
575
576config MTD_NAND_FSMC
577 tristate "Support for NAND on ST Micros FSMC"
578 depends on PLAT_SPEAR || PLAT_NOMADIK || MACH_U300
579 help
580 Enables support for NAND Flash chips on the ST Microelectronics
581 Flexible Static Memory Controller (FSMC)
582
583endif # MTD_NAND