Version:  2.0.40 2.2.26 2.4.37 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8

Linux/drivers/mtd/nand/Kconfig

  1 config MTD_NAND_ECC
  2         tristate
  3 
  4 config MTD_NAND_ECC_SMC
  5         bool "NAND ECC Smart Media byte order"
  6         depends on MTD_NAND_ECC
  7         default n
  8         help
  9           Software ECC according to the Smart Media Specification.
 10           The original Linux implementation had byte 0 and 1 swapped.
 11 
 12 
 13 menuconfig MTD_NAND
 14         tristate "NAND Device Support"
 15         depends on MTD
 16         select MTD_NAND_IDS
 17         select MTD_NAND_ECC
 18         help
 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>.
 22 
 23 if MTD_NAND
 24 
 25 config MTD_NAND_BCH
 26         tristate
 27         select BCH
 28         depends on MTD_NAND_ECC_BCH
 29         default MTD_NAND
 30 
 31 config MTD_NAND_ECC_BCH
 32         bool "Support software BCH ECC"
 33         default n
 34         help
 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
 38           of error correction.
 39 
 40 config MTD_SM_COMMON
 41         tristate
 42         default n
 43 
 44 config MTD_NAND_DENALI
 45         tristate
 46 
 47 config MTD_NAND_DENALI_PCI
 48         tristate "Support Denali NAND controller on Intel Moorestown"
 49         select MTD_NAND_DENALI
 50         depends on HAS_DMA && PCI
 51         help
 52           Enable the driver for NAND flash on Intel Moorestown, using the
 53           Denali NAND controller core.
 54 
 55 config MTD_NAND_DENALI_DT
 56         tristate "Support Denali NAND controller as a DT device"
 57         select MTD_NAND_DENALI
 58         depends on HAS_DMA && HAVE_CLK && OF
 59         help
 60           Enable the driver for NAND flash on platforms using a Denali NAND
 61           controller as a DT device.
 62 
 63 config MTD_NAND_DENALI_SCRATCH_REG_ADDR
 64         hex "Denali NAND size scratch register address"
 65         default "0xFF108018"
 66         depends on MTD_NAND_DENALI_PCI
 67         help
 68           Some platforms place the NAND chip size in a scratch register
 69           because (some versions of) the driver aren't able to automatically
 70           determine the size of certain chips. Set the address of the
 71           scratch register here to enable this feature. On Intel Moorestown
 72           boards, the scratch register is at 0xFF108018.
 73 
 74 config MTD_NAND_GPIO
 75         tristate "GPIO assisted NAND Flash driver"
 76         depends on GPIOLIB || COMPILE_TEST
 77         depends on HAS_IOMEM
 78         help
 79           This enables a NAND flash driver where control signals are
 80           connected to GPIO pins, and commands and data are communicated
 81           via a memory mapped interface.
 82 
 83 config MTD_NAND_AMS_DELTA
 84         tristate "NAND Flash device on Amstrad E3"
 85         depends on MACH_AMS_DELTA
 86         default y
 87         help
 88           Support for NAND flash on Amstrad E3 (Delta).
 89 
 90 config MTD_NAND_OMAP2
 91         tristate "NAND Flash device on OMAP2, OMAP3 and OMAP4"
 92         depends on ARCH_OMAP2PLUS
 93         help
 94           Support for NAND flash on Texas Instruments OMAP2, OMAP3 and OMAP4
 95           platforms.
 96 
 97 config MTD_NAND_OMAP_BCH
 98         depends on MTD_NAND_OMAP2
 99         bool "Support hardware based BCH error correction"
100         default n
101         select BCH
102         help
103           This config enables the ELM hardware engine, which can be used to
104           locate and correct errors when using BCH ECC scheme. This offloads
105           the cpu from doing ECC error searching and correction. However some
106           legacy OMAP families like OMAP2xxx, OMAP3xxx do not have ELM engine
107           so this is optional for them.
108 
109 config MTD_NAND_OMAP_BCH_BUILD
110         def_tristate MTD_NAND_OMAP2 && MTD_NAND_OMAP_BCH
111 
112 config MTD_NAND_IDS
113         tristate
114 
115 config MTD_NAND_RICOH
116         tristate "Ricoh xD card reader"
117         default n
118         depends on PCI
119         select MTD_SM_COMMON
120         help
121           Enable support for Ricoh R5C852 xD card reader
122           You also need to enable ether
123           NAND SSFDC (SmartMedia) read only translation layer' or new
124           expermental, readwrite
125           'SmartMedia/xD new translation layer'
126 
127 config MTD_NAND_AU1550
128         tristate "Au1550/1200 NAND support"
129         depends on MIPS_ALCHEMY
130         help
131           This enables the driver for the NAND flash controller on the
132           AMD/Alchemy 1550 SOC.
133 
134 config MTD_NAND_BF5XX
135         tristate "Blackfin on-chip NAND Flash Controller driver"
136         depends on BF54x || BF52x
137         help
138           This enables the Blackfin on-chip NAND flash controller
139 
140           No board specific support is done by this driver, each board
141           must advertise a platform_device for the driver to attach.
142 
143           This driver can also be built as a module. If so, the module
144           will be called bf5xx-nand.
145 
146 config MTD_NAND_BF5XX_HWECC
147         bool "BF5XX NAND Hardware ECC"
148         default y
149         depends on MTD_NAND_BF5XX
150         help
151           Enable the use of the BF5XX's internal ECC generator when
152           using NAND.
153 
154 config MTD_NAND_BF5XX_BOOTROM_ECC
155         bool "Use Blackfin BootROM ECC Layout"
156         default n
157         depends on MTD_NAND_BF5XX_HWECC
158         help
159           If you wish to modify NAND pages and allow the Blackfin on-chip
160           BootROM to boot from them, say Y here.  This is only necessary
161           if you are booting U-Boot out of NAND and you wish to update
162           U-Boot from Linux' userspace.  Otherwise, you should say N here.
163 
164           If unsure, say N.
165 
166 config MTD_NAND_S3C2410
167         tristate "NAND Flash support for Samsung S3C SoCs"
168         depends on ARCH_S3C24XX || ARCH_S3C64XX
169         help
170           This enables the NAND flash controller on the S3C24xx and S3C64xx
171           SoCs
172 
173           No board specific support is done by this driver, each board
174           must advertise a platform_device for the driver to attach.
175 
176 config MTD_NAND_S3C2410_DEBUG
177         bool "Samsung S3C NAND driver debug"
178         depends on MTD_NAND_S3C2410
179         help
180           Enable debugging of the S3C NAND driver
181 
182 config MTD_NAND_S3C2410_HWECC
183         bool "Samsung S3C NAND Hardware ECC"
184         depends on MTD_NAND_S3C2410
185         help
186           Enable the use of the controller's internal ECC generator when
187           using NAND. Early versions of the chips have had problems with
188           incorrect ECC generation, and if using these, the default of
189           software ECC is preferable.
190 
191 config MTD_NAND_NDFC
192         tristate "NDFC NanD Flash Controller"
193         depends on 4xx
194         select MTD_NAND_ECC_SMC
195         help
196          NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
197 
198 config MTD_NAND_S3C2410_CLKSTOP
199         bool "Samsung S3C NAND IDLE clock stop"
200         depends on MTD_NAND_S3C2410
201         default n
202         help
203           Stop the clock to the NAND controller when there is no chip
204           selected to save power. This will mean there is a small delay
205           when the is NAND chip selected or released, but will save
206           approximately 5mA of power when there is nothing happening.
207 
208 config MTD_NAND_DISKONCHIP
209         tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation)"
210         depends on HAS_IOMEM
211         select REED_SOLOMON
212         select REED_SOLOMON_DEC16
213         help
214           This is a reimplementation of M-Systems DiskOnChip 2000,
215           Millennium and Millennium Plus as a standard NAND device driver,
216           as opposed to the earlier self-contained MTD device drivers.
217           This should enable, among other things, proper JFFS2 operation on
218           these devices.
219 
220 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
221         bool "Advanced detection options for DiskOnChip"
222         depends on MTD_NAND_DISKONCHIP
223         help
224           This option allows you to specify nonstandard address at which to
225           probe for a DiskOnChip, or to change the detection options.  You
226           are unlikely to need any of this unless you are using LinuxBIOS.
227           Say 'N'.
228 
229 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
230         hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
231         depends on MTD_NAND_DISKONCHIP
232         default "0"
233         ---help---
234         By default, the probe for DiskOnChip devices will look for a
235         DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
236         This option allows you to specify a single address at which to probe
237         for the device, which is useful if you have other devices in that
238         range which get upset when they are probed.
239 
240         (Note that on PowerPC, the normal probe will only check at
241         0xE4000000.)
242 
243         Normally, you should leave this set to zero, to allow the probe at
244         the normal addresses.
245 
246 config MTD_NAND_DISKONCHIP_PROBE_HIGH
247         bool "Probe high addresses"
248         depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
249         help
250           By default, the probe for DiskOnChip devices will look for a
251           DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
252           This option changes to make it probe between 0xFFFC8000 and
253           0xFFFEE000.  Unless you are using LinuxBIOS, this is unlikely to be
254           useful to you.  Say 'N'.
255 
256 config MTD_NAND_DISKONCHIP_BBTWRITE
257         bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
258         depends on MTD_NAND_DISKONCHIP
259         help
260           On DiskOnChip devices shipped with the INFTL filesystem (Millennium
261           and 2000 TSOP/Alon), Linux reserves some space at the end of the
262           device for the Bad Block Table (BBT).  If you have existing INFTL
263           data on your device (created by non-Linux tools such as M-Systems'
264           DOS drivers), your data might overlap the area Linux wants to use for
265           the BBT.  If this is a concern for you, leave this option disabled and
266           Linux will not write BBT data into this area.
267           The downside of leaving this option disabled is that if bad blocks
268           are detected by Linux, they will not be recorded in the BBT, which
269           could cause future problems.
270           Once you enable this option, new filesystems (INFTL or others, created
271           in Linux or other operating systems) will not use the reserved area.
272           The only reason not to enable this option is to prevent damage to
273           preexisting filesystems.
274           Even if you leave this disabled, you can enable BBT writes at module
275           load time (assuming you build diskonchip as a module) with the module
276           parameter "inftl_bbt_write=1".
277 
278 config MTD_NAND_DOCG4
279         tristate "Support for DiskOnChip G4"
280         depends on HAS_IOMEM
281         select BCH
282         select BITREVERSE
283         help
284           Support for diskonchip G4 nand flash, found in various smartphones and
285           PDAs, among them the Palm Treo680, HTC Prophet and Wizard, Toshiba
286           Portege G900, Asus P526, and O2 XDA Zinc.
287 
288           With this driver you will be able to use UBI and create a ubifs on the
289           device, so you may wish to consider enabling UBI and UBIFS as well.
290 
291           These devices ship with the Mys/Sandisk SAFTL formatting, for which
292           there is currently no mtd parser, so you may want to use command line
293           partitioning to segregate write-protected blocks. On the Treo680, the
294           first five erase blocks (256KiB each) are write-protected, followed
295           by the block containing the saftl partition table.  This is probably
296           typical.
297 
298 config MTD_NAND_SHARPSL
299         tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
300         depends on ARCH_PXA
301 
302 config MTD_NAND_CAFE
303         tristate "NAND support for OLPC CAFÉ chip"
304         depends on PCI
305         select REED_SOLOMON
306         select REED_SOLOMON_DEC16
307         help
308           Use NAND flash attached to the CAFÉ chip designed for the OLPC
309           laptop.
310 
311 config MTD_NAND_CS553X
312         tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
313         depends on X86_32
314         depends on !UML && HAS_IOMEM
315         help
316           The CS553x companion chips for the AMD Geode processor
317           include NAND flash controllers with built-in hardware ECC
318           capabilities; enabling this option will allow you to use
319           these. The driver will check the MSRs to verify that the
320           controller is enabled for NAND, and currently requires that
321           the controller be in MMIO mode.
322 
323           If you say "m", the module will be called cs553x_nand.
324 
325 config MTD_NAND_ATMEL
326         tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
327         depends on ARCH_AT91 || AVR32
328         help
329           Enables support for NAND Flash / Smart Media Card interface
330           on Atmel AT91 and AVR32 processors.
331 
332 config MTD_NAND_PXA3xx
333         tristate "NAND support on PXA3xx and Armada 370/XP"
334         depends on PXA3xx || ARCH_MMP || PLAT_ORION
335         help
336           This enables the driver for the NAND flash device found on
337           PXA3xx processors (NFCv1) and also on Armada 370/XP (NFCv2).
338 
339 config MTD_NAND_SLC_LPC32XX
340         tristate "NXP LPC32xx SLC Controller"
341         depends on ARCH_LPC32XX
342         help
343           Enables support for NXP's LPC32XX SLC (i.e. for Single Level Cell
344           chips) NAND controller. This is the default for the PHYTEC 3250
345           reference board which contains a NAND256R3A2CZA6 chip.
346 
347           Please check the actual NAND chip connected and its support
348           by the SLC NAND controller.
349 
350 config MTD_NAND_MLC_LPC32XX
351         tristate "NXP LPC32xx MLC Controller"
352         depends on ARCH_LPC32XX
353         help
354           Uses the LPC32XX MLC (i.e. for Multi Level Cell chips) NAND
355           controller. This is the default for the WORK92105 controller
356           board.
357 
358           Please check the actual NAND chip connected and its support
359           by the MLC NAND controller.
360 
361 config MTD_NAND_CM_X270
362         tristate "Support for NAND Flash on CM-X270 modules"
363         depends on MACH_ARMCORE
364 
365 config MTD_NAND_PASEMI
366         tristate "NAND support for PA Semi PWRficient"
367         depends on PPC_PASEMI
368         help
369           Enables support for NAND Flash interface on PA Semi PWRficient
370           based boards
371 
372 config MTD_NAND_TMIO
373         tristate "NAND Flash device on Toshiba Mobile IO Controller"
374         depends on MFD_TMIO
375         help
376           Support for NAND flash connected to a Toshiba Mobile IO
377           Controller in some PDAs, including the Sharp SL6000x.
378 
379 config MTD_NAND_NANDSIM
380         tristate "Support for NAND Flash Simulator"
381         help
382           The simulator may simulate various NAND flash chips for the
383           MTD nand layer.
384 
385 config MTD_NAND_GPMI_NAND
386         tristate "GPMI NAND Flash Controller driver"
387         depends on MTD_NAND && MXS_DMA
388         help
389          Enables NAND Flash support for IMX23, IMX28 or IMX6.
390          The GPMI controller is very powerful, with the help of BCH
391          module, it can do the hardware ECC. The GPMI supports several
392          NAND flashs at the same time. The GPMI may conflicts with other
393          block, such as SD card. So pay attention to it when you enable
394          the GPMI.
395 
396 config MTD_NAND_BRCMNAND
397         tristate "Broadcom STB NAND controller"
398         depends on ARM || ARM64 || MIPS
399         help
400           Enables the Broadcom NAND controller driver. The controller was
401           originally designed for Set-Top Box but is used on various BCM7xxx,
402           BCM3xxx, BCM63xxx, iProc/Cygnus and more.
403 
404 config MTD_NAND_BCM47XXNFLASH
405         tristate "Support for NAND flash on BCM4706 BCMA bus"
406         depends on BCMA_NFLASH
407         help
408           BCMA bus can have various flash memories attached, they are
409           registered by bcma as platform devices. This enables driver for
410           NAND flash memories. For now only BCM4706 is supported.
411 
412 config MTD_NAND_PLATFORM
413         tristate "Support for generic platform NAND driver"
414         depends on HAS_IOMEM
415         help
416           This implements a generic NAND driver for on-SOC platform
417           devices. You will need to provide platform-specific functions
418           via platform_data.
419 
420 config MTD_NAND_ORION
421         tristate "NAND Flash support for Marvell Orion SoC"
422         depends on PLAT_ORION
423         help
424           This enables the NAND flash controller on Orion machines.
425 
426           No board specific support is done by this driver, each board
427           must advertise a platform_device for the driver to attach.
428 
429 config MTD_NAND_FSL_ELBC
430         tristate "NAND support for Freescale eLBC controllers"
431         depends on PPC
432         select FSL_LBC
433         help
434           Various Freescale chips, including the 8313, include a NAND Flash
435           Controller Module with built-in hardware ECC capabilities.
436           Enabling this option will enable you to use this to control
437           external NAND devices.
438 
439 config MTD_NAND_FSL_IFC
440         tristate "NAND support for Freescale IFC controller"
441         depends on MTD_NAND && (FSL_SOC || ARCH_LAYERSCAPE)
442         select FSL_IFC
443         select MEMORY
444         help
445           Various Freescale chips e.g P1010, include a NAND Flash machine
446           with built-in hardware ECC capabilities.
447           Enabling this option will enable you to use this to control
448           external NAND devices.
449 
450 config MTD_NAND_FSL_UPM
451         tristate "Support for NAND on Freescale UPM"
452         depends on PPC_83xx || PPC_85xx
453         select FSL_LBC
454         help
455           Enables support for NAND Flash chips wired onto Freescale PowerPC
456           processor localbus with User-Programmable Machine support.
457 
458 config MTD_NAND_MPC5121_NFC
459         tristate "MPC5121 built-in NAND Flash Controller support"
460         depends on PPC_MPC512x
461         help
462           This enables the driver for the NAND flash controller on the
463           MPC5121 SoC.
464 
465 config MTD_NAND_VF610_NFC
466         tristate "Support for Freescale NFC for VF610/MPC5125"
467         depends on (SOC_VF610 || COMPILE_TEST)
468         depends on HAS_IOMEM
469         help
470           Enables support for NAND Flash Controller on some Freescale
471           processors like the VF610, MPC5125, MCF54418 or Kinetis K70.
472           The driver supports a maximum 2k page size. With 2k pages and
473           64 bytes or more of OOB, hardware ECC with up to 32-bit error
474           correction is supported. Hardware ECC is only enabled through
475           device tree.
476 
477 config MTD_NAND_MXC
478         tristate "MXC NAND support"
479         depends on ARCH_MXC
480         help
481           This enables the driver for the NAND flash controller on the
482           MXC processors.
483 
484 config MTD_NAND_SH_FLCTL
485         tristate "Support for NAND on Renesas SuperH FLCTL"
486         depends on SUPERH || COMPILE_TEST
487         depends on HAS_IOMEM
488         depends on HAS_DMA
489         help
490           Several Renesas SuperH CPU has FLCTL. This option enables support
491           for NAND Flash using FLCTL.
492 
493 config MTD_NAND_DAVINCI
494         tristate "Support NAND on DaVinci/Keystone SoC"
495         depends on ARCH_DAVINCI || (ARCH_KEYSTONE && TI_AEMIF)
496         help
497           Enable the driver for NAND flash chips on Texas Instruments
498           DaVinci/Keystone processors.
499 
500 config MTD_NAND_TXX9NDFMC
501         tristate "NAND Flash support for TXx9 SoC"
502         depends on SOC_TX4938 || SOC_TX4939
503         help
504           This enables the NAND flash controller on the TXx9 SoCs.
505 
506 config MTD_NAND_SOCRATES
507         tristate "Support for NAND on Socrates board"
508         depends on SOCRATES
509         help
510           Enables support for NAND Flash chips wired onto Socrates board.
511 
512 config MTD_NAND_NUC900
513         tristate "Support for NAND on Nuvoton NUC9xx/w90p910 evaluation boards."
514         depends on ARCH_W90X900
515         help
516           This enables the driver for the NAND Flash on evaluation board based
517           on w90p910 / NUC9xx.
518 
519 config MTD_NAND_JZ4740
520         tristate "Support for JZ4740 SoC NAND controller"
521         depends on MACH_JZ4740
522         help
523                 Enables support for NAND Flash on JZ4740 SoC based boards.
524 
525 config MTD_NAND_JZ4780
526         tristate "Support for NAND on JZ4780 SoC"
527         depends on MACH_JZ4780 && JZ4780_NEMC
528         help
529           Enables support for NAND Flash connected to the NEMC on JZ4780 SoC
530           based boards, using the BCH controller for hardware error correction.
531 
532 config MTD_NAND_FSMC
533         tristate "Support for NAND on ST Micros FSMC"
534         depends on PLAT_SPEAR || ARCH_NOMADIK || ARCH_U8500 || MACH_U300
535         help
536           Enables support for NAND Flash chips on the ST Microelectronics
537           Flexible Static Memory Controller (FSMC)
538 
539 config MTD_NAND_XWAY
540         tristate "Support for NAND on Lantiq XWAY SoC"
541         depends on LANTIQ && SOC_TYPE_XWAY
542         help
543           Enables support for NAND Flash chips on Lantiq XWAY SoCs. NAND is attached
544           to the External Bus Unit (EBU).
545 
546 config MTD_NAND_SUNXI
547         tristate "Support for NAND on Allwinner SoCs"
548         depends on ARCH_SUNXI
549         help
550           Enables support for NAND Flash chips on Allwinner SoCs.
551 
552 config MTD_NAND_HISI504
553         tristate "Support for NAND controller on Hisilicon SoC Hip04"
554         depends on HAS_DMA
555         help
556           Enables support for NAND controller on Hisilicon SoC Hip04.
557 
558 config MTD_NAND_QCOM
559         tristate "Support for NAND on QCOM SoCs"
560         depends on ARCH_QCOM
561         help
562           Enables support for NAND flash chips on SoCs containing the EBI2 NAND
563           controller. This controller is found on IPQ806x SoC.
564 
565 config MTD_NAND_MTK
566         tristate "Support for NAND controller on MTK SoCs"
567         depends on HAS_DMA
568         help
569           Enables support for NAND controller on MTK SoCs.
570           This controller is found on mt27xx, mt81xx, mt65xx SoCs.
571 
572 endif # MTD_NAND

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us