]> git.proxmox.com Git - mirror_ubuntu-zesty-kernel.git/blob - drivers/mtd/nand/Kconfig
Merge branch 'overlayfs-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mszer...
[mirror_ubuntu-zesty-kernel.git] / drivers / mtd / nand / Kconfig
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_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
23 if MTD_NAND
24
25 config MTD_NAND_BCH
26 tristate
27 select BCH
28 depends on MTD_NAND_ECC_BCH
29 default MTD_NAND
30
31 config MTD_NAND_ECC_BCH
32 bool "Support software BCH ECC"
33 default n
34 help
35 This enables support for software BCH error correction. Binary BCH
36 codes are more powerful and cpu intensive than traditional Hamming
37 ECC codes. They are used with NAND devices requiring more than 1 bit
38 of error correction.
39
40 config MTD_SM_COMMON
41 tristate
42 default n
43
44 config MTD_NAND_DENALI
45 tristate
46
47 config MTD_NAND_DENALI_PCI
48 tristate "Support Denali NAND controller on Intel Moorestown"
49 select MTD_NAND_DENALI
50 depends on HAS_DMA && PCI
51 help
52 Enable the driver for NAND flash on Intel Moorestown, using the
53 Denali NAND controller core.
54
55 config MTD_NAND_DENALI_DT
56 tristate "Support Denali NAND controller as a DT device"
57 select MTD_NAND_DENALI
58 depends on HAS_DMA && HAVE_CLK && OF
59 help
60 Enable the driver for NAND flash on platforms using a Denali NAND
61 controller as a DT device.
62
63 config MTD_NAND_DENALI_SCRATCH_REG_ADDR
64 hex "Denali NAND size scratch register address"
65 default "0xFF108018"
66 depends on MTD_NAND_DENALI_PCI
67 help
68 Some platforms place the NAND chip size in a scratch register
69 because (some versions of) the driver aren't able to automatically
70 determine the size of certain chips. Set the address of the
71 scratch register here to enable this feature. On Intel Moorestown
72 boards, the scratch register is at 0xFF108018.
73
74 config MTD_NAND_GPIO
75 tristate "GPIO assisted NAND Flash driver"
76 depends on GPIOLIB || COMPILE_TEST
77 depends on HAS_IOMEM
78 help
79 This enables a NAND flash driver where control signals are
80 connected to GPIO pins, and commands and data are communicated
81 via a memory mapped interface.
82
83 config MTD_NAND_AMS_DELTA
84 tristate "NAND Flash device on Amstrad E3"
85 depends on MACH_AMS_DELTA
86 default y
87 help
88 Support for NAND flash on Amstrad E3 (Delta).
89
90 config MTD_NAND_OMAP2
91 tristate "NAND Flash device on OMAP2, OMAP3, OMAP4 and Keystone"
92 depends on (ARCH_OMAP2PLUS || ARCH_KEYSTONE)
93 help
94 Support for NAND flash on Texas Instruments OMAP2, OMAP3, OMAP4
95 and Keystone platforms.
96
97 config MTD_NAND_OMAP_BCH
98 depends on MTD_NAND_OMAP2
99 bool "Support hardware based BCH error correction"
100 default n
101 select BCH
102 help
103 This config enables the ELM hardware engine, which can be used to
104 locate and correct errors when using BCH ECC scheme. This offloads
105 the cpu from doing ECC error searching and correction. However some
106 legacy OMAP families like OMAP2xxx, OMAP3xxx do not have ELM engine
107 so this is optional for them.
108
109 config MTD_NAND_OMAP_BCH_BUILD
110 def_tristate MTD_NAND_OMAP2 && MTD_NAND_OMAP_BCH
111
112 config MTD_NAND_IDS
113 tristate
114
115 config MTD_NAND_RICOH
116 tristate "Ricoh xD card reader"
117 default n
118 depends on PCI
119 select MTD_SM_COMMON
120 help
121 Enable support for Ricoh R5C852 xD card reader
122 You also need to enable ether
123 NAND SSFDC (SmartMedia) read only translation layer' or new
124 expermental, readwrite
125 'SmartMedia/xD new translation layer'
126
127 config MTD_NAND_AU1550
128 tristate "Au1550/1200 NAND support"
129 depends on MIPS_ALCHEMY
130 help
131 This enables the driver for the NAND flash controller on the
132 AMD/Alchemy 1550 SOC.
133
134 config MTD_NAND_BF5XX
135 tristate "Blackfin on-chip NAND Flash Controller driver"
136 depends on BF54x || BF52x
137 help
138 This enables the Blackfin on-chip NAND flash controller
139
140 No board specific support is done by this driver, each board
141 must advertise a platform_device for the driver to attach.
142
143 This driver can also be built as a module. If so, the module
144 will be called bf5xx-nand.
145
146 config MTD_NAND_BF5XX_HWECC
147 bool "BF5XX NAND Hardware ECC"
148 default y
149 depends on MTD_NAND_BF5XX
150 help
151 Enable the use of the BF5XX's internal ECC generator when
152 using NAND.
153
154 config MTD_NAND_BF5XX_BOOTROM_ECC
155 bool "Use Blackfin BootROM ECC Layout"
156 default n
157 depends on MTD_NAND_BF5XX_HWECC
158 help
159 If you wish to modify NAND pages and allow the Blackfin on-chip
160 BootROM to boot from them, say Y here. This is only necessary
161 if you are booting U-Boot out of NAND and you wish to update
162 U-Boot from Linux' userspace. Otherwise, you should say N here.
163
164 If unsure, say N.
165
166 config MTD_NAND_S3C2410
167 tristate "NAND Flash support for Samsung S3C SoCs"
168 depends on ARCH_S3C24XX || ARCH_S3C64XX
169 help
170 This enables the NAND flash controller on the S3C24xx and S3C64xx
171 SoCs
172
173 No board specific support is done by this driver, each board
174 must advertise a platform_device for the driver to attach.
175
176 config MTD_NAND_S3C2410_DEBUG
177 bool "Samsung S3C NAND driver debug"
178 depends on MTD_NAND_S3C2410
179 help
180 Enable debugging of the S3C NAND driver
181
182 config MTD_NAND_NDFC
183 tristate "NDFC NanD Flash Controller"
184 depends on 4xx
185 select MTD_NAND_ECC_SMC
186 help
187 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
188
189 config MTD_NAND_S3C2410_CLKSTOP
190 bool "Samsung S3C NAND IDLE clock stop"
191 depends on MTD_NAND_S3C2410
192 default n
193 help
194 Stop the clock to the NAND controller when there is no chip
195 selected to save power. This will mean there is a small delay
196 when the is NAND chip selected or released, but will save
197 approximately 5mA of power when there is nothing happening.
198
199 config MTD_NAND_TANGO
200 tristate "NAND Flash support for Tango chips"
201 depends on ARCH_TANGO || COMPILE_TEST
202 depends on HAS_DMA
203 help
204 Enables the NAND Flash controller on Tango chips.
205
206 config MTD_NAND_DISKONCHIP
207 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation)"
208 depends on HAS_IOMEM
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
218 config 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
227 config 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
244 config 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
254 config 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
276 config MTD_NAND_DOCG4
277 tristate "Support for DiskOnChip G4"
278 depends on HAS_IOMEM
279 select BCH
280 select BITREVERSE
281 help
282 Support for diskonchip G4 nand flash, found in various smartphones and
283 PDAs, among them the Palm Treo680, HTC Prophet and Wizard, Toshiba
284 Portege G900, Asus P526, and O2 XDA Zinc.
285
286 With this driver you will be able to use UBI and create a ubifs on the
287 device, so you may wish to consider enabling UBI and UBIFS as well.
288
289 These devices ship with the Mys/Sandisk SAFTL formatting, for which
290 there is currently no mtd parser, so you may want to use command line
291 partitioning to segregate write-protected blocks. On the Treo680, the
292 first five erase blocks (256KiB each) are write-protected, followed
293 by the block containing the saftl partition table. This is probably
294 typical.
295
296 config MTD_NAND_SHARPSL
297 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
298 depends on ARCH_PXA
299
300 config MTD_NAND_CAFE
301 tristate "NAND support for OLPC CAFÉ chip"
302 depends on PCI
303 select REED_SOLOMON
304 select REED_SOLOMON_DEC16
305 help
306 Use NAND flash attached to the CAFÉ chip designed for the OLPC
307 laptop.
308
309 config MTD_NAND_CS553X
310 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
311 depends on X86_32
312 depends on !UML && HAS_IOMEM
313 help
314 The CS553x companion chips for the AMD Geode processor
315 include NAND flash controllers with built-in hardware ECC
316 capabilities; enabling this option will allow you to use
317 these. The driver will check the MSRs to verify that the
318 controller is enabled for NAND, and currently requires that
319 the controller be in MMIO mode.
320
321 If you say "m", the module will be called cs553x_nand.
322
323 config MTD_NAND_ATMEL
324 tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
325 depends on ARCH_AT91 || AVR32
326 help
327 Enables support for NAND Flash / Smart Media Card interface
328 on Atmel AT91 and AVR32 processors.
329
330 config MTD_NAND_PXA3xx
331 tristate "NAND support on PXA3xx and Armada 370/XP"
332 depends on PXA3xx || ARCH_MMP || PLAT_ORION
333 help
334 This enables the driver for the NAND flash device found on
335 PXA3xx processors (NFCv1) and also on Armada 370/XP (NFCv2).
336
337 config MTD_NAND_SLC_LPC32XX
338 tristate "NXP LPC32xx SLC Controller"
339 depends on ARCH_LPC32XX
340 help
341 Enables support for NXP's LPC32XX SLC (i.e. for Single Level Cell
342 chips) NAND controller. This is the default for the PHYTEC 3250
343 reference board which contains a NAND256R3A2CZA6 chip.
344
345 Please check the actual NAND chip connected and its support
346 by the SLC NAND controller.
347
348 config MTD_NAND_MLC_LPC32XX
349 tristate "NXP LPC32xx MLC Controller"
350 depends on ARCH_LPC32XX
351 help
352 Uses the LPC32XX MLC (i.e. for Multi Level Cell chips) NAND
353 controller. This is the default for the WORK92105 controller
354 board.
355
356 Please check the actual NAND chip connected and its support
357 by the MLC NAND controller.
358
359 config MTD_NAND_CM_X270
360 tristate "Support for NAND Flash on CM-X270 modules"
361 depends on MACH_ARMCORE
362
363 config MTD_NAND_PASEMI
364 tristate "NAND support for PA Semi PWRficient"
365 depends on PPC_PASEMI
366 help
367 Enables support for NAND Flash interface on PA Semi PWRficient
368 based boards
369
370 config MTD_NAND_TMIO
371 tristate "NAND Flash device on Toshiba Mobile IO Controller"
372 depends on MFD_TMIO
373 help
374 Support for NAND flash connected to a Toshiba Mobile IO
375 Controller in some PDAs, including the Sharp SL6000x.
376
377 config MTD_NAND_NANDSIM
378 tristate "Support for NAND Flash Simulator"
379 help
380 The simulator may simulate various NAND flash chips for the
381 MTD nand layer.
382
383 config MTD_NAND_GPMI_NAND
384 tristate "GPMI NAND Flash Controller driver"
385 depends on MTD_NAND && MXS_DMA
386 help
387 Enables NAND Flash support for IMX23, IMX28 or IMX6.
388 The GPMI controller is very powerful, with the help of BCH
389 module, it can do the hardware ECC. The GPMI supports several
390 NAND flashs at the same time. The GPMI may conflicts with other
391 block, such as SD card. So pay attention to it when you enable
392 the GPMI.
393
394 config MTD_NAND_BRCMNAND
395 tristate "Broadcom STB NAND controller"
396 depends on ARM || ARM64 || MIPS
397 help
398 Enables the Broadcom NAND controller driver. The controller was
399 originally designed for Set-Top Box but is used on various BCM7xxx,
400 BCM3xxx, BCM63xxx, iProc/Cygnus and more.
401
402 config MTD_NAND_BCM47XXNFLASH
403 tristate "Support for NAND flash on BCM4706 BCMA bus"
404 depends on BCMA_NFLASH
405 help
406 BCMA bus can have various flash memories attached, they are
407 registered by bcma as platform devices. This enables driver for
408 NAND flash memories. For now only BCM4706 is supported.
409
410 config MTD_NAND_PLATFORM
411 tristate "Support for generic platform NAND driver"
412 depends on HAS_IOMEM
413 help
414 This implements a generic NAND driver for on-SOC platform
415 devices. You will need to provide platform-specific functions
416 via platform_data.
417
418 config MTD_NAND_ORION
419 tristate "NAND Flash support for Marvell Orion SoC"
420 depends on PLAT_ORION
421 help
422 This enables the NAND flash controller on Orion machines.
423
424 No board specific support is done by this driver, each board
425 must advertise a platform_device for the driver to attach.
426
427 config MTD_NAND_OXNAS
428 tristate "NAND Flash support for Oxford Semiconductor SoC"
429 depends on HAS_IOMEM
430 help
431 This enables the NAND flash controller on Oxford Semiconductor SoCs.
432
433 config MTD_NAND_FSL_ELBC
434 tristate "NAND support for Freescale eLBC controllers"
435 depends on FSL_SOC
436 select FSL_LBC
437 help
438 Various Freescale chips, including the 8313, include a NAND Flash
439 Controller Module with built-in hardware ECC capabilities.
440 Enabling this option will enable you to use this to control
441 external NAND devices.
442
443 config MTD_NAND_FSL_IFC
444 tristate "NAND support for Freescale IFC controller"
445 depends on FSL_SOC || ARCH_LAYERSCAPE
446 select FSL_IFC
447 select MEMORY
448 help
449 Various Freescale chips e.g P1010, include a NAND Flash machine
450 with built-in hardware ECC capabilities.
451 Enabling this option will enable you to use this to control
452 external NAND devices.
453
454 config MTD_NAND_FSL_UPM
455 tristate "Support for NAND on Freescale UPM"
456 depends on PPC_83xx || PPC_85xx
457 select FSL_LBC
458 help
459 Enables support for NAND Flash chips wired onto Freescale PowerPC
460 processor localbus with User-Programmable Machine support.
461
462 config MTD_NAND_MPC5121_NFC
463 tristate "MPC5121 built-in NAND Flash Controller support"
464 depends on PPC_MPC512x
465 help
466 This enables the driver for the NAND flash controller on the
467 MPC5121 SoC.
468
469 config MTD_NAND_VF610_NFC
470 tristate "Support for Freescale NFC for VF610/MPC5125"
471 depends on (SOC_VF610 || COMPILE_TEST)
472 depends on HAS_IOMEM
473 help
474 Enables support for NAND Flash Controller on some Freescale
475 processors like the VF610, MPC5125, MCF54418 or Kinetis K70.
476 The driver supports a maximum 2k page size. With 2k pages and
477 64 bytes or more of OOB, hardware ECC with up to 32-bit error
478 correction is supported. Hardware ECC is only enabled through
479 device tree.
480
481 config MTD_NAND_MXC
482 tristate "MXC NAND support"
483 depends on ARCH_MXC
484 help
485 This enables the driver for the NAND flash controller on the
486 MXC processors.
487
488 config MTD_NAND_SH_FLCTL
489 tristate "Support for NAND on Renesas SuperH FLCTL"
490 depends on SUPERH || COMPILE_TEST
491 depends on HAS_IOMEM
492 depends on HAS_DMA
493 help
494 Several Renesas SuperH CPU has FLCTL. This option enables support
495 for NAND Flash using FLCTL.
496
497 config MTD_NAND_DAVINCI
498 tristate "Support NAND on DaVinci/Keystone SoC"
499 depends on ARCH_DAVINCI || (ARCH_KEYSTONE && TI_AEMIF)
500 help
501 Enable the driver for NAND flash chips on Texas Instruments
502 DaVinci/Keystone processors.
503
504 config 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
510 config 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
516 config MTD_NAND_NUC900
517 tristate "Support for NAND on Nuvoton NUC9xx/w90p910 evaluation boards."
518 depends on ARCH_W90X900
519 help
520 This enables the driver for the NAND Flash on evaluation board based
521 on w90p910 / NUC9xx.
522
523 config 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
529 config MTD_NAND_JZ4780
530 tristate "Support for NAND on JZ4780 SoC"
531 depends on MACH_JZ4780 && JZ4780_NEMC
532 help
533 Enables support for NAND Flash connected to the NEMC on JZ4780 SoC
534 based boards, using the BCH controller for hardware error correction.
535
536 config MTD_NAND_FSMC
537 tristate "Support for NAND on ST Micros FSMC"
538 depends on PLAT_SPEAR || ARCH_NOMADIK || ARCH_U8500 || MACH_U300
539 help
540 Enables support for NAND Flash chips on the ST Microelectronics
541 Flexible Static Memory Controller (FSMC)
542
543 config MTD_NAND_XWAY
544 bool "Support for NAND on Lantiq XWAY SoC"
545 depends on LANTIQ && SOC_TYPE_XWAY
546 help
547 Enables support for NAND Flash chips on Lantiq XWAY SoCs. NAND is attached
548 to the External Bus Unit (EBU).
549
550 config MTD_NAND_SUNXI
551 tristate "Support for NAND on Allwinner SoCs"
552 depends on ARCH_SUNXI
553 help
554 Enables support for NAND Flash chips on Allwinner SoCs.
555
556 config MTD_NAND_HISI504
557 tristate "Support for NAND controller on Hisilicon SoC Hip04"
558 depends on HAS_DMA
559 help
560 Enables support for NAND controller on Hisilicon SoC Hip04.
561
562 config MTD_NAND_QCOM
563 tristate "Support for NAND on QCOM SoCs"
564 depends on ARCH_QCOM
565 help
566 Enables support for NAND flash chips on SoCs containing the EBI2 NAND
567 controller. This controller is found on IPQ806x SoC.
568
569 config MTD_NAND_MTK
570 tristate "Support for NAND controller on MTK SoCs"
571 depends on HAS_DMA
572 help
573 Enables support for NAND controller on MTK SoCs.
574 This controller is found on mt27xx, mt81xx, mt65xx SoCs.
575
576 endif # MTD_NAND