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