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_SPIA 60 tristate "NAND Flash device on SPIA board" 61 depends on ARCH_P720T 62 help 63 If you had to ask, you don't have one. Say 'N'. 64 65config MTD_NAND_AMS_DELTA 66 tristate "NAND Flash device on Amstrad E3" 67 depends on MACH_AMS_DELTA 68 help 69 Support for NAND flash on Amstrad E3 (Delta). 70 71config MTD_NAND_TOTO 72 tristate "NAND Flash device on TOTO board" 73 depends on ARCH_OMAP && BROKEN 74 help 75 Support for NAND flash on Texas Instruments Toto platform. 76 77config MTD_NAND_TS7250 78 tristate "NAND Flash device on TS-7250 board" 79 depends on MACH_TS72XX 80 help 81 Support for NAND flash on Technologic Systems TS-7250 platform. 82 83config MTD_NAND_IDS 84 tristate 85 86config MTD_NAND_AU1550 87 tristate "Au1550/1200 NAND support" 88 depends on SOC_AU1200 || SOC_AU1550 89 help 90 This enables the driver for the NAND flash controller on the 91 AMD/Alchemy 1550 SOC. 92 93config MTD_NAND_BF5XX 94 tristate "Blackfin on-chip NAND Flash Controller driver" 95 depends on (BF54x || BF52x) && MTD_NAND 96 help 97 This enables the Blackfin on-chip NAND flash controller 98 99 No board specific support is done by this driver, each board 100 must advertise a platform_device for the driver to attach. 101 102 This driver can also be built as a module. If so, the module 103 will be called bf5xx-nand. 104 105config MTD_NAND_BF5XX_HWECC 106 bool "BF5XX NAND Hardware ECC" 107 default y 108 depends on MTD_NAND_BF5XX 109 help 110 Enable the use of the BF5XX's internal ECC generator when 111 using NAND. 112 113config MTD_NAND_BF5XX_BOOTROM_ECC 114 bool "Use Blackfin BootROM ECC Layout" 115 default n 116 depends on MTD_NAND_BF5XX_HWECC 117 help 118 If you wish to modify NAND pages and allow the Blackfin on-chip 119 BootROM to boot from them, say Y here. This is only necessary 120 if you are booting U-Boot out of NAND and you wish to update 121 U-Boot from Linux' userspace. Otherwise, you should say N here. 122 123 If unsure, say N. 124 125config MTD_NAND_RTC_FROM4 126 tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)" 127 depends on SH_SOLUTION_ENGINE 128 select REED_SOLOMON 129 select REED_SOLOMON_DEC8 130 select BITREVERSE 131 help 132 This enables the driver for the Renesas Technology AG-AND 133 flash interface board (FROM_BOARD4) 134 135config MTD_NAND_PPCHAMELEONEVB 136 tristate "NAND Flash device on PPChameleonEVB board" 137 depends on PPCHAMELEONEVB && BROKEN 138 help 139 This enables the NAND flash driver on the PPChameleon EVB Board. 140 141config MTD_NAND_S3C2410 142 tristate "NAND Flash support for S3C2410/S3C2440 SoC" 143 depends on ARCH_S3C2410 144 help 145 This enables the NAND flash controller on the S3C2410 and S3C2440 146 SoCs 147 148 No board specific support is done by this driver, each board 149 must advertise a platform_device for the driver to attach. 150 151config MTD_NAND_S3C2410_DEBUG 152 bool "S3C2410 NAND driver debug" 153 depends on MTD_NAND_S3C2410 154 help 155 Enable debugging of the S3C2410 NAND driver 156 157config MTD_NAND_S3C2410_HWECC 158 bool "S3C2410 NAND Hardware ECC" 159 depends on MTD_NAND_S3C2410 160 help 161 Enable the use of the S3C2410's internal ECC generator when 162 using NAND. Early versions of the chip have had problems with 163 incorrect ECC generation, and if using these, the default of 164 software ECC is preferable. 165 166config MTD_NAND_NDFC 167 tristate "NDFC NanD Flash Controller" 168 depends on 4xx && !PPC_MERGE 169 select MTD_NAND_ECC_SMC 170 help 171 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs 172 173config MTD_NAND_S3C2410_CLKSTOP 174 bool "S3C2410 NAND IDLE clock stop" 175 depends on MTD_NAND_S3C2410 176 default n 177 help 178 Stop the clock to the NAND controller when there is no chip 179 selected to save power. This will mean there is a small delay 180 when the is NAND chip selected or released, but will save 181 approximately 5mA of power when there is nothing happening. 182 183config MTD_NAND_DISKONCHIP 184 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)" 185 depends on EXPERIMENTAL 186 select REED_SOLOMON 187 select REED_SOLOMON_DEC16 188 help 189 This is a reimplementation of M-Systems DiskOnChip 2000, 190 Millennium and Millennium Plus as a standard NAND device driver, 191 as opposed to the earlier self-contained MTD device drivers. 192 This should enable, among other things, proper JFFS2 operation on 193 these devices. 194 195config MTD_NAND_DISKONCHIP_PROBE_ADVANCED 196 bool "Advanced detection options for DiskOnChip" 197 depends on MTD_NAND_DISKONCHIP 198 help 199 This option allows you to specify nonstandard address at which to 200 probe for a DiskOnChip, or to change the detection options. You 201 are unlikely to need any of this unless you are using LinuxBIOS. 202 Say 'N'. 203 204config MTD_NAND_DISKONCHIP_PROBE_ADDRESS 205 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED 206 depends on MTD_NAND_DISKONCHIP 207 default "0" 208 ---help--- 209 By default, the probe for DiskOnChip devices will look for a 210 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000. 211 This option allows you to specify a single address at which to probe 212 for the device, which is useful if you have other devices in that 213 range which get upset when they are probed. 214 215 (Note that on PowerPC, the normal probe will only check at 216 0xE4000000.) 217 218 Normally, you should leave this set to zero, to allow the probe at 219 the normal addresses. 220 221config MTD_NAND_DISKONCHIP_PROBE_HIGH 222 bool "Probe high addresses" 223 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED 224 help 225 By default, the probe for DiskOnChip devices will look for a 226 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000. 227 This option changes to make it probe between 0xFFFC8000 and 228 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be 229 useful to you. Say 'N'. 230 231config MTD_NAND_DISKONCHIP_BBTWRITE 232 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP" 233 depends on MTD_NAND_DISKONCHIP 234 help 235 On DiskOnChip devices shipped with the INFTL filesystem (Millennium 236 and 2000 TSOP/Alon), Linux reserves some space at the end of the 237 device for the Bad Block Table (BBT). If you have existing INFTL 238 data on your device (created by non-Linux tools such as M-Systems' 239 DOS drivers), your data might overlap the area Linux wants to use for 240 the BBT. If this is a concern for you, leave this option disabled and 241 Linux will not write BBT data into this area. 242 The downside of leaving this option disabled is that if bad blocks 243 are detected by Linux, they will not be recorded in the BBT, which 244 could cause future problems. 245 Once you enable this option, new filesystems (INFTL or others, created 246 in Linux or other operating systems) will not use the reserved area. 247 The only reason not to enable this option is to prevent damage to 248 preexisting filesystems. 249 Even if you leave this disabled, you can enable BBT writes at module 250 load time (assuming you build diskonchip as a module) with the module 251 parameter "inftl_bbt_write=1". 252 253config MTD_NAND_SHARPSL 254 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)" 255 depends on ARCH_PXA 256 257config MTD_NAND_BASLER_EXCITE 258 tristate "Support for NAND Flash on Basler eXcite" 259 depends on BASLER_EXCITE 260 help 261 This enables the driver for the NAND flash device found on the 262 Basler eXcite Smart Camera. If built as a module, the driver 263 will be named "excite_nandflash.ko". 264 265config MTD_NAND_CAFE 266 tristate "NAND support for OLPC CAFÉ chip" 267 depends on PCI 268 select REED_SOLOMON 269 select REED_SOLOMON_DEC16 270 help 271 Use NAND flash attached to the CAFÉ chip designed for the OLPC 272 laptop. 273 274config MTD_NAND_CS553X 275 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)" 276 depends on X86_32 && (X86_PC || X86_GENERICARCH) 277 help 278 The CS553x companion chips for the AMD Geode processor 279 include NAND flash controllers with built-in hardware ECC 280 capabilities; enabling this option will allow you to use 281 these. The driver will check the MSRs to verify that the 282 controller is enabled for NAND, and currently requires that 283 the controller be in MMIO mode. 284 285 If you say "m", the module will be called "cs553x_nand.ko". 286 287config MTD_NAND_ATMEL 288 tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32" 289 depends on ARCH_AT91 || AVR32 290 help 291 Enables support for NAND Flash / Smart Media Card interface 292 on Atmel AT91 and AVR32 processors. 293choice 294 prompt "ECC management for NAND Flash / SmartMedia on AT91 / AVR32" 295 depends on MTD_NAND_ATMEL 296 297config MTD_NAND_ATMEL_ECC_HW 298 bool "Hardware ECC" 299 depends on ARCH_AT91SAM9263 || ARCH_AT91SAM9260 || AVR32 300 help 301 Use hardware ECC instead of software ECC when the chip 302 supports it. 303 304 The hardware ECC controller is capable of single bit error 305 correction and 2-bit random detection per page. 306 307 NB : hardware and software ECC schemes are incompatible. 308 If you switch from one to another, you'll have to erase your 309 mtd partition. 310 311 If unsure, say Y 312 313config MTD_NAND_ATMEL_ECC_SOFT 314 bool "Software ECC" 315 help 316 Use software ECC. 317 318 NB : hardware and software ECC schemes are incompatible. 319 If you switch from one to another, you'll have to erase your 320 mtd partition. 321 322config MTD_NAND_ATMEL_ECC_NONE 323 bool "No ECC (testing only, DANGEROUS)" 324 depends on DEBUG_KERNEL 325 help 326 No ECC will be used. 327 It's not a good idea and it should be reserved for testing 328 purpose only. 329 330 If unsure, say N 331 332 endchoice 333 334endchoice 335 336config MTD_NAND_PXA3xx 337 bool "Support for NAND flash devices on PXA3xx" 338 depends on MTD_NAND && PXA3xx 339 help 340 This enables the driver for the NAND flash device found on 341 PXA3xx processors 342 343config MTD_NAND_CM_X270 344 tristate "Support for NAND Flash on CM-X270 modules" 345 depends on MTD_NAND && MACH_ARMCORE 346 347config MTD_NAND_PASEMI 348 tristate "NAND support for PA Semi PWRficient" 349 depends on MTD_NAND && PPC_PASEMI 350 help 351 Enables support for NAND Flash interface on PA Semi PWRficient 352 based boards 353 354config MTD_NAND_NANDSIM 355 tristate "Support for NAND Flash Simulator" 356 depends on MTD_PARTITIONS 357 help 358 The simulator may simulate various NAND flash chips for the 359 MTD nand layer. 360 361config MTD_NAND_PLATFORM 362 tristate "Support for generic platform NAND driver" 363 depends on MTD_NAND 364 help 365 This implements a generic NAND driver for on-SOC platform 366 devices. You will need to provide platform-specific functions 367 via platform_data. 368 369config MTD_ALAUDA 370 tristate "MTD driver for Olympus MAUSB-10 and Fujifilm DPC-R1" 371 depends on MTD_NAND && USB 372 help 373 These two (and possibly other) Alauda-based cardreaders for 374 SmartMedia and xD allow raw flash access. 375 376config MTD_NAND_ORION 377 tristate "NAND Flash support for Marvell Orion SoC" 378 depends on PLAT_ORION && MTD_NAND 379 help 380 This enables the NAND flash controller on Orion machines. 381 382 No board specific support is done by this driver, each board 383 must advertise a platform_device for the driver to attach. 384 385config MTD_NAND_FSL_ELBC 386 tristate "NAND support for Freescale eLBC controllers" 387 depends on MTD_NAND && PPC_OF 388 help 389 Various Freescale chips, including the 8313, include a NAND Flash 390 Controller Module with built-in hardware ECC capabilities. 391 Enabling this option will enable you to use this to control 392 external NAND devices. 393 394config MTD_NAND_FSL_UPM 395 tristate "Support for NAND on Freescale UPM" 396 depends on MTD_NAND && OF_GPIO && (PPC_83xx || PPC_85xx) 397 select FSL_LBC 398 help 399 Enables support for NAND Flash chips wired onto Freescale PowerPC 400 processor localbus with User-Programmable Machine support. 401 402endif # MTD_NAND 403