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