xref: /openbmc/linux/drivers/mtd/nand/Kconfig (revision 4dc7ccf7)
1menuconfig MTD_NAND
2	tristate "NAND Device Support"
3	depends on MTD
4	select MTD_NAND_IDS
5	help
6	  This enables support for accessing all type of NAND flash
7	  devices. For further information see
8	  <http://www.linux-mtd.infradead.org/doc/nand.html>.
9
10if MTD_NAND
11
12config MTD_NAND_VERIFY_WRITE
13	bool "Verify NAND page writes"
14	help
15	  This adds an extra check when data is written to the flash. The
16	  NAND flash device internally checks only bits transitioning
17	  from 1 to 0. There is a rare possibility that even though the
18	  device thinks the write was successful, a bit could have been
19	  flipped accidentally due to device wear or something else.
20
21config MTD_NAND_ECC_SMC
22	bool "NAND ECC Smart Media byte order"
23	default n
24	help
25	  Software ECC according to the Smart Media Specification.
26	  The original Linux implementation had byte 0 and 1 swapped.
27
28config MTD_NAND_MUSEUM_IDS
29	bool "Enable chip ids for obsolete ancient NAND devices"
30	depends on MTD_NAND
31	default n
32	help
33	  Enable this option only when your board has first generation
34	  NAND chips (page size 256 byte, erase size 4-8KiB). The IDs
35	  of these chips were reused by later, larger chips.
36
37config MTD_NAND_AUTCPU12
38	tristate "SmartMediaCard on autronix autcpu12 board"
39	depends on ARCH_AUTCPU12
40	help
41	  This enables the driver for the autronix autcpu12 board to
42	  access the SmartMediaCard.
43
44config MTD_NAND_EDB7312
45	tristate "Support for Cirrus Logic EBD7312 evaluation board"
46	depends on ARCH_EDB7312
47	help
48	  This enables the driver for the Cirrus Logic EBD7312 evaluation
49	  board to access the onboard NAND Flash.
50
51config MTD_NAND_H1900
52	tristate "iPAQ H1900 flash"
53	depends on ARCH_PXA && MTD_PARTITIONS
54	help
55	  This enables the driver for the iPAQ h1900 flash.
56
57config MTD_NAND_GPIO
58	tristate "GPIO NAND Flash driver"
59	depends on GENERIC_GPIO && ARM
60	help
61	  This enables a GPIO based NAND flash driver.
62
63config MTD_NAND_SPIA
64	tristate "NAND Flash device on SPIA board"
65	depends on ARCH_P720T
66	help
67	  If you had to ask, you don't have one. Say 'N'.
68
69config MTD_NAND_AMS_DELTA
70	tristate "NAND Flash device on Amstrad E3"
71	depends on MACH_AMS_DELTA
72	help
73	  Support for NAND flash on Amstrad E3 (Delta).
74
75config MTD_NAND_OMAP2
76	tristate "NAND Flash device on OMAP2 and OMAP3"
77	depends on ARM && MTD_NAND && (ARCH_OMAP2 || ARCH_OMAP3)
78	help
79          Support for NAND flash on Texas Instruments OMAP2 and OMAP3 platforms.
80
81config MTD_NAND_OMAP_PREFETCH
82	bool "GPMC prefetch support for NAND Flash device"
83	depends on MTD_NAND && MTD_NAND_OMAP2
84	default y
85	help
86	 The NAND device can be accessed for Read/Write using GPMC PREFETCH engine
87	 to improve the performance.
88
89config MTD_NAND_OMAP_PREFETCH_DMA
90	depends on MTD_NAND_OMAP_PREFETCH
91	bool "DMA mode"
92	default n
93	help
94	 The GPMC PREFETCH engine can be configured eigther in MPU interrupt mode
95	 or in DMA interrupt mode.
96	 Say y for DMA mode or MPU mode will be used
97
98config MTD_NAND_TS7250
99	tristate "NAND Flash device on TS-7250 board"
100	depends on MACH_TS72XX
101	help
102	  Support for NAND flash on Technologic Systems TS-7250 platform.
103
104config MTD_NAND_IDS
105	tristate
106
107config MTD_NAND_AU1550
108	tristate "Au1550/1200 NAND support"
109	depends on SOC_AU1200 || SOC_AU1550
110	help
111	  This enables the driver for the NAND flash controller on the
112	  AMD/Alchemy 1550 SOC.
113
114config MTD_NAND_BF5XX
115	tristate "Blackfin on-chip NAND Flash Controller driver"
116	depends on (BF54x || BF52x) && MTD_NAND
117	help
118	  This enables the Blackfin on-chip NAND flash controller
119
120	  No board specific support is done by this driver, each board
121	  must advertise a platform_device for the driver to attach.
122
123	  This driver can also be built as a module. If so, the module
124	  will be called bf5xx-nand.
125
126config MTD_NAND_BF5XX_HWECC
127	bool "BF5XX NAND Hardware ECC"
128	default y
129	depends on MTD_NAND_BF5XX
130	help
131	  Enable the use of the BF5XX's internal ECC generator when
132	  using NAND.
133
134config MTD_NAND_BF5XX_BOOTROM_ECC
135	bool "Use Blackfin BootROM ECC Layout"
136	default n
137	depends on MTD_NAND_BF5XX_HWECC
138	help
139	  If you wish to modify NAND pages and allow the Blackfin on-chip
140	  BootROM to boot from them, say Y here.  This is only necessary
141	  if you are booting U-Boot out of NAND and you wish to update
142	  U-Boot from Linux' userspace.  Otherwise, you should say N here.
143
144	  If unsure, say N.
145
146config MTD_NAND_RTC_FROM4
147	tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
148	depends on SH_SOLUTION_ENGINE
149	select REED_SOLOMON
150	select REED_SOLOMON_DEC8
151	select BITREVERSE
152	help
153	  This enables the driver for the Renesas Technology AG-AND
154	  flash interface board (FROM_BOARD4)
155
156config MTD_NAND_PPCHAMELEONEVB
157	tristate "NAND Flash device on PPChameleonEVB board"
158	depends on PPCHAMELEONEVB && BROKEN
159	help
160	  This enables the NAND flash driver on the PPChameleon EVB Board.
161
162config MTD_NAND_S3C2410
163	tristate "NAND Flash support for Samsung S3C SoCs"
164	depends on ARCH_S3C2410 || ARCH_S3C64XX
165	help
166	  This enables the NAND flash controller on the S3C24xx and S3C64xx
167	  SoCs
168
169	  No board specific support is done by this driver, each board
170	  must advertise a platform_device for the driver to attach.
171
172config MTD_NAND_S3C2410_DEBUG
173	bool "Samsung S3C NAND driver debug"
174	depends on MTD_NAND_S3C2410
175	help
176	  Enable debugging of the S3C NAND driver
177
178config MTD_NAND_S3C2410_HWECC
179	bool "Samsung S3C NAND Hardware ECC"
180	depends on MTD_NAND_S3C2410
181	help
182	  Enable the use of the controller's internal ECC generator when
183	  using NAND. Early versions of the chips have had problems with
184	  incorrect ECC generation, and if using these, the default of
185	  software ECC is preferable.
186
187config MTD_NAND_NDFC
188	tristate "NDFC NanD Flash Controller"
189	depends on 4xx
190	select MTD_NAND_ECC_SMC
191	help
192	 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
193
194config MTD_NAND_S3C2410_CLKSTOP
195	bool "Samsung S3C NAND IDLE clock stop"
196	depends on MTD_NAND_S3C2410
197	default n
198	help
199	  Stop the clock to the NAND controller when there is no chip
200	  selected to save power. This will mean there is a small delay
201	  when the is NAND chip selected or released, but will save
202	  approximately 5mA of power when there is nothing happening.
203
204config MTD_NAND_BCM_UMI
205	tristate "NAND Flash support for BCM Reference Boards"
206	depends on ARCH_BCMRING && MTD_NAND
207	help
208	  This enables the NAND flash controller on the BCM UMI block.
209
210	  No board specfic support is done by this driver, each board
211	  must advertise a platform_device for the driver to attach.
212
213config MTD_NAND_BCM_UMI_HWCS
214	bool "BCM UMI NAND Hardware CS"
215	depends on MTD_NAND_BCM_UMI
216	help
217	  Enable the use of the BCM UMI block's internal CS using NAND.
218	  This should only be used if you know the external NAND CS can toggle.
219
220config MTD_NAND_DISKONCHIP
221	tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
222	depends on EXPERIMENTAL
223	select REED_SOLOMON
224	select REED_SOLOMON_DEC16
225	help
226	  This is a reimplementation of M-Systems DiskOnChip 2000,
227	  Millennium and Millennium Plus as a standard NAND device driver,
228	  as opposed to the earlier self-contained MTD device drivers.
229	  This should enable, among other things, proper JFFS2 operation on
230	  these devices.
231
232config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
233        bool "Advanced detection options for DiskOnChip"
234        depends on MTD_NAND_DISKONCHIP
235        help
236          This option allows you to specify nonstandard address at which to
237          probe for a DiskOnChip, or to change the detection options.  You
238          are unlikely to need any of this unless you are using LinuxBIOS.
239          Say 'N'.
240
241config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
242        hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
243        depends on MTD_NAND_DISKONCHIP
244        default "0"
245        ---help---
246        By default, the probe for DiskOnChip devices will look for a
247        DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
248        This option allows you to specify a single address at which to probe
249        for the device, which is useful if you have other devices in that
250        range which get upset when they are probed.
251
252        (Note that on PowerPC, the normal probe will only check at
253        0xE4000000.)
254
255        Normally, you should leave this set to zero, to allow the probe at
256        the normal addresses.
257
258config MTD_NAND_DISKONCHIP_PROBE_HIGH
259        bool "Probe high addresses"
260        depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
261        help
262          By default, the probe for DiskOnChip devices will look for a
263          DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
264          This option changes to make it probe between 0xFFFC8000 and
265          0xFFFEE000.  Unless you are using LinuxBIOS, this is unlikely to be
266          useful to you.  Say 'N'.
267
268config MTD_NAND_DISKONCHIP_BBTWRITE
269	bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
270	depends on MTD_NAND_DISKONCHIP
271	help
272	  On DiskOnChip devices shipped with the INFTL filesystem (Millennium
273	  and 2000 TSOP/Alon), Linux reserves some space at the end of the
274	  device for the Bad Block Table (BBT).  If you have existing INFTL
275	  data on your device (created by non-Linux tools such as M-Systems'
276	  DOS drivers), your data might overlap the area Linux wants to use for
277	  the BBT.  If this is a concern for you, leave this option disabled and
278	  Linux will not write BBT data into this area.
279	  The downside of leaving this option disabled is that if bad blocks
280	  are detected by Linux, they will not be recorded in the BBT, which
281	  could cause future problems.
282	  Once you enable this option, new filesystems (INFTL or others, created
283	  in Linux or other operating systems) will not use the reserved area.
284	  The only reason not to enable this option is to prevent damage to
285	  preexisting filesystems.
286	  Even if you leave this disabled, you can enable BBT writes at module
287	  load time (assuming you build diskonchip as a module) with the module
288	  parameter "inftl_bbt_write=1".
289
290config MTD_NAND_SHARPSL
291	tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
292	depends on ARCH_PXA
293
294config MTD_NAND_CAFE
295	tristate "NAND support for OLPC CAFÉ chip"
296	depends on PCI
297	select REED_SOLOMON
298	select REED_SOLOMON_DEC16
299	help
300	  Use NAND flash attached to the CAFÉ chip designed for the OLPC
301	  laptop.
302
303config MTD_NAND_CS553X
304	tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
305	depends on X86_32
306	help
307	  The CS553x companion chips for the AMD Geode processor
308	  include NAND flash controllers with built-in hardware ECC
309	  capabilities; enabling this option will allow you to use
310	  these. The driver will check the MSRs to verify that the
311	  controller is enabled for NAND, and currently requires that
312	  the controller be in MMIO mode.
313
314	  If you say "m", the module will be called cs553x_nand.
315
316config MTD_NAND_ATMEL
317	tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
318	depends on ARCH_AT91 || AVR32
319	help
320	  Enables support for NAND Flash / Smart Media Card interface
321	  on Atmel AT91 and AVR32 processors.
322choice
323	prompt "ECC management for NAND Flash / SmartMedia on AT91 / AVR32"
324	depends on MTD_NAND_ATMEL
325
326config MTD_NAND_ATMEL_ECC_HW
327	bool "Hardware ECC"
328	depends on ARCH_AT91SAM9263 || ARCH_AT91SAM9260 || AVR32
329	help
330	  Use hardware ECC instead of software ECC when the chip
331	  supports it.
332
333	  The hardware ECC controller is capable of single bit error
334	  correction and 2-bit random detection per page.
335
336	  NB : hardware and software ECC schemes are incompatible.
337	  If you switch from one to another, you'll have to erase your
338	  mtd partition.
339
340	  If unsure, say Y
341
342config MTD_NAND_ATMEL_ECC_SOFT
343	bool "Software ECC"
344	help
345	  Use software ECC.
346
347	  NB : hardware and software ECC schemes are incompatible.
348	  If you switch from one to another, you'll have to erase your
349	  mtd partition.
350
351config MTD_NAND_ATMEL_ECC_NONE
352	bool "No ECC (testing only, DANGEROUS)"
353	depends on DEBUG_KERNEL
354	help
355	  No ECC will be used.
356	  It's not a good idea and it should be reserved for testing
357	  purpose only.
358
359	  If unsure, say N
360
361	  endchoice
362
363endchoice
364
365config MTD_NAND_PXA3xx
366	tristate "Support for NAND flash devices on PXA3xx"
367	depends on MTD_NAND && (PXA3xx || ARCH_MMP)
368	help
369	  This enables the driver for the NAND flash device found on
370	  PXA3xx processors
371
372config MTD_NAND_PXA3xx_BUILTIN
373	bool "Use builtin definitions for some NAND chips (deprecated)"
374	depends on MTD_NAND_PXA3xx
375	help
376	  This enables builtin definitions for some NAND chips. This
377	  is deprecated in favor of platform specific data.
378
379config MTD_NAND_CM_X270
380	tristate "Support for NAND Flash on CM-X270 modules"
381	depends on MTD_NAND && MACH_ARMCORE
382
383config MTD_NAND_PASEMI
384	tristate "NAND support for PA Semi PWRficient"
385	depends on MTD_NAND && PPC_PASEMI
386	help
387	  Enables support for NAND Flash interface on PA Semi PWRficient
388	  based boards
389
390config MTD_NAND_TMIO
391	tristate "NAND Flash device on Toshiba Mobile IO Controller"
392	depends on MTD_NAND && MFD_TMIO
393	help
394	  Support for NAND flash connected to a Toshiba Mobile IO
395	  Controller in some PDAs, including the Sharp SL6000x.
396
397config MTD_NAND_NANDSIM
398	tristate "Support for NAND Flash Simulator"
399	depends on MTD_PARTITIONS
400	help
401	  The simulator may simulate various NAND flash chips for the
402	  MTD nand layer.
403
404config MTD_NAND_PLATFORM
405	tristate "Support for generic platform NAND driver"
406	depends on MTD_NAND
407	help
408	  This implements a generic NAND driver for on-SOC platform
409	  devices. You will need to provide platform-specific functions
410	  via platform_data.
411
412config MTD_ALAUDA
413	tristate "MTD driver for Olympus MAUSB-10 and Fujifilm DPC-R1"
414	depends on MTD_NAND && USB
415	help
416	  These two (and possibly other) Alauda-based cardreaders for
417	  SmartMedia and xD allow raw flash access.
418
419config MTD_NAND_ORION
420	tristate "NAND Flash support for Marvell Orion SoC"
421	depends on PLAT_ORION && MTD_NAND
422	help
423	  This enables the NAND flash controller on Orion machines.
424
425	  No board specific support is done by this driver, each board
426	  must advertise a platform_device for the driver to attach.
427
428config MTD_NAND_FSL_ELBC
429	tristate "NAND support for Freescale eLBC controllers"
430	depends on MTD_NAND && PPC_OF
431	help
432	  Various Freescale chips, including the 8313, include a NAND Flash
433	  Controller Module with built-in hardware ECC capabilities.
434	  Enabling this option will enable you to use this to control
435	  external NAND devices.
436
437config MTD_NAND_FSL_UPM
438	tristate "Support for NAND on Freescale UPM"
439	depends on MTD_NAND && (PPC_83xx || PPC_85xx)
440	select FSL_LBC
441	help
442	  Enables support for NAND Flash chips wired onto Freescale PowerPC
443	  processor localbus with User-Programmable Machine support.
444
445config MTD_NAND_MXC
446	tristate "MXC NAND support"
447	depends on ARCH_MX2 || ARCH_MX25 || ARCH_MX3
448	help
449	  This enables the driver for the NAND flash controller on the
450	  MXC processors.
451
452config MTD_NAND_NOMADIK
453	tristate "ST Nomadik 8815 NAND support"
454	depends on ARCH_NOMADIK
455	help
456	  Driver for the NAND flash controller on the Nomadik, with ECC.
457
458config MTD_NAND_SH_FLCTL
459	tristate "Support for NAND on Renesas SuperH FLCTL"
460	depends on MTD_NAND && (SUPERH || ARCH_SHMOBILE)
461	help
462	  Several Renesas SuperH CPU has FLCTL. This option enables support
463	  for NAND Flash using FLCTL.
464
465config MTD_NAND_DAVINCI
466        tristate "Support NAND on DaVinci SoC"
467        depends on ARCH_DAVINCI
468        help
469	  Enable the driver for NAND flash chips on Texas Instruments
470	  DaVinci processors.
471
472config MTD_NAND_TXX9NDFMC
473	tristate "NAND Flash support for TXx9 SoC"
474	depends on SOC_TX4938 || SOC_TX4939
475	help
476	  This enables the NAND flash controller on the TXx9 SoCs.
477
478config MTD_NAND_SOCRATES
479	tristate "Support for NAND on Socrates board"
480	depends on MTD_NAND && SOCRATES
481	help
482	  Enables support for NAND Flash chips wired onto Socrates board.
483
484config MTD_NAND_W90P910
485	tristate "Support for NAND on w90p910 evaluation board."
486	depends on ARCH_W90X900 && MTD_PARTITIONS
487	help
488	  This enables the driver for the NAND Flash on evaluation board based
489	  on w90p910.
490
491endif # MTD_NAND
492