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