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