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