xref: /openbmc/linux/drivers/mtd/nand/Kconfig (revision 68198dca)
1config MTD_NAND_ECC
2	tristate
3
4config 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
13menuconfig 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
22if MTD_NAND
23
24config MTD_NAND_BCH
25	tristate
26	select BCH
27	depends on MTD_NAND_ECC_BCH
28	default MTD_NAND
29
30config 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
39config MTD_SM_COMMON
40	tristate
41	default n
42
43config MTD_NAND_DENALI
44	tristate
45
46config 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
54config 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
62config 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
71config 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
78config 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
85config 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
97config MTD_NAND_OMAP_BCH_BUILD
98	def_tristate MTD_NAND_OMAP2 && MTD_NAND_OMAP_BCH
99
100config 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
112config 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
119config 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
131config 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
139config 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
151config 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
161config 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
167config 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
174config 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
184config 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
191config 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
203config 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
212config 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
229config 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
239config 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
261config 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
281config MTD_NAND_SHARPSL
282	tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
283	depends on ARCH_PXA
284
285config 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
294config 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
308config 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
316config 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
321	  This enables the driver for the NAND flash device found on
322	  PXA3xx processors (NFCv1) and also on 32-bit Armada
323	  platforms (XP, 370, 375, 38x, 39x) and 64-bit Armada
324	  platforms (7K, 8K) (NFCv2).
325
326config MTD_NAND_SLC_LPC32XX
327	tristate "NXP LPC32xx SLC Controller"
328	depends on ARCH_LPC32XX
329	help
330	  Enables support for NXP's LPC32XX SLC (i.e. for Single Level Cell
331	  chips) NAND controller. This is the default for the PHYTEC 3250
332	  reference board which contains a NAND256R3A2CZA6 chip.
333
334	  Please check the actual NAND chip connected and its support
335	  by the SLC NAND controller.
336
337config MTD_NAND_MLC_LPC32XX
338	tristate "NXP LPC32xx MLC Controller"
339	depends on ARCH_LPC32XX
340	help
341	  Uses the LPC32XX MLC (i.e. for Multi Level Cell chips) NAND
342	  controller. This is the default for the WORK92105 controller
343	  board.
344
345	  Please check the actual NAND chip connected and its support
346	  by the MLC NAND controller.
347
348config MTD_NAND_CM_X270
349	tristate "Support for NAND Flash on CM-X270 modules"
350	depends on MACH_ARMCORE
351
352config MTD_NAND_PASEMI
353	tristate "NAND support for PA Semi PWRficient"
354	depends on PPC_PASEMI
355	help
356	  Enables support for NAND Flash interface on PA Semi PWRficient
357	  based boards
358
359config MTD_NAND_TMIO
360	tristate "NAND Flash device on Toshiba Mobile IO Controller"
361	depends on MFD_TMIO
362	help
363	  Support for NAND flash connected to a Toshiba Mobile IO
364	  Controller in some PDAs, including the Sharp SL6000x.
365
366config MTD_NAND_NANDSIM
367	tristate "Support for NAND Flash Simulator"
368	help
369	  The simulator may simulate various NAND flash chips for the
370	  MTD nand layer.
371
372config MTD_NAND_GPMI_NAND
373        tristate "GPMI NAND Flash Controller driver"
374        depends on MTD_NAND && MXS_DMA
375        help
376	 Enables NAND Flash support for IMX23, IMX28 or IMX6.
377	 The GPMI controller is very powerful, with the help of BCH
378	 module, it can do the hardware ECC. The GPMI supports several
379	 NAND flashs at the same time. The GPMI may conflicts with other
380	 block, such as SD card. So pay attention to it when you enable
381	 the GPMI.
382
383config MTD_NAND_BRCMNAND
384	tristate "Broadcom STB NAND controller"
385	depends on ARM || ARM64 || MIPS
386	help
387	  Enables the Broadcom NAND controller driver. The controller was
388	  originally designed for Set-Top Box but is used on various BCM7xxx,
389	  BCM3xxx, BCM63xxx, iProc/Cygnus and more.
390
391config MTD_NAND_BCM47XXNFLASH
392	tristate "Support for NAND flash on BCM4706 BCMA bus"
393	depends on BCMA_NFLASH
394	help
395	  BCMA bus can have various flash memories attached, they are
396	  registered by bcma as platform devices. This enables driver for
397	  NAND flash memories. For now only BCM4706 is supported.
398
399config MTD_NAND_PLATFORM
400	tristate "Support for generic platform NAND driver"
401	depends on HAS_IOMEM
402	help
403	  This implements a generic NAND driver for on-SOC platform
404	  devices. You will need to provide platform-specific functions
405	  via platform_data.
406
407config MTD_NAND_ORION
408	tristate "NAND Flash support for Marvell Orion SoC"
409	depends on PLAT_ORION
410	help
411	  This enables the NAND flash controller on Orion machines.
412
413	  No board specific support is done by this driver, each board
414	  must advertise a platform_device for the driver to attach.
415
416config MTD_NAND_OXNAS
417	tristate "NAND Flash support for Oxford Semiconductor SoC"
418	depends on ARCH_OXNAS || COMPILE_TEST
419	depends on HAS_IOMEM
420	help
421	  This enables the NAND flash controller on Oxford Semiconductor SoCs.
422
423config MTD_NAND_FSL_ELBC
424	tristate "NAND support for Freescale eLBC controllers"
425	depends on FSL_SOC
426	select FSL_LBC
427	help
428	  Various Freescale chips, including the 8313, include a NAND Flash
429	  Controller Module with built-in hardware ECC capabilities.
430	  Enabling this option will enable you to use this to control
431	  external NAND devices.
432
433config MTD_NAND_FSL_IFC
434	tristate "NAND support for Freescale IFC controller"
435	depends on FSL_SOC || ARCH_LAYERSCAPE || SOC_LS1021A
436	select FSL_IFC
437	select MEMORY
438	help
439	  Various Freescale chips e.g P1010, include a NAND Flash machine
440	  with built-in hardware ECC capabilities.
441	  Enabling this option will enable you to use this to control
442	  external NAND devices.
443
444config MTD_NAND_FSL_UPM
445	tristate "Support for NAND on Freescale UPM"
446	depends on PPC_83xx || PPC_85xx
447	select FSL_LBC
448	help
449	  Enables support for NAND Flash chips wired onto Freescale PowerPC
450	  processor localbus with User-Programmable Machine support.
451
452config MTD_NAND_MPC5121_NFC
453	tristate "MPC5121 built-in NAND Flash Controller support"
454	depends on PPC_MPC512x
455	help
456	  This enables the driver for the NAND flash controller on the
457	  MPC5121 SoC.
458
459config MTD_NAND_VF610_NFC
460	tristate "Support for Freescale NFC for VF610/MPC5125"
461	depends on (SOC_VF610 || COMPILE_TEST)
462	depends on HAS_IOMEM
463	help
464	  Enables support for NAND Flash Controller on some Freescale
465	  processors like the VF610, MPC5125, MCF54418 or Kinetis K70.
466	  The driver supports a maximum 2k page size. With 2k pages and
467	  64 bytes or more of OOB, hardware ECC with up to 32-bit error
468	  correction is supported. Hardware ECC is only enabled through
469	  device tree.
470
471config MTD_NAND_MXC
472	tristate "MXC NAND support"
473	depends on ARCH_MXC
474	help
475	  This enables the driver for the NAND flash controller on the
476	  MXC processors.
477
478config MTD_NAND_SH_FLCTL
479	tristate "Support for NAND on Renesas SuperH FLCTL"
480	depends on SUPERH || COMPILE_TEST
481	depends on HAS_IOMEM
482	depends on HAS_DMA
483	help
484	  Several Renesas SuperH CPU has FLCTL. This option enables support
485	  for NAND Flash using FLCTL.
486
487config MTD_NAND_DAVINCI
488        tristate "Support NAND on DaVinci/Keystone SoC"
489        depends on ARCH_DAVINCI || (ARCH_KEYSTONE && TI_AEMIF)
490        help
491	  Enable the driver for NAND flash chips on Texas Instruments
492	  DaVinci/Keystone processors.
493
494config MTD_NAND_TXX9NDFMC
495	tristate "NAND Flash support for TXx9 SoC"
496	depends on SOC_TX4938 || SOC_TX4939
497	help
498	  This enables the NAND flash controller on the TXx9 SoCs.
499
500config MTD_NAND_SOCRATES
501	tristate "Support for NAND on Socrates board"
502	depends on SOCRATES
503	help
504	  Enables support for NAND Flash chips wired onto Socrates board.
505
506config MTD_NAND_NUC900
507	tristate "Support for NAND on Nuvoton NUC9xx/w90p910 evaluation boards."
508	depends on ARCH_W90X900
509	help
510	  This enables the driver for the NAND Flash on evaluation board based
511	  on w90p910 / NUC9xx.
512
513config MTD_NAND_JZ4740
514	tristate "Support for JZ4740 SoC NAND controller"
515	depends on MACH_JZ4740
516	help
517		Enables support for NAND Flash on JZ4740 SoC based boards.
518
519config MTD_NAND_JZ4780
520	tristate "Support for NAND on JZ4780 SoC"
521	depends on MACH_JZ4780 && JZ4780_NEMC
522	help
523	  Enables support for NAND Flash connected to the NEMC on JZ4780 SoC
524	  based boards, using the BCH controller for hardware error correction.
525
526config MTD_NAND_FSMC
527	tristate "Support for NAND on ST Micros FSMC"
528	depends on OF
529	depends on PLAT_SPEAR || ARCH_NOMADIK || ARCH_U8500 || MACH_U300
530	help
531	  Enables support for NAND Flash chips on the ST Microelectronics
532	  Flexible Static Memory Controller (FSMC)
533
534config MTD_NAND_XWAY
535	bool "Support for NAND on Lantiq XWAY SoC"
536	depends on LANTIQ && SOC_TYPE_XWAY
537	help
538	  Enables support for NAND Flash chips on Lantiq XWAY SoCs. NAND is attached
539	  to the External Bus Unit (EBU).
540
541config MTD_NAND_SUNXI
542	tristate "Support for NAND on Allwinner SoCs"
543	depends on ARCH_SUNXI
544	help
545	  Enables support for NAND Flash chips on Allwinner SoCs.
546
547config MTD_NAND_HISI504
548	tristate "Support for NAND controller on Hisilicon SoC Hip04"
549	depends on ARCH_HISI || COMPILE_TEST
550	depends on HAS_DMA
551	help
552	  Enables support for NAND controller on Hisilicon SoC Hip04.
553
554config MTD_NAND_QCOM
555	tristate "Support for NAND on QCOM SoCs"
556	depends on ARCH_QCOM
557	help
558	  Enables support for NAND flash chips on SoCs containing the EBI2 NAND
559	  controller. This controller is found on IPQ806x SoC.
560
561config MTD_NAND_MTK
562	tristate "Support for NAND controller on MTK SoCs"
563	depends on ARCH_MEDIATEK || COMPILE_TEST
564	depends on HAS_DMA
565	help
566	  Enables support for NAND controller on MTK SoCs.
567	  This controller is found on mt27xx, mt81xx, mt65xx SoCs.
568
569endif # MTD_NAND
570