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