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_VERIFY_WRITE
  26         bool "Verify NAND page writes"
  27         help
  28           This adds an extra check when data is written to the flash. The
  29           NAND flash device internally checks only bits transitioning
  30           from 1 to 0. There is a rare possibility that even though the
  31           device thinks the write was successful, a bit could have been
  32           flipped accidentally due to device wear or something else.
  33
  34 config MTD_NAND_BCH
  35         tristate
  36         select BCH
  37         depends on MTD_NAND_ECC_BCH
  38         default MTD_NAND
  39
  40 config MTD_NAND_ECC_BCH
  41         bool "Support software BCH ECC"
  42         default n
  43         help
  44           This enables support for software BCH error correction. Binary BCH
  45           codes are more powerful and cpu intensive than traditional Hamming
  46           ECC codes. They are used with NAND devices requiring more than 1 bit
  47           of error correction.
  48
  49 config MTD_SM_COMMON
  50         tristate
  51         default n
  52
  53 config MTD_NAND_MUSEUM_IDS
  54         bool "Enable chip ids for obsolete ancient NAND devices"
  55         default n
  56         help
  57           Enable this option only when your board has first generation
  58           NAND chips (page size 256 byte, erase size 4-8KiB). The IDs
  59           of these chips were reused by later, larger chips.
  60
  61 config MTD_NAND_AUTCPU12
  62         tristate "SmartMediaCard on autronix autcpu12 board"
  63         depends on ARCH_AUTCPU12
  64         help
  65           This enables the driver for the autronix autcpu12 board to
  66           access the SmartMediaCard.
  67
  68 config MTD_NAND_DENALI
  69        depends on PCI
  70         tristate "Support Denali NAND controller on Intel Moorestown"
  71         help
  72           Enable the driver for NAND flash on Intel Moorestown, using the
  73           Denali NAND controller core.
  74
  75 config MTD_NAND_DENALI_SCRATCH_REG_ADDR
  76         hex "Denali NAND size scratch register address"
  77         default "0xFF108018"
  78         depends on MTD_NAND_DENALI
  79         help
  80           Some platforms place the NAND chip size in a scratch register
  81           because (some versions of) the driver aren't able to automatically
  82           determine the size of certain chips. Set the address of the
  83           scratch register here to enable this feature. On Intel Moorestown
  84           boards, the scratch register is at 0xFF108018.
  85
  86 config MTD_NAND_H1900
  87         tristate "iPAQ H1900 flash"
  88         depends on ARCH_PXA && BROKEN
  89         help
  90           This enables the driver for the iPAQ h1900 flash.
  91
  92 config MTD_NAND_GPIO
  93         tristate "GPIO NAND Flash driver"
  94         depends on GENERIC_GPIO && ARM
  95         help
  96           This enables a GPIO based NAND flash driver.
  97
  98 config MTD_NAND_SPIA
  99         tristate "NAND Flash device on SPIA board"
 100         depends on ARCH_P720T
 101         help
 102           If you had to ask, you don't have one. Say 'N'.
 103
 104 config MTD_NAND_AMS_DELTA
 105         tristate "NAND Flash device on Amstrad E3"
 106         depends on MACH_AMS_DELTA
 107         default y
 108         help
 109           Support for NAND flash on Amstrad E3 (Delta).
 110
 111 config MTD_NAND_OMAP2
 112         tristate "NAND Flash device on OMAP2, OMAP3 and OMAP4"
 113         depends on ARCH_OMAP2PLUS
 114         help
 115           Support for NAND flash on Texas Instruments OMAP2, OMAP3 and OMAP4
 116           platforms.
 117
 118 config MTD_NAND_IDS
 119         tristate
 120
 121 config MTD_NAND_RICOH
 122         tristate "Ricoh xD card reader"
 123         default n
 124         depends on PCI
 125         select MTD_SM_COMMON
 126         help
 127           Enable support for Ricoh R5C852 xD card reader
 128           You also need to enable ether
 129           NAND SSFDC (SmartMedia) read only translation layer' or new
 130           expermental, readwrite
 131           'SmartMedia/xD new translation layer'
 132
 133 config MTD_NAND_AU1550
 134         tristate "Au1550/1200 NAND support"
 135         depends on MIPS_ALCHEMY
 136         help
 137           This enables the driver for the NAND flash controller on the
 138           AMD/Alchemy 1550 SOC.
 139
 140 config MTD_NAND_BF5XX
 141         tristate "Blackfin on-chip NAND Flash Controller driver"
 142         depends on BF54x || BF52x
 143         help
 144           This enables the Blackfin on-chip NAND flash controller
 145
 146           No board specific support is done by this driver, each board
 147           must advertise a platform_device for the driver to attach.
 148
 149           This driver can also be built as a module. If so, the module
 150           will be called bf5xx-nand.
 151
 152 config MTD_NAND_BF5XX_HWECC
 153         bool "BF5XX NAND Hardware ECC"
 154         default y
 155         depends on MTD_NAND_BF5XX
 156         help
 157           Enable the use of the BF5XX's internal ECC generator when
 158           using NAND.
 159
 160 config MTD_NAND_BF5XX_BOOTROM_ECC
 161         bool "Use Blackfin BootROM ECC Layout"
 162         default n
 163         depends on MTD_NAND_BF5XX_HWECC
 164         help
 165           If you wish to modify NAND pages and allow the Blackfin on-chip
 166           BootROM to boot from them, say Y here.  This is only necessary
 167           if you are booting U-Boot out of NAND and you wish to update
 168           U-Boot from Linux' userspace.  Otherwise, you should say N here.
 169
 170           If unsure, say N.
 171
 172 config MTD_NAND_RTC_FROM4
 173         tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
 174         depends on SH_SOLUTION_ENGINE
 175         select REED_SOLOMON
 176         select REED_SOLOMON_DEC8
 177         select BITREVERSE
 178         help
 179           This enables the driver for the Renesas Technology AG-AND
 180           flash interface board (FROM_BOARD4)
 181
 182 config MTD_NAND_PPCHAMELEONEVB
 183         tristate "NAND Flash device on PPChameleonEVB board"
 184         depends on PPCHAMELEONEVB && BROKEN
 185         help
 186           This enables the NAND flash driver on the PPChameleon EVB Board.
 187
 188 config MTD_NAND_S3C2410
 189         tristate "NAND Flash support for Samsung S3C SoCs"
 190         depends on ARCH_S3C2410 || ARCH_S3C64XX
 191         help
 192           This enables the NAND flash controller on the S3C24xx and S3C64xx
 193           SoCs
 194
 195           No board specific support is done by this driver, each board
 196           must advertise a platform_device for the driver to attach.
 197
 198 config MTD_NAND_S3C2410_DEBUG
 199         bool "Samsung S3C NAND driver debug"
 200         depends on MTD_NAND_S3C2410
 201         help
 202           Enable debugging of the S3C NAND driver
 203
 204 config MTD_NAND_S3C2410_HWECC
 205         bool "Samsung S3C NAND Hardware ECC"
 206         depends on MTD_NAND_S3C2410
 207         help
 208           Enable the use of the controller's internal ECC generator when
 209           using NAND. Early versions of the chips have had problems with
 210           incorrect ECC generation, and if using these, the default of
 211           software ECC is preferable.
 212
 213 config MTD_NAND_NDFC
 214         tristate "NDFC NanD Flash Controller"
 215         depends on 4xx
 216         select MTD_NAND_ECC_SMC
 217         help
 218          NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
 219
 220 config MTD_NAND_S3C2410_CLKSTOP
 221         bool "Samsung S3C NAND IDLE clock stop"
 222         depends on MTD_NAND_S3C2410
 223         default n
 224         help
 225           Stop the clock to the NAND controller when there is no chip
 226           selected to save power. This will mean there is a small delay
 227           when the is NAND chip selected or released, but will save
 228           approximately 5mA of power when there is nothing happening.
 229
 230 config MTD_NAND_BCM_UMI
 231         tristate "NAND Flash support for BCM Reference Boards"
 232         depends on ARCH_BCMRING
 233         help
 234           This enables the NAND flash controller on the BCM UMI block.
 235
 236           No board specific support is done by this driver, each board
 237           must advertise a platform_device for the driver to attach.
 238
 239 config MTD_NAND_BCM_UMI_HWCS
 240         bool "BCM UMI NAND Hardware CS"
 241         depends on MTD_NAND_BCM_UMI
 242         help
 243           Enable the use of the BCM UMI block's internal CS using NAND.
 244           This should only be used if you know the external NAND CS can toggle.
 245
 246 config MTD_NAND_DISKONCHIP
 247         tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
 248         depends on EXPERIMENTAL
 249         select REED_SOLOMON
 250         select REED_SOLOMON_DEC16
 251         help
 252           This is a reimplementation of M-Systems DiskOnChip 2000,
 253           Millennium and Millennium Plus as a standard NAND device driver,
 254           as opposed to the earlier self-contained MTD device drivers.
 255           This should enable, among other things, proper JFFS2 operation on
 256           these devices.
 257
 258 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
 259         bool "Advanced detection options for DiskOnChip"
 260         depends on MTD_NAND_DISKONCHIP
 261         help
 262           This option allows you to specify nonstandard address at which to
 263           probe for a DiskOnChip, or to change the detection options.  You
 264           are unlikely to need any of this unless you are using LinuxBIOS.
 265           Say 'N'.
 266
 267 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
 268         hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
 269         depends on MTD_NAND_DISKONCHIP
 270         default "0"
 271         ---help---
 272         By default, the probe for DiskOnChip devices will look for a
 273         DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
 274         This option allows you to specify a single address at which to probe
 275         for the device, which is useful if you have other devices in that
 276         range which get upset when they are probed.
 277
 278         (Note that on PowerPC, the normal probe will only check at
 279         0xE4000000.)
 280
 281         Normally, you should leave this set to zero, to allow the probe at
 282         the normal addresses.
 283
 284 config MTD_NAND_DISKONCHIP_PROBE_HIGH
 285         bool "Probe high addresses"
 286         depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
 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 changes to make it probe between 0xFFFC8000 and
 291           0xFFFEE000.  Unless you are using LinuxBIOS, this is unlikely to be
 292           useful to you.  Say 'N'.
 293
 294 config MTD_NAND_DISKONCHIP_BBTWRITE
 295         bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
 296         depends on MTD_NAND_DISKONCHIP
 297         help
 298           On DiskOnChip devices shipped with the INFTL filesystem (Millennium
 299           and 2000 TSOP/Alon), Linux reserves some space at the end of the
 300           device for the Bad Block Table (BBT).  If you have existing INFTL
 301           data on your device (created by non-Linux tools such as M-Systems'
 302           DOS drivers), your data might overlap the area Linux wants to use for
 303           the BBT.  If this is a concern for you, leave this option disabled and
 304           Linux will not write BBT data into this area.
 305           The downside of leaving this option disabled is that if bad blocks
 306           are detected by Linux, they will not be recorded in the BBT, which
 307           could cause future problems.
 308           Once you enable this option, new filesystems (INFTL or others, created
 309           in Linux or other operating systems) will not use the reserved area.
 310           The only reason not to enable this option is to prevent damage to
 311           preexisting filesystems.
 312           Even if you leave this disabled, you can enable BBT writes at module
 313           load time (assuming you build diskonchip as a module) with the module
 314           parameter "inftl_bbt_write=1".
 315
 316 config MTD_NAND_SHARPSL
 317         tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
 318         depends on ARCH_PXA
 319
 320 config MTD_NAND_CAFE
 321         tristate "NAND support for OLPC CAFÉ chip"
 322         depends on PCI
 323         select REED_SOLOMON
 324         select REED_SOLOMON_DEC16
 325         help
 326           Use NAND flash attached to the CAFÉ chip designed for the OLPC
 327           laptop.
 328
 329 config MTD_NAND_CS553X
 330         tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
 331         depends on X86_32
 332         help
 333           The CS553x companion chips for the AMD Geode processor
 334           include NAND flash controllers with built-in hardware ECC
 335           capabilities; enabling this option will allow you to use
 336           these. The driver will check the MSRs to verify that the
 337           controller is enabled for NAND, and currently requires that
 338           the controller be in MMIO mode.
 339
 340           If you say "m", the module will be called cs553x_nand.
 341
 342 config MTD_NAND_ATMEL
 343         tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
 344         depends on ARCH_AT91 || AVR32
 345         help
 346           Enables support for NAND Flash / Smart Media Card interface
 347           on Atmel AT91 and AVR32 processors.
 348 choice
 349         prompt "ECC management for NAND Flash / SmartMedia on AT91 / AVR32"
 350         depends on MTD_NAND_ATMEL
 351
 352 config MTD_NAND_ATMEL_ECC_HW
 353         bool "Hardware ECC"
 354         depends on ARCH_AT91SAM9263 || ARCH_AT91SAM9260 || AVR32
 355         help
 356           Use hardware ECC instead of software ECC when the chip
 357           supports it.
 358
 359           The hardware ECC controller is capable of single bit error
 360           correction and 2-bit random detection per page.
 361
 362           NB : hardware and software ECC schemes are incompatible.
 363           If you switch from one to another, you'll have to erase your
 364           mtd partition.
 365
 366           If unsure, say Y
 367
 368 config MTD_NAND_ATMEL_ECC_SOFT
 369         bool "Software ECC"
 370         help
 371           Use software ECC.
 372
 373           NB : hardware and software ECC schemes are incompatible.
 374           If you switch from one to another, you'll have to erase your
 375           mtd partition.
 376
 377 config MTD_NAND_ATMEL_ECC_NONE
 378         bool "No ECC (testing only, DANGEROUS)"
 379         depends on DEBUG_KERNEL
 380         help
 381           No ECC will be used.
 382           It's not a good idea and it should be reserved for testing
 383           purpose only.
 384
 385           If unsure, say N
 386
 387 endchoice
 388
 389 config MTD_NAND_PXA3xx
 390         tristate "Support for NAND flash devices on PXA3xx"
 391         depends on PXA3xx || ARCH_MMP
 392         help
 393           This enables the driver for the NAND flash device found on
 394           PXA3xx processors
 395
 396 config MTD_NAND_CM_X270
 397         tristate "Support for NAND Flash on CM-X270 modules"
 398         depends on MACH_ARMCORE
 399
 400 config MTD_NAND_PASEMI
 401         tristate "NAND support for PA Semi PWRficient"
 402         depends on PPC_PASEMI
 403         help
 404           Enables support for NAND Flash interface on PA Semi PWRficient
 405           based boards
 406
 407 config MTD_NAND_TMIO
 408         tristate "NAND Flash device on Toshiba Mobile IO Controller"
 409         depends on MFD_TMIO
 410         help
 411           Support for NAND flash connected to a Toshiba Mobile IO
 412           Controller in some PDAs, including the Sharp SL6000x.
 413
 414 config MTD_NAND_NANDSIM
 415         tristate "Support for NAND Flash Simulator"
 416         help
 417           The simulator may simulate various NAND flash chips for the
 418           MTD nand layer.
 419
 420 config MTD_NAND_GPMI_NAND
 421         bool "GPMI NAND Flash Controller driver"
 422         depends on MTD_NAND && (SOC_IMX23 || SOC_IMX28)
 423         select MTD_CMDLINE_PARTS
 424         help
 425          Enables NAND Flash support for IMX23 or IMX28.
 426          The GPMI controller is very powerful, with the help of BCH
 427          module, it can do the hardware ECC. The GPMI supports several
 428          NAND flashs at the same time. The GPMI may conflicts with other
 429          block, such as SD card. So pay attention to it when you enable
 430          the GPMI.
 431
 432 config MTD_NAND_PLATFORM
 433         tristate "Support for generic platform NAND driver"
 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_UPM
 466         tristate "Support for NAND on Freescale UPM"
 467         depends on PPC_83xx || PPC_85xx
 468         select FSL_LBC
 469         help
 470           Enables support for NAND Flash chips wired onto Freescale PowerPC
 471           processor localbus with User-Programmable Machine support.
 472
 473 config MTD_NAND_MPC5121_NFC
 474         tristate "MPC5121 built-in NAND Flash Controller support"
 475         depends on PPC_MPC512x
 476         help
 477           This enables the driver for the NAND flash controller on the
 478           MPC5121 SoC.
 479
 480 config MTD_NAND_MXC
 481         tristate "MXC NAND support"
 482         depends on IMX_HAVE_PLATFORM_MXC_NAND
 483         help
 484           This enables the driver for the NAND flash controller on the
 485           MXC processors.
 486
 487 config MTD_NAND_NOMADIK
 488         tristate "ST Nomadik 8815 NAND support"
 489         depends on ARCH_NOMADIK
 490         help
 491           Driver for the NAND flash controller on the Nomadik, with ECC.
 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 || PLAT_NOMADIK || MACH_U300
 535         help
 536           Enables support for NAND Flash chips on the ST Microelectronics
 537           Flexible Static Memory Controller (FSMC)
 538
 539 endif # MTD_NAND