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