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