1 config MTD_NAND_ECC_SW_HAMMING
4 config MTD_NAND_ECC_SW_HAMMING_SMC
5 bool "NAND ECC Smart Media byte order"
6 depends on MTD_NAND_ECC_SW_HAMMING
9 Software ECC according to the Smart Media Specification.
10 The original Linux implementation had byte 0 and 1 swapped.
12 menuconfig MTD_RAW_NAND
13 tristate "Raw/Parallel NAND Device Support"
16 select MTD_NAND_ECC_SW_HAMMING
18 This enables support for accessing all type of raw/parallel
19 NAND flash devices. For further information see
20 <http://www.linux-mtd.infradead.org/doc/nand.html>.
24 config MTD_NAND_ECC_SW_BCH
25 tristate "Support software BCH ECC"
29 This enables support for software BCH error correction. Binary BCH
30 codes are more powerful and cpu intensive than traditional Hamming
31 ECC codes. They are used with NAND devices requiring more than 1 bit
34 comment "Raw/parallel NAND flash controllers"
36 config MTD_NAND_DENALI
39 config MTD_NAND_DENALI_PCI
40 tristate "Denali NAND controller on Intel Moorestown"
41 select MTD_NAND_DENALI
44 Enable the driver for NAND flash on Intel Moorestown, using the
45 Denali NAND controller core.
47 config MTD_NAND_DENALI_DT
48 tristate "Denali NAND controller as a DT device"
49 select MTD_NAND_DENALI
50 depends on HAS_DMA && HAVE_CLK && OF
52 Enable the driver for NAND flash on platforms using a Denali NAND
53 controller as a DT device.
55 config MTD_NAND_AMS_DELTA
56 tristate "Amstrad E3 NAND controller"
57 depends on MACH_AMS_DELTA || COMPILE_TEST
60 Support for NAND flash on Amstrad E3 (Delta).
63 tristate "OMAP2, OMAP3, OMAP4 and Keystone NAND controller"
64 depends on ARCH_OMAP2PLUS || ARCH_KEYSTONE || COMPILE_TEST
67 Support for NAND flash on Texas Instruments OMAP2, OMAP3, OMAP4
68 and Keystone platforms.
70 config MTD_NAND_OMAP_BCH
71 depends on MTD_NAND_OMAP2
72 bool "Support hardware based BCH error correction"
76 This config enables the ELM hardware engine, which can be used to
77 locate and correct errors when using BCH ECC scheme. This offloads
78 the cpu from doing ECC error searching and correction. However some
79 legacy OMAP families like OMAP2xxx, OMAP3xxx do not have ELM engine
80 so this is optional for them.
82 config MTD_NAND_OMAP_BCH_BUILD
83 def_tristate MTD_NAND_OMAP2 && MTD_NAND_OMAP_BCH
85 config MTD_NAND_AU1550
86 tristate "Au1550/1200 NAND support"
87 depends on MIPS_ALCHEMY
89 This enables the driver for the NAND flash controller on the
93 tristate "IBM/MCC 4xx NAND controller"
95 select MTD_NAND_ECC_SW_HAMMING_SMC
97 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
99 config MTD_NAND_S3C2410
100 tristate "Samsung S3C NAND controller"
101 depends on ARCH_S3C24XX || ARCH_S3C64XX
103 This enables the NAND flash controller on the S3C24xx and S3C64xx
106 No board specific support is done by this driver, each board
107 must advertise a platform_device for the driver to attach.
109 config MTD_NAND_S3C2410_DEBUG
110 bool "Samsung S3C NAND controller debug"
111 depends on MTD_NAND_S3C2410
113 Enable debugging of the S3C NAND driver
115 config MTD_NAND_S3C2410_CLKSTOP
116 bool "Samsung S3C NAND IDLE clock stop"
117 depends on MTD_NAND_S3C2410
120 Stop the clock to the NAND controller when there is no chip
121 selected to save power. This will mean there is a small delay
122 when the is NAND chip selected or released, but will save
123 approximately 5mA of power when there is nothing happening.
125 config MTD_NAND_TANGO
126 tristate "Tango NAND controller"
127 depends on ARCH_TANGO || COMPILE_TEST
130 Enables the NAND Flash controller on Tango chips.
132 config MTD_NAND_SHARPSL
133 tristate "Sharp SL Series (C7xx + others) NAND controller"
134 depends on ARCH_PXA || COMPILE_TEST
138 tristate "OLPC CAFÉ NAND controller"
141 select REED_SOLOMON_DEC16
143 Use NAND flash attached to the CAFÉ chip designed for the OLPC
146 config MTD_NAND_CS553X
147 tristate "CS5535/CS5536 (AMD Geode companion) NAND controller"
149 depends on !UML && HAS_IOMEM
151 The CS553x companion chips for the AMD Geode processor
152 include NAND flash controllers with built-in hardware ECC
153 capabilities; enabling this option will allow you to use
154 these. The driver will check the MSRs to verify that the
155 controller is enabled for NAND, and currently requires that
156 the controller be in MMIO mode.
158 If you say "m", the module will be called cs553x_nand.
160 config MTD_NAND_ATMEL
161 tristate "Atmel AT91 NAND Flash/SmartMedia NAND controller"
162 depends on ARCH_AT91 || COMPILE_TEST
164 select GENERIC_ALLOCATOR
167 Enables support for NAND Flash / Smart Media Card interface
168 on Atmel AT91 processors.
170 config MTD_NAND_ORION
171 tristate "Marvell Orion NAND controller"
172 depends on PLAT_ORION
174 This enables the NAND flash controller on Orion machines.
176 No board specific support is done by this driver, each board
177 must advertise a platform_device for the driver to attach.
179 config MTD_NAND_MARVELL
180 tristate "Marvell EBU NAND controller"
181 depends on PXA3xx || ARCH_MMP || PLAT_ORION || ARCH_MVEBU || \
185 This enables the NAND flash controller driver for Marvell boards,
187 - PXA3xx processors (NFCv1)
188 - 32-bit Armada platforms (XP, 37x, 38x, 39x) (NFCv2)
189 - 64-bit Aramda platforms (7k, 8k) (NFCv2)
191 config MTD_NAND_SLC_LPC32XX
192 tristate "NXP LPC32xx SLC NAND controller"
193 depends on ARCH_LPC32XX || COMPILE_TEST
196 Enables support for NXP's LPC32XX SLC (i.e. for Single Level Cell
197 chips) NAND controller. This is the default for the PHYTEC 3250
198 reference board which contains a NAND256R3A2CZA6 chip.
200 Please check the actual NAND chip connected and its support
201 by the SLC NAND controller.
203 config MTD_NAND_MLC_LPC32XX
204 tristate "NXP LPC32xx MLC NAND controller"
205 depends on ARCH_LPC32XX || COMPILE_TEST
208 Uses the LPC32XX MLC (i.e. for Multi Level Cell chips) NAND
209 controller. This is the default for the WORK92105 controller
212 Please check the actual NAND chip connected and its support
213 by the MLC NAND controller.
215 config MTD_NAND_CM_X270
216 tristate "CM-X270 modules NAND controller"
217 depends on MACH_ARMCORE
219 config MTD_NAND_PASEMI
220 tristate "PA Semi PWRficient NAND controller"
221 depends on PPC_PASEMI
223 Enables support for NAND Flash interface on PA Semi PWRficient
227 tristate "Toshiba Mobile IO NAND controller"
230 Support for NAND flash connected to a Toshiba Mobile IO
231 Controller in some PDAs, including the Sharp SL6000x.
233 config MTD_NAND_BRCMNAND
234 tristate "Broadcom STB NAND controller"
235 depends on ARM || ARM64 || MIPS || COMPILE_TEST
238 Enables the Broadcom NAND controller driver. The controller was
239 originally designed for Set-Top Box but is used on various BCM7xxx,
240 BCM3xxx, BCM63xxx, iProc/Cygnus and more.
242 config MTD_NAND_BCM47XXNFLASH
243 tristate "BCM4706 BCMA NAND controller"
244 depends on BCMA_NFLASH
247 BCMA bus can have various flash memories attached, they are
248 registered by bcma as platform devices. This enables driver for
249 NAND flash memories. For now only BCM4706 is supported.
251 config MTD_NAND_OXNAS
252 tristate "Oxford Semiconductor NAND controller"
253 depends on ARCH_OXNAS || COMPILE_TEST
256 This enables the NAND flash controller on Oxford Semiconductor SoCs.
258 config MTD_NAND_MPC5121_NFC
259 tristate "MPC5121 NAND controller"
260 depends on PPC_MPC512x
262 This enables the driver for the NAND flash controller on the
265 config MTD_NAND_GPMI_NAND
266 tristate "Freescale GPMI NAND controller"
269 Enables NAND Flash support for IMX23, IMX28 or IMX6.
270 The GPMI controller is very powerful, with the help of BCH
271 module, it can do the hardware ECC. The GPMI supports several
272 NAND flashs at the same time.
274 config MTD_NAND_FSL_ELBC
275 tristate "Freescale eLBC NAND controller"
279 Various Freescale chips, including the 8313, include a NAND Flash
280 Controller Module with built-in hardware ECC capabilities.
281 Enabling this option will enable you to use this to control
282 external NAND devices.
284 config MTD_NAND_FSL_IFC
285 tristate "Freescale IFC NAND controller"
286 depends on FSL_SOC || ARCH_LAYERSCAPE || SOC_LS1021A || COMPILE_TEST
291 Various Freescale chips e.g P1010, include a NAND Flash machine
292 with built-in hardware ECC capabilities.
293 Enabling this option will enable you to use this to control
294 external NAND devices.
296 config MTD_NAND_FSL_UPM
297 tristate "Freescale UPM NAND controller"
298 depends on PPC_83xx || PPC_85xx
301 Enables support for NAND Flash chips wired onto Freescale PowerPC
302 processor localbus with User-Programmable Machine support.
304 config MTD_NAND_VF610_NFC
305 tristate "Freescale VF610/MPC5125 NAND controller"
306 depends on (SOC_VF610 || COMPILE_TEST)
309 Enables support for NAND Flash Controller on some Freescale
310 processors like the VF610, MPC5125, MCF54418 or Kinetis K70.
311 The driver supports a maximum 2k page size. With 2k pages and
312 64 bytes or more of OOB, hardware ECC with up to 32-bit error
313 correction is supported. Hardware ECC is only enabled through
317 tristate "Freescale MXC NAND controller"
318 depends on ARCH_MXC || COMPILE_TEST
321 This enables the driver for the NAND flash controller on the
324 config MTD_NAND_SH_FLCTL
325 tristate "Renesas SuperH FLCTL NAND controller"
326 depends on SUPERH || COMPILE_TEST
329 Several Renesas SuperH CPU has FLCTL. This option enables support
330 for NAND Flash using FLCTL.
332 config MTD_NAND_DAVINCI
333 tristate "DaVinci/Keystone NAND controller"
334 depends on ARCH_DAVINCI || (ARCH_KEYSTONE && TI_AEMIF) || COMPILE_TEST
337 Enable the driver for NAND flash chips on Texas Instruments
338 DaVinci/Keystone processors.
340 config MTD_NAND_TXX9NDFMC
341 tristate "TXx9 NAND controller"
342 depends on SOC_TX4938 || SOC_TX4939 || COMPILE_TEST
345 This enables the NAND flash controller on the TXx9 SoCs.
347 config MTD_NAND_SOCRATES
348 tristate "Socrates NAND controller"
351 Enables support for NAND Flash chips wired onto Socrates board.
353 config MTD_NAND_NUC900
354 tristate "Nuvoton NUC9xx/w90p910 NAND controller"
355 depends on ARCH_W90X900 || COMPILE_TEST
358 This enables the driver for the NAND Flash on evaluation board based
361 source "drivers/mtd/nand/raw/ingenic/Kconfig"
364 tristate "ST Micros FSMC NAND controller"
365 depends on OF && HAS_IOMEM
366 depends on PLAT_SPEAR || ARCH_NOMADIK || ARCH_U8500 || MACH_U300 || \
369 Enables support for NAND Flash chips on the ST Microelectronics
370 Flexible Static Memory Controller (FSMC)
373 bool "Lantiq XWAY NAND controller"
374 depends on LANTIQ && SOC_TYPE_XWAY
376 Enables support for NAND Flash chips on Lantiq XWAY SoCs. NAND is attached
377 to the External Bus Unit (EBU).
379 config MTD_NAND_SUNXI
380 tristate "Allwinner NAND controller"
381 depends on ARCH_SUNXI || COMPILE_TEST
384 Enables support for NAND Flash chips on Allwinner SoCs.
386 config MTD_NAND_HISI504
387 tristate "Hisilicon Hip04 NAND controller"
388 depends on ARCH_HISI || COMPILE_TEST
391 Enables support for NAND controller on Hisilicon SoC Hip04.
394 tristate "QCOM NAND controller"
395 depends on ARCH_QCOM || COMPILE_TEST
398 Enables support for NAND flash chips on SoCs containing the EBI2 NAND
399 controller. This controller is found on IPQ806x SoC.
402 tristate "MTK NAND controller"
403 depends on ARCH_MEDIATEK || COMPILE_TEST
406 Enables support for NAND controller on MTK SoCs.
407 This controller is found on mt27xx, mt81xx, mt65xx SoCs.
409 config MTD_NAND_TEGRA
410 tristate "NVIDIA Tegra NAND controller"
411 depends on ARCH_TEGRA || COMPILE_TEST
414 Enables support for NAND flash controller on NVIDIA Tegra SoC.
415 The driver has been developed and tested on a Tegra 2 SoC. DMA
416 support, raw read/write page as well as HW ECC read/write page
417 is supported. Extra OOB bytes when using HW ECC are currently
420 config MTD_NAND_STM32_FMC2
421 tristate "Support for NAND controller on STM32MP SoCs"
422 depends on MACH_STM32MP157 || COMPILE_TEST
424 Enables support for NAND Flash chips on SoCs containing the FMC2
425 NAND controller. This controller is found on STM32MP SoCs.
426 The controller supports a maximum 8k page size and supports
427 a maximum 8-bit correction error per sector of 512 bytes.
429 config MTD_NAND_MESON
430 tristate "Support for NAND controller on Amlogic's Meson SoCs"
431 depends on ARCH_MESON || COMPILE_TEST
434 Enables support for NAND controller on Amlogic's Meson SoCs.
435 This controller is found on Meson SoCs.
438 tristate "GPIO assisted NAND controller"
439 depends on GPIOLIB || COMPILE_TEST
442 This enables a NAND flash driver where control signals are
443 connected to GPIO pins, and commands and data are communicated
444 via a memory mapped interface.
446 config MTD_NAND_PLATFORM
447 tristate "Generic NAND controller"
450 This implements a generic NAND driver for on-SOC platform
451 devices. You will need to provide platform-specific functions
460 config MTD_NAND_NANDSIM
461 tristate "Support for NAND Flash Simulator"
463 The simulator may simulate various NAND flash chips for the
466 config MTD_NAND_RICOH
467 tristate "Ricoh xD card reader"
472 Enable support for Ricoh R5C852 xD card reader
473 You also need to enable ether
474 NAND SSFDC (SmartMedia) read only translation layer' or new
475 expermental, readwrite
476 'SmartMedia/xD new translation layer'
478 config MTD_NAND_DISKONCHIP
479 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation)"
482 select REED_SOLOMON_DEC16
484 This is a reimplementation of M-Systems DiskOnChip 2000,
485 Millennium and Millennium Plus as a standard NAND device driver,
486 as opposed to the earlier self-contained MTD device drivers.
487 This should enable, among other things, proper JFFS2 operation on
490 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
491 bool "Advanced detection options for DiskOnChip"
492 depends on MTD_NAND_DISKONCHIP
494 This option allows you to specify nonstandard address at which to
495 probe for a DiskOnChip, or to change the detection options. You
496 are unlikely to need any of this unless you are using LinuxBIOS.
499 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
500 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
501 depends on MTD_NAND_DISKONCHIP
504 By default, the probe for DiskOnChip devices will look for a
505 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
506 This option allows you to specify a single address at which to probe
507 for the device, which is useful if you have other devices in that
508 range which get upset when they are probed.
510 (Note that on PowerPC, the normal probe will only check at
513 Normally, you should leave this set to zero, to allow the probe at
514 the normal addresses.
516 config MTD_NAND_DISKONCHIP_PROBE_HIGH
517 bool "Probe high addresses"
518 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
520 By default, the probe for DiskOnChip devices will look for a
521 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
522 This option changes to make it probe between 0xFFFC8000 and
523 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
524 useful to you. Say 'N'.
526 config MTD_NAND_DISKONCHIP_BBTWRITE
527 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
528 depends on MTD_NAND_DISKONCHIP
530 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
531 and 2000 TSOP/Alon), Linux reserves some space at the end of the
532 device for the Bad Block Table (BBT). If you have existing INFTL
533 data on your device (created by non-Linux tools such as M-Systems'
534 DOS drivers), your data might overlap the area Linux wants to use for
535 the BBT. If this is a concern for you, leave this option disabled and
536 Linux will not write BBT data into this area.
537 The downside of leaving this option disabled is that if bad blocks
538 are detected by Linux, they will not be recorded in the BBT, which
539 could cause future problems.
540 Once you enable this option, new filesystems (INFTL or others, created
541 in Linux or other operating systems) will not use the reserved area.
542 The only reason not to enable this option is to prevent damage to
543 preexisting filesystems.
544 Even if you leave this disabled, you can enable BBT writes at module
545 load time (assuming you build diskonchip as a module) with the module
546 parameter "inftl_bbt_write=1".