drivers/mtd/nand/Kconfig

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