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