Version:  2.0.40 2.2.26 2.4.37 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17


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

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us