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