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