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