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