1 # drivers/mtd/nand/Kconfig
2 # $Id: Kconfig,v 1.35 2005/11/07 11:14:30 gleixner Exp $
5 tristate "NAND Device Support"
9 This enables support for accessing all type of NAND flash
10 devices. For further information see
11 <http://www.linux-mtd.infradead.org/doc/nand.html>.
15 config MTD_NAND_VERIFY_WRITE
16 bool "Verify NAND page writes"
18 This adds an extra check when data is written to the flash. The
19 NAND flash device internally checks only bits transitioning
20 from 1 to 0. There is a rare possibility that even though the
21 device thinks the write was successful, a bit could have been
22 flipped accidentally due to device wear or something else.
24 config MTD_NAND_ECC_SMC
25 bool "NAND ECC Smart Media byte order"
28 Software ECC according to the Smart Media Specification.
29 The original Linux implementation had byte 0 and 1 swapped.
31 config MTD_NAND_MUSEUM_IDS
32 bool "Enable chip ids for obsolete ancient NAND devices"
36 Enable this option only when your board has first generation
37 NAND chips (page size 256 byte, erase size 4-8KiB). The IDs
38 of these chips were reused by later, larger chips.
40 config MTD_NAND_AUTCPU12
41 tristate "SmartMediaCard on autronix autcpu12 board"
42 depends on ARCH_AUTCPU12
44 This enables the driver for the autronix autcpu12 board to
45 access the SmartMediaCard.
47 config MTD_NAND_EDB7312
48 tristate "Support for Cirrus Logic EBD7312 evaluation board"
49 depends on ARCH_EDB7312
51 This enables the driver for the Cirrus Logic EBD7312 evaluation
52 board to access the onboard NAND Flash.
55 tristate "iPAQ H1900 flash"
56 depends on ARCH_PXA && MTD_PARTITIONS
58 This enables the driver for the iPAQ h1900 flash.
61 tristate "NAND Flash device on SPIA board"
64 If you had to ask, you don't have one. Say 'N'.
66 config MTD_NAND_AMS_DELTA
67 tristate "NAND Flash device on Amstrad E3"
68 depends on MACH_AMS_DELTA
70 Support for NAND flash on Amstrad E3 (Delta).
73 tristate "NAND Flash device on OMAP 2420H4/2430SDP boards"
74 depends on (ARM && ARCH_OMAP2 && MTD_NAND)
76 Support for NAND flash on Texas Instruments 2430SDP/2420H4 platforms.
79 tristate "NAND Flash device on OMAP H3/H2/P2 boards"
80 depends on ARM && ARCH_OMAP1 && MTD_NAND && (MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_PERSEUS2)
82 Support for NAND flash on Texas Instruments H3/H2/P2 platforms.
84 config MTD_NAND_OMAP_HW
85 bool "OMAP HW NAND Flash controller support"
86 depends on ARM && ARCH_OMAP16XX && MTD_NAND
89 Driver for TI OMAP16xx hardware NAND flash controller.
92 tristate "NAND Flash device on TOTO board"
93 depends on ARCH_OMAP && BROKEN
95 Support for NAND flash on Texas Instruments Toto platform.
97 config MTD_NAND_TS7250
98 tristate "NAND Flash device on TS-7250 board"
99 depends on MACH_TS72XX
101 Support for NAND flash on Technologic Systems TS-7250 platform.
106 config MTD_NAND_AU1550
107 tristate "Au1550/1200 NAND support"
108 depends on SOC_AU1200 || SOC_AU1550
110 This enables the driver for the NAND flash controller on the
111 AMD/Alchemy 1550 SOC.
113 config MTD_NAND_BF5XX
114 tristate "Blackfin on-chip NAND Flash Controller driver"
115 depends on (BF54x || BF52x) && MTD_NAND
117 This enables the Blackfin on-chip NAND flash controller
119 No board specific support is done by this driver, each board
120 must advertise a platform_device for the driver to attach.
122 This driver can also be built as a module. If so, the module
123 will be called bf5xx-nand.
125 config MTD_NAND_BF5XX_HWECC
126 bool "BF5XX NAND Hardware ECC"
127 depends on MTD_NAND_BF5XX
129 Enable the use of the BF5XX's internal ECC generator when
132 config MTD_NAND_RTC_FROM4
133 tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)"
134 depends on SH_SOLUTION_ENGINE
136 select REED_SOLOMON_DEC8
139 This enables the driver for the Renesas Technology AG-AND
140 flash interface board (FROM_BOARD4)
142 config MTD_NAND_PPCHAMELEONEVB
143 tristate "NAND Flash device on PPChameleonEVB board"
144 depends on PPCHAMELEONEVB && BROKEN
146 This enables the NAND flash driver on the PPChameleon EVB Board.
148 config MTD_NAND_S3C2410
149 tristate "NAND Flash support for S3C2410/S3C2440 SoC"
150 depends on ARCH_S3C2410
152 This enables the NAND flash controller on the S3C2410 and S3C2440
155 No board specific support is done by this driver, each board
156 must advertise a platform_device for the driver to attach.
158 config MTD_NAND_S3C2410_DEBUG
159 bool "S3C2410 NAND driver debug"
160 depends on MTD_NAND_S3C2410
162 Enable debugging of the S3C2410 NAND driver
164 config MTD_NAND_S3C2410_HWECC
165 bool "S3C2410 NAND Hardware ECC"
166 depends on MTD_NAND_S3C2410
168 Enable the use of the S3C2410's internal ECC generator when
169 using NAND. Early versions of the chip have had problems with
170 incorrect ECC generation, and if using these, the default of
171 software ECC is preferable.
174 tristate "NDFC NanD Flash Controller"
175 depends on 4xx && !PPC_MERGE
176 select MTD_NAND_ECC_SMC
178 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
180 config MTD_NAND_S3C2410_CLKSTOP
181 bool "S3C2410 NAND IDLE clock stop"
182 depends on MTD_NAND_S3C2410
185 Stop the clock to the NAND controller when there is no chip
186 selected to save power. This will mean there is a small delay
187 when the is NAND chip selected or released, but will save
188 approximately 5mA of power when there is nothing happening.
190 config MTD_NAND_DISKONCHIP
191 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)"
192 depends on EXPERIMENTAL
194 select REED_SOLOMON_DEC16
196 This is a reimplementation of M-Systems DiskOnChip 2000,
197 Millennium and Millennium Plus as a standard NAND device driver,
198 as opposed to the earlier self-contained MTD device drivers.
199 This should enable, among other things, proper JFFS2 operation on
202 config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
203 bool "Advanced detection options for DiskOnChip"
204 depends on MTD_NAND_DISKONCHIP
206 This option allows you to specify nonstandard address at which to
207 probe for a DiskOnChip, or to change the detection options. You
208 are unlikely to need any of this unless you are using LinuxBIOS.
211 config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
212 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
213 depends on MTD_NAND_DISKONCHIP
216 By default, the probe for DiskOnChip devices will look for a
217 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
218 This option allows you to specify a single address at which to probe
219 for the device, which is useful if you have other devices in that
220 range which get upset when they are probed.
222 (Note that on PowerPC, the normal probe will only check at
225 Normally, you should leave this set to zero, to allow the probe at
226 the normal addresses.
228 config MTD_NAND_DISKONCHIP_PROBE_HIGH
229 bool "Probe high addresses"
230 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
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 changes to make it probe between 0xFFFC8000 and
235 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
236 useful to you. Say 'N'.
238 config MTD_NAND_DISKONCHIP_BBTWRITE
239 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
240 depends on MTD_NAND_DISKONCHIP
242 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
243 and 2000 TSOP/Alon), Linux reserves some space at the end of the
244 device for the Bad Block Table (BBT). If you have existing INFTL
245 data on your device (created by non-Linux tools such as M-Systems'
246 DOS drivers), your data might overlap the area Linux wants to use for
247 the BBT. If this is a concern for you, leave this option disabled and
248 Linux will not write BBT data into this area.
249 The downside of leaving this option disabled is that if bad blocks
250 are detected by Linux, they will not be recorded in the BBT, which
251 could cause future problems.
252 Once you enable this option, new filesystems (INFTL or others, created
253 in Linux or other operating systems) will not use the reserved area.
254 The only reason not to enable this option is to prevent damage to
255 preexisting filesystems.
256 Even if you leave this disabled, you can enable BBT writes at module
257 load time (assuming you build diskonchip as a module) with the module
258 parameter "inftl_bbt_write=1".
260 config MTD_NAND_SHARPSL
261 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
264 config MTD_NAND_BASLER_EXCITE
265 tristate "Support for NAND Flash on Basler eXcite"
266 depends on BASLER_EXCITE
268 This enables the driver for the NAND flash device found on the
269 Basler eXcite Smart Camera. If built as a module, the driver
270 will be named "excite_nandflash.ko".
273 tristate "NAND support for OLPC CAFÉ chip"
276 select REED_SOLOMON_DEC16
278 Use NAND flash attached to the CAFÉ chip designed for the OLPC
281 config MTD_NAND_CS553X
282 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
283 depends on X86_32 && (X86_PC || X86_GENERICARCH)
285 The CS553x companion chips for the AMD Geode processor
286 include NAND flash controllers with built-in hardware ECC
287 capabilities; enabling this option will allow you to use
288 these. The driver will check the MSRs to verify that the
289 controller is enabled for NAND, and currently requires that
290 the controller be in MMIO mode.
292 If you say "m", the module will be called "cs553x_nand.ko".
295 bool "Support for NAND Flash / SmartMedia on AT91"
298 Enables support for NAND Flash / Smart Media Card interface
299 on Atmel AT91 processors.
301 config MTD_NAND_CM_X270
302 tristate "Support for NAND Flash on CM-X270 modules"
303 depends on MTD_NAND && MACH_ARMCORE
305 config MTD_NAND_PASEMI
306 tristate "NAND support for PA Semi PWRficient"
307 depends on MTD_NAND && PPC_PASEMI
309 Enables support for NAND Flash interface on PA Semi PWRficient
312 config MTD_NAND_NANDSIM
313 tristate "Support for NAND Flash Simulator"
314 depends on MTD_PARTITIONS
316 The simulator may simulate various NAND flash chips for the
319 config MTD_NAND_PLATFORM
320 tristate "Support for generic platform NAND driver"
323 This implements a generic NAND driver for on-SOC platform
324 devices. You will need to provide platform-specific functions
328 tristate "MTD driver for Olympus MAUSB-10 and Fujifilm DPC-R1"
329 depends on MTD_NAND && USB
331 These two (and possibly other) Alauda-based cardreaders for
332 SmartMedia and xD allow raw flash access.
334 config MTD_NAND_ORION
335 tristate "NAND Flash support for Marvell Orion SoC"
336 depends on PLAT_ORION && MTD_NAND
338 This enables the NAND flash controller on Orion machines.
340 No board specific support is done by this driver, each board
341 must advertise a platform_device for the driver to attach.
343 config MTD_NAND_FSL_ELBC
344 tristate "NAND support for Freescale eLBC controllers"
345 depends on MTD_NAND && PPC_OF
347 Various Freescale chips, including the 8313, include a NAND Flash
348 Controller Module with built-in hardware ECC capabilities.
349 Enabling this option will enable you to use this to control
350 external NAND devices.