mtd: nand: add tango NAND flash controller support
[linux-2.6-block.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
193bd400
ID
25config MTD_NAND_BCH
26 tristate
27 select BCH
28 depends on MTD_NAND_ECC_BCH
29 default MTD_NAND
30
31config 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.
1da177e4 39
9fc51a37 40config MTD_SM_COMMON
9fc51a37
ML
41 tristate
42 default n
43
ce082596 44config MTD_NAND_DENALI
04868a67 45 tristate
2a0a288e
DN
46
47config MTD_NAND_DENALI_PCI
ce082596 48 tristate "Support Denali NAND controller on Intel Moorestown"
04868a67
AS
49 select MTD_NAND_DENALI
50 depends on HAS_DMA && PCI
ce082596
JR
51 help
52 Enable the driver for NAND flash on Intel Moorestown, using the
53 Denali NAND controller core.
30f9f2fb
DN
54
55config MTD_NAND_DENALI_DT
56 tristate "Support Denali NAND controller as a DT device"
04868a67 57 select MTD_NAND_DENALI
0ed6ca3a 58 depends on HAS_DMA && HAVE_CLK && OF
30f9f2fb
DN
59 help
60 Enable the driver for NAND flash on platforms using a Denali NAND
61 controller as a DT device.
62
ce082596
JR
63config MTD_NAND_DENALI_SCRATCH_REG_ADDR
64 hex "Denali NAND size scratch register address"
65 default "0xFF108018"
2a0a288e 66 depends on MTD_NAND_DENALI_PCI
ce082596
JR
67 help
68 Some platforms place the NAND chip size in a scratch register
69 because (some versions of) the driver aren't able to automatically
70 determine the size of certain chips. Set the address of the
71 scratch register here to enable this feature. On Intel Moorestown
72 boards, the scratch register is at 0xFF108018.
73
aaf7ea20 74config MTD_NAND_GPIO
c9d79c4b 75 tristate "GPIO assisted NAND Flash driver"
f650ce24 76 depends on GPIOLIB || COMPILE_TEST
15c0be7b 77 depends on HAS_IOMEM
aaf7ea20 78 help
c9d79c4b
GS
79 This enables a NAND flash driver where control signals are
80 connected to GPIO pins, and commands and data are communicated
81 via a memory mapped interface.
aaf7ea20 82
3d12c0c7
JM
83config MTD_NAND_AMS_DELTA
84 tristate "NAND Flash device on Amstrad E3"
ec98c681 85 depends on MACH_AMS_DELTA
494f45d5 86 default y
3d12c0c7
JM
87 help
88 Support for NAND flash on Amstrad E3 (Delta).
89
67ce04bf 90config MTD_NAND_OMAP2
e13f880b
RQ
91 tristate "NAND Flash device on OMAP2, OMAP3, OMAP4 and Keystone"
92 depends on (ARCH_OMAP2PLUS || ARCH_KEYSTONE)
67ce04bf 93 help
e13f880b
RQ
94 Support for NAND flash on Texas Instruments OMAP2, OMAP3, OMAP4
95 and Keystone platforms.
67ce04bf 96
0e618ef0 97config MTD_NAND_OMAP_BCH
43b77693 98 depends on MTD_NAND_OMAP2
e7cd6824 99 bool "Support hardware based BCH error correction"
0e618ef0
ID
100 default n
101 select BCH
0e618ef0 102 help
90c9c955
PG
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
8b3d58e5 107 so this is optional for them.
0e618ef0 108
e7cd6824
EG
109config MTD_NAND_OMAP_BCH_BUILD
110 def_tristate MTD_NAND_OMAP2 && MTD_NAND_OMAP_BCH
111
1da177e4
LT
112config MTD_NAND_IDS
113 tristate
114
67e054e9
ML
115config MTD_NAND_RICOH
116 tristate "Ricoh xD card reader"
117 default n
f696aa43 118 depends on PCI
67e054e9
ML
119 select MTD_SM_COMMON
120 help
121 Enable support for Ricoh R5C852 xD card reader
122 You also need to enable ether
123 NAND SSFDC (SmartMedia) read only translation layer' or new
124 expermental, readwrite
125 'SmartMedia/xD new translation layer'
126
1da177e4 127config MTD_NAND_AU1550
ef6f0d1f 128 tristate "Au1550/1200 NAND support"
37663860 129 depends on MIPS_ALCHEMY
1da177e4
LT
130 help
131 This enables the driver for the NAND flash controller on the
132 AMD/Alchemy 1550 SOC.
133
b37bde14
BW
134config MTD_NAND_BF5XX
135 tristate "Blackfin on-chip NAND Flash Controller driver"
8c1a1158 136 depends on BF54x || BF52x
b37bde14
BW
137 help
138 This enables the Blackfin on-chip NAND flash controller
139
140 No board specific support is done by this driver, each board
141 must advertise a platform_device for the driver to attach.
142
143 This driver can also be built as a module. If so, the module
144 will be called bf5xx-nand.
145
146config MTD_NAND_BF5XX_HWECC
147 bool "BF5XX NAND Hardware ECC"
a0dd2018 148 default y
b37bde14
BW
149 depends on MTD_NAND_BF5XX
150 help
151 Enable the use of the BF5XX's internal ECC generator when
152 using NAND.
153
fcb90ba7
MF
154config MTD_NAND_BF5XX_BOOTROM_ECC
155 bool "Use Blackfin BootROM ECC Layout"
156 default n
157 depends on MTD_NAND_BF5XX_HWECC
158 help
159 If you wish to modify NAND pages and allow the Blackfin on-chip
160 BootROM to boot from them, say Y here. This is only necessary
161 if you are booting U-Boot out of NAND and you wish to update
162 U-Boot from Linux' userspace. Otherwise, you should say N here.
163
164 If unsure, say N.
165
1da177e4 166config MTD_NAND_S3C2410
9dbc0902 167 tristate "NAND Flash support for Samsung S3C SoCs"
b130d5c2 168 depends on ARCH_S3C24XX || ARCH_S3C64XX
1da177e4 169 help
9dbc0902 170 This enables the NAND flash controller on the S3C24xx and S3C64xx
a4f957f1 171 SoCs
1da177e4 172
4992a9e8 173 No board specific support is done by this driver, each board
61b03bd7 174 must advertise a platform_device for the driver to attach.
1da177e4
LT
175
176config MTD_NAND_S3C2410_DEBUG
9dbc0902 177 bool "Samsung S3C NAND driver debug"
1da177e4
LT
178 depends on MTD_NAND_S3C2410
179 help
9dbc0902 180 Enable debugging of the S3C NAND driver
1da177e4 181
a808ad3b
SM
182config MTD_NAND_NDFC
183 tristate "NDFC NanD Flash Controller"
184 depends on 4xx
185 select MTD_NAND_ECC_SMC
186 help
187 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
188
d1fef3c5 189config MTD_NAND_S3C2410_CLKSTOP
9dbc0902 190 bool "Samsung S3C NAND IDLE clock stop"
d1fef3c5
BD
191 depends on MTD_NAND_S3C2410
192 default n
193 help
194 Stop the clock to the NAND controller when there is no chip
195 selected to save power. This will mean there is a small delay
196 when the is NAND chip selected or released, but will save
197 approximately 5mA of power when there is nothing happening.
198
6956e238
MG
199config MTD_NAND_TANGO
200 tristate "NAND Flash support for Tango chips"
201 depends on ARCH_TANGO || COMPILE_TEST
202 depends on HAS_DMA
203 help
204 Enables the NAND Flash controller on Tango chips.
205
1da177e4 206config MTD_NAND_DISKONCHIP
5d0e137d 207 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation)"
9310da0b 208 depends on HAS_IOMEM
1da177e4
LT
209 select REED_SOLOMON
210 select REED_SOLOMON_DEC16
211 help
212 This is a reimplementation of M-Systems DiskOnChip 2000,
213 Millennium and Millennium Plus as a standard NAND device driver,
214 as opposed to the earlier self-contained MTD device drivers.
215 This should enable, among other things, proper JFFS2 operation on
216 these devices.
217
218config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
219 bool "Advanced detection options for DiskOnChip"
220 depends on MTD_NAND_DISKONCHIP
221 help
222 This option allows you to specify nonstandard address at which to
223 probe for a DiskOnChip, or to change the detection options. You
224 are unlikely to need any of this unless you are using LinuxBIOS.
225 Say 'N'.
226
227config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
228 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
229 depends on MTD_NAND_DISKONCHIP
230 default "0"
231 ---help---
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 allows you to specify a single address at which to probe
235 for the device, which is useful if you have other devices in that
236 range which get upset when they are probed.
237
238 (Note that on PowerPC, the normal probe will only check at
239 0xE4000000.)
240
241 Normally, you should leave this set to zero, to allow the probe at
242 the normal addresses.
243
244config MTD_NAND_DISKONCHIP_PROBE_HIGH
245 bool "Probe high addresses"
246 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
247 help
248 By default, the probe for DiskOnChip devices will look for a
249 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
250 This option changes to make it probe between 0xFFFC8000 and
251 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
252 useful to you. Say 'N'.
253
254config MTD_NAND_DISKONCHIP_BBTWRITE
255 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
256 depends on MTD_NAND_DISKONCHIP
257 help
258 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
259 and 2000 TSOP/Alon), Linux reserves some space at the end of the
260 device for the Bad Block Table (BBT). If you have existing INFTL
261 data on your device (created by non-Linux tools such as M-Systems'
262 DOS drivers), your data might overlap the area Linux wants to use for
263 the BBT. If this is a concern for you, leave this option disabled and
264 Linux will not write BBT data into this area.
265 The downside of leaving this option disabled is that if bad blocks
266 are detected by Linux, they will not be recorded in the BBT, which
267 could cause future problems.
268 Once you enable this option, new filesystems (INFTL or others, created
269 in Linux or other operating systems) will not use the reserved area.
270 The only reason not to enable this option is to prevent damage to
271 preexisting filesystems.
272 Even if you leave this disabled, you can enable BBT writes at module
273 load time (assuming you build diskonchip as a module) with the module
274 parameter "inftl_bbt_write=1".
1da177e4 275
570469f3 276config MTD_NAND_DOCG4
5d0e137d
KC
277 tristate "Support for DiskOnChip G4"
278 depends on HAS_IOMEM
570469f3
MD
279 select BCH
280 select BITREVERSE
281 help
282 Support for diskonchip G4 nand flash, found in various smartphones and
283 PDAs, among them the Palm Treo680, HTC Prophet and Wizard, Toshiba
284 Portege G900, Asus P526, and O2 XDA Zinc.
285
286 With this driver you will be able to use UBI and create a ubifs on the
287 device, so you may wish to consider enabling UBI and UBIFS as well.
288
289 These devices ship with the Mys/Sandisk SAFTL formatting, for which
290 there is currently no mtd parser, so you may want to use command line
291 partitioning to segregate write-protected blocks. On the Treo680, the
292 first five erase blocks (256KiB each) are write-protected, followed
293 by the block containing the saftl partition table. This is probably
294 typical.
295
54af6b46
AB
296config MTD_NAND_SHARPSL
297 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
ec98c681 298 depends on ARCH_PXA
54af6b46 299
c45aa055 300config MTD_NAND_CAFE
8c61b7a7
SB
301 tristate "NAND support for OLPC CAFÉ chip"
302 depends on PCI
303 select REED_SOLOMON
304 select REED_SOLOMON_DEC16
305 help
8f46c527 306 Use NAND flash attached to the CAFÉ chip designed for the OLPC
8c61b7a7 307 laptop.
c45aa055 308
179fdc3f
DW
309config MTD_NAND_CS553X
310 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
4272ebfb 311 depends on X86_32
02c3b0bd 312 depends on !UML && HAS_IOMEM
f41a5f80
DW
313 help
314 The CS553x companion chips for the AMD Geode processor
315 include NAND flash controllers with built-in hardware ECC
316 capabilities; enabling this option will allow you to use
317 these. The driver will check the MSRs to verify that the
318 controller is enabled for NAND, and currently requires that
319 the controller be in MMIO mode.
320
4737f097 321 If you say "m", the module will be called cs553x_nand.
f41a5f80 322
d4f4c0aa 323config MTD_NAND_ATMEL
bd5a4382 324 tristate "Support for NAND Flash / SmartMedia on AT91 and AVR32"
984290de 325 depends on ARCH_AT91 || AVR32
42cb1403
AV
326 help
327 Enables support for NAND Flash / Smart Media Card interface
984290de 328 on Atmel AT91 and AVR32 processors.
42cb1403 329
fe69af00 330config MTD_NAND_PXA3xx
c5f99677 331 tristate "NAND support on PXA3xx and Armada 370/XP"
0d58f6ee 332 depends on PXA3xx || ARCH_MMP || PLAT_ORION
fe69af00 333 help
334 This enables the driver for the NAND flash device found on
c5f99677 335 PXA3xx processors (NFCv1) and also on Armada 370/XP (NFCv2).
fe69af00 336
2944a44d
RS
337config MTD_NAND_SLC_LPC32XX
338 tristate "NXP LPC32xx SLC Controller"
339 depends on ARCH_LPC32XX
340 help
341 Enables support for NXP's LPC32XX SLC (i.e. for Single Level Cell
342 chips) NAND controller. This is the default for the PHYTEC 3250
343 reference board which contains a NAND256R3A2CZA6 chip.
344
345 Please check the actual NAND chip connected and its support
346 by the SLC NAND controller.
347
70f7cb78
RS
348config MTD_NAND_MLC_LPC32XX
349 tristate "NXP LPC32xx MLC Controller"
350 depends on ARCH_LPC32XX
351 help
352 Uses the LPC32XX MLC (i.e. for Multi Level Cell chips) NAND
353 controller. This is the default for the WORK92105 controller
354 board.
355
356 Please check the actual NAND chip connected and its support
357 by the MLC NAND controller.
358
54d33c4c
MR
359config MTD_NAND_CM_X270
360 tristate "Support for NAND Flash on CM-X270 modules"
8c1a1158 361 depends on MACH_ARMCORE
54d33c4c 362
846fc31d
EM
363config MTD_NAND_PASEMI
364 tristate "NAND support for PA Semi PWRficient"
8c1a1158 365 depends on PPC_PASEMI
846fc31d
EM
366 help
367 Enables support for NAND Flash interface on PA Semi PWRficient
368 based boards
54d33c4c 369
ec43b816
IM
370config MTD_NAND_TMIO
371 tristate "NAND Flash device on Toshiba Mobile IO Controller"
8c1a1158 372 depends on MFD_TMIO
ec43b816
IM
373 help
374 Support for NAND flash connected to a Toshiba Mobile IO
375 Controller in some PDAs, including the Sharp SL6000x.
376
54af6b46
AB
377config MTD_NAND_NANDSIM
378 tristate "Support for NAND Flash Simulator"
1da177e4 379 help
f41a5f80 380 The simulator may simulate various NAND flash chips for the
1da177e4 381 MTD nand layer.
54af6b46 382
157550ff 383config MTD_NAND_GPMI_NAND
e1f5b3f6 384 tristate "GPMI NAND Flash Controller driver"
a3349377 385 depends on MTD_NAND && MXS_DMA
157550ff 386 help
27c84fa5 387 Enables NAND Flash support for IMX23, IMX28 or IMX6.
157550ff
HS
388 The GPMI controller is very powerful, with the help of BCH
389 module, it can do the hardware ECC. The GPMI supports several
390 NAND flashs at the same time. The GPMI may conflicts with other
391 block, such as SD card. So pay attention to it when you enable
392 the GPMI.
393
27c5b17c
BN
394config MTD_NAND_BRCMNAND
395 tristate "Broadcom STB NAND controller"
ebdee13a 396 depends on ARM || ARM64 || MIPS
27c5b17c
BN
397 help
398 Enables the Broadcom NAND controller driver. The controller was
399 originally designed for Set-Top Box but is used on various BCM7xxx,
400 BCM3xxx, BCM63xxx, iProc/Cygnus and more.
401
a5401370 402config MTD_NAND_BCM47XXNFLASH
ecfe57b7 403 tristate "Support for NAND flash on BCM4706 BCMA bus"
a5401370
RM
404 depends on BCMA_NFLASH
405 help
406 BCMA bus can have various flash memories attached, they are
407 registered by bcma as platform devices. This enables driver for
ecfe57b7 408 NAND flash memories. For now only BCM4706 is supported.
a5401370 409
711fdf62
VW
410config MTD_NAND_PLATFORM
411 tristate "Support for generic platform NAND driver"
9310da0b 412 depends on HAS_IOMEM
711fdf62
VW
413 help
414 This implements a generic NAND driver for on-SOC platform
415 devices. You will need to provide platform-specific functions
416 via platform_data.
417
2a1dba29
TP
418config MTD_NAND_ORION
419 tristate "NAND Flash support for Marvell Orion SoC"
8c1a1158 420 depends on PLAT_ORION
2a1dba29
TP
421 help
422 This enables the NAND flash controller on Orion machines.
423
424 No board specific support is done by this driver, each board
425 must advertise a platform_device for the driver to attach.
426
66859249
NA
427config MTD_NAND_OXNAS
428 tristate "NAND Flash support for Oxford Semiconductor SoC"
429 help
430 This enables the NAND flash controller on Oxford Semiconductor SoCs.
431
76b10467
SW
432config MTD_NAND_FSL_ELBC
433 tristate "NAND support for Freescale eLBC controllers"
107896c5 434 depends on FSL_SOC
3ab8f2a2 435 select FSL_LBC
76b10467
SW
436 help
437 Various Freescale chips, including the 8313, include a NAND Flash
438 Controller Module with built-in hardware ECC capabilities.
439 Enabling this option will enable you to use this to control
440 external NAND devices.
441
82771882
PK
442config MTD_NAND_FSL_IFC
443 tristate "NAND support for Freescale IFC controller"
75c19e58 444 depends on FSL_SOC || ARCH_LAYERSCAPE
82771882 445 select FSL_IFC
42d87b18 446 select MEMORY
82771882
PK
447 help
448 Various Freescale chips e.g P1010, include a NAND Flash machine
449 with built-in hardware ECC capabilities.
450 Enabling this option will enable you to use this to control
451 external NAND devices.
452
5c249c5a
AV
453config MTD_NAND_FSL_UPM
454 tristate "Support for NAND on Freescale UPM"
8c1a1158 455 depends on PPC_83xx || PPC_85xx
5c249c5a
AV
456 select FSL_LBC
457 help
458 Enables support for NAND Flash chips wired onto Freescale PowerPC
459 processor localbus with User-Programmable Machine support.
460
bb315f74
AG
461config MTD_NAND_MPC5121_NFC
462 tristate "MPC5121 built-in NAND Flash Controller support"
463 depends on PPC_MPC512x
464 help
465 This enables the driver for the NAND flash controller on the
466 MPC5121 SoC.
467
456930d8
SA
468config MTD_NAND_VF610_NFC
469 tristate "Support for Freescale NFC for VF610/MPC5125"
470 depends on (SOC_VF610 || COMPILE_TEST)
15c0be7b 471 depends on HAS_IOMEM
456930d8
SA
472 help
473 Enables support for NAND Flash Controller on some Freescale
474 processors like the VF610, MPC5125, MCF54418 or Kinetis K70.
049f4250
SA
475 The driver supports a maximum 2k page size. With 2k pages and
476 64 bytes or more of OOB, hardware ECC with up to 32-bit error
477 correction is supported. Hardware ECC is only enabled through
478 device tree.
456930d8 479
34f6e157
SH
480config MTD_NAND_MXC
481 tristate "MXC NAND support"
4d363b55 482 depends on ARCH_MXC
34f6e157
SH
483 help
484 This enables the driver for the NAND flash controller on the
485 MXC processors.
486
6028aa01
YS
487config MTD_NAND_SH_FLCTL
488 tristate "Support for NAND on Renesas SuperH FLCTL"
d5c56201 489 depends on SUPERH || COMPILE_TEST
3d44dc23
RW
490 depends on HAS_IOMEM
491 depends on HAS_DMA
6028aa01
YS
492 help
493 Several Renesas SuperH CPU has FLCTL. This option enables support
b79c7adf 494 for NAND Flash using FLCTL.
6028aa01 495
ff4569c7 496config MTD_NAND_DAVINCI
458f3933
IK
497 tristate "Support NAND on DaVinci/Keystone SoC"
498 depends on ARCH_DAVINCI || (ARCH_KEYSTONE && TI_AEMIF)
ff4569c7
DB
499 help
500 Enable the driver for NAND flash chips on Texas Instruments
458f3933 501 DaVinci/Keystone processors.
ff4569c7 502
64fb65ba
AN
503config MTD_NAND_TXX9NDFMC
504 tristate "NAND Flash support for TXx9 SoC"
505 depends on SOC_TX4938 || SOC_TX4939
506 help
507 This enables the NAND flash controller on the TXx9 SoCs.
508
1b578193
WG
509config MTD_NAND_SOCRATES
510 tristate "Support for NAND on Socrates board"
8c1a1158 511 depends on SOCRATES
1b578193
WG
512 help
513 Enables support for NAND Flash chips wired onto Socrates board.
514
bb6a7755
DW
515config MTD_NAND_NUC900
516 tristate "Support for NAND on Nuvoton NUC9xx/w90p910 evaluation boards."
6a8a98b2 517 depends on ARCH_W90X900
8bff82cb
WZ
518 help
519 This enables the driver for the NAND Flash on evaluation board based
bb6a7755 520 on w90p910 / NUC9xx.
8bff82cb 521
ba01d6ec
LPC
522config MTD_NAND_JZ4740
523 tristate "Support for JZ4740 SoC NAND controller"
524 depends on MACH_JZ4740
525 help
526 Enables support for NAND Flash on JZ4740 SoC based boards.
527
ae02ab00
AS
528config MTD_NAND_JZ4780
529 tristate "Support for NAND on JZ4780 SoC"
530 depends on MACH_JZ4780 && JZ4780_NEMC
531 help
532 Enables support for NAND Flash connected to the NEMC on JZ4780 SoC
533 based boards, using the BCH controller for hardware error correction.
534
6c009ab8
LW
535config MTD_NAND_FSMC
536 tristate "Support for NAND on ST Micros FSMC"
694e33a7 537 depends on PLAT_SPEAR || ARCH_NOMADIK || ARCH_U8500 || MACH_U300
6c009ab8
LW
538 help
539 Enables support for NAND Flash chips on the ST Microelectronics
540 Flexible Static Memory Controller (FSMC)
541
99f2b107
JC
542config MTD_NAND_XWAY
543 tristate "Support for NAND on Lantiq XWAY SoC"
544 depends on LANTIQ && SOC_TYPE_XWAY
99f2b107
JC
545 help
546 Enables support for NAND Flash chips on Lantiq XWAY SoCs. NAND is attached
547 to the External Bus Unit (EBU).
548
1fef62c1
BB
549config MTD_NAND_SUNXI
550 tristate "Support for NAND on Allwinner SoCs"
551 depends on ARCH_SUNXI
552 help
553 Enables support for NAND Flash chips on Allwinner SoCs.
554
54f531f6
ZW
555config MTD_NAND_HISI504
556 tristate "Support for NAND controller on Hisilicon SoC Hip04"
5e0899db 557 depends on HAS_DMA
54f531f6
ZW
558 help
559 Enables support for NAND controller on Hisilicon SoC Hip04.
560
c76b78d8
AT
561config MTD_NAND_QCOM
562 tristate "Support for NAND on QCOM SoCs"
563 depends on ARCH_QCOM
564 help
565 Enables support for NAND flash chips on SoCs containing the EBI2 NAND
566 controller. This controller is found on IPQ806x SoC.
567
1d6b1e46
JRO
568config MTD_NAND_MTK
569 tristate "Support for NAND controller on MTK SoCs"
570 depends on HAS_DMA
571 help
572 Enables support for NAND controller on MTK SoCs.
573 This controller is found on mt27xx, mt81xx, mt65xx SoCs.
574
ec98c681 575endif # MTD_NAND