mtd: nand: vf610: remove useless mtd->ecclayout assignment
[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
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
aaf7ea20 77 help
c9d79c4b
GS
78 This enables a NAND flash driver where control signals are
79 connected to GPIO pins, and commands and data are communicated
80 via a memory mapped interface.
aaf7ea20 81
3d12c0c7
JM
82config MTD_NAND_AMS_DELTA
83 tristate "NAND Flash device on Amstrad E3"
ec98c681 84 depends on MACH_AMS_DELTA
494f45d5 85 default y
3d12c0c7
JM
86 help
87 Support for NAND flash on Amstrad E3 (Delta).
88
67ce04bf 89config MTD_NAND_OMAP2
46a00d83 90 tristate "NAND Flash device on OMAP2, OMAP3 and OMAP4"
12f049bd 91 depends on ARCH_OMAP2PLUS
67ce04bf 92 help
46a00d83
JW
93 Support for NAND flash on Texas Instruments OMAP2, OMAP3 and OMAP4
94 platforms.
67ce04bf 95
0e618ef0 96config MTD_NAND_OMAP_BCH
43b77693 97 depends on MTD_NAND_OMAP2
e7cd6824 98 bool "Support hardware based BCH error correction"
0e618ef0
ID
99 default n
100 select BCH
0e618ef0 101 help
90c9c955
PG
102 This config enables the ELM hardware engine, which can be used to
103 locate and correct errors when using BCH ECC scheme. This offloads
104 the cpu from doing ECC error searching and correction. However some
105 legacy OMAP families like OMAP2xxx, OMAP3xxx do not have ELM engine
8b3d58e5 106 so this is optional for them.
0e618ef0 107
e7cd6824
EG
108config MTD_NAND_OMAP_BCH_BUILD
109 def_tristate MTD_NAND_OMAP2 && MTD_NAND_OMAP_BCH
110
1da177e4
LT
111config MTD_NAND_IDS
112 tristate
113
67e054e9
ML
114config MTD_NAND_RICOH
115 tristate "Ricoh xD card reader"
116 default n
f696aa43 117 depends on PCI
67e054e9
ML
118 select MTD_SM_COMMON
119 help
120 Enable support for Ricoh R5C852 xD card reader
121 You also need to enable ether
122 NAND SSFDC (SmartMedia) read only translation layer' or new
123 expermental, readwrite
124 'SmartMedia/xD new translation layer'
125
1da177e4 126config MTD_NAND_AU1550
ef6f0d1f 127 tristate "Au1550/1200 NAND support"
37663860 128 depends on MIPS_ALCHEMY
1da177e4
LT
129 help
130 This enables the driver for the NAND flash controller on the
131 AMD/Alchemy 1550 SOC.
132
b37bde14
BW
133config MTD_NAND_BF5XX
134 tristate "Blackfin on-chip NAND Flash Controller driver"
8c1a1158 135 depends on BF54x || BF52x
b37bde14
BW
136 help
137 This enables the Blackfin on-chip NAND flash controller
138
139 No board specific support is done by this driver, each board
140 must advertise a platform_device for the driver to attach.
141
142 This driver can also be built as a module. If so, the module
143 will be called bf5xx-nand.
144
145config MTD_NAND_BF5XX_HWECC
146 bool "BF5XX NAND Hardware ECC"
a0dd2018 147 default y
b37bde14
BW
148 depends on MTD_NAND_BF5XX
149 help
150 Enable the use of the BF5XX's internal ECC generator when
151 using NAND.
152
fcb90ba7
MF
153config MTD_NAND_BF5XX_BOOTROM_ECC
154 bool "Use Blackfin BootROM ECC Layout"
155 default n
156 depends on MTD_NAND_BF5XX_HWECC
157 help
158 If you wish to modify NAND pages and allow the Blackfin on-chip
159 BootROM to boot from them, say Y here. This is only necessary
160 if you are booting U-Boot out of NAND and you wish to update
161 U-Boot from Linux' userspace. Otherwise, you should say N here.
162
163 If unsure, say N.
164
1da177e4 165config MTD_NAND_S3C2410
9dbc0902 166 tristate "NAND Flash support for Samsung S3C SoCs"
b130d5c2 167 depends on ARCH_S3C24XX || ARCH_S3C64XX
1da177e4 168 help
9dbc0902 169 This enables the NAND flash controller on the S3C24xx and S3C64xx
a4f957f1 170 SoCs
1da177e4 171
4992a9e8 172 No board specific support is done by this driver, each board
61b03bd7 173 must advertise a platform_device for the driver to attach.
1da177e4
LT
174
175config MTD_NAND_S3C2410_DEBUG
9dbc0902 176 bool "Samsung S3C NAND driver debug"
1da177e4
LT
177 depends on MTD_NAND_S3C2410
178 help
9dbc0902 179 Enable debugging of the S3C NAND driver
1da177e4
LT
180
181config MTD_NAND_S3C2410_HWECC
9dbc0902 182 bool "Samsung S3C NAND Hardware ECC"
1da177e4
LT
183 depends on MTD_NAND_S3C2410
184 help
9dbc0902
PK
185 Enable the use of the controller's internal ECC generator when
186 using NAND. Early versions of the chips have had problems with
1da177e4
LT
187 incorrect ECC generation, and if using these, the default of
188 software ECC is preferable.
189
a808ad3b
SM
190config MTD_NAND_NDFC
191 tristate "NDFC NanD Flash Controller"
192 depends on 4xx
193 select MTD_NAND_ECC_SMC
194 help
195 NDFC Nand Flash Controllers are integrated in IBM/AMCC's 4xx SoCs
196
d1fef3c5 197config MTD_NAND_S3C2410_CLKSTOP
9dbc0902 198 bool "Samsung S3C NAND IDLE clock stop"
d1fef3c5
BD
199 depends on MTD_NAND_S3C2410
200 default n
201 help
202 Stop the clock to the NAND controller when there is no chip
203 selected to save power. This will mean there is a small delay
204 when the is NAND chip selected or released, but will save
205 approximately 5mA of power when there is nothing happening.
206
1da177e4 207config MTD_NAND_DISKONCHIP
5d0e137d 208 tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation)"
9310da0b 209 depends on HAS_IOMEM
1da177e4
LT
210 select REED_SOLOMON
211 select REED_SOLOMON_DEC16
212 help
213 This is a reimplementation of M-Systems DiskOnChip 2000,
214 Millennium and Millennium Plus as a standard NAND device driver,
215 as opposed to the earlier self-contained MTD device drivers.
216 This should enable, among other things, proper JFFS2 operation on
217 these devices.
218
219config MTD_NAND_DISKONCHIP_PROBE_ADVANCED
220 bool "Advanced detection options for DiskOnChip"
221 depends on MTD_NAND_DISKONCHIP
222 help
223 This option allows you to specify nonstandard address at which to
224 probe for a DiskOnChip, or to change the detection options. You
225 are unlikely to need any of this unless you are using LinuxBIOS.
226 Say 'N'.
227
228config MTD_NAND_DISKONCHIP_PROBE_ADDRESS
229 hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED
230 depends on MTD_NAND_DISKONCHIP
231 default "0"
232 ---help---
233 By default, the probe for DiskOnChip devices will look for a
234 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
235 This option allows you to specify a single address at which to probe
236 for the device, which is useful if you have other devices in that
237 range which get upset when they are probed.
238
239 (Note that on PowerPC, the normal probe will only check at
240 0xE4000000.)
241
242 Normally, you should leave this set to zero, to allow the probe at
243 the normal addresses.
244
245config MTD_NAND_DISKONCHIP_PROBE_HIGH
246 bool "Probe high addresses"
247 depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED
248 help
249 By default, the probe for DiskOnChip devices will look for a
250 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
251 This option changes to make it probe between 0xFFFC8000 and
252 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
253 useful to you. Say 'N'.
254
255config MTD_NAND_DISKONCHIP_BBTWRITE
256 bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP"
257 depends on MTD_NAND_DISKONCHIP
258 help
259 On DiskOnChip devices shipped with the INFTL filesystem (Millennium
260 and 2000 TSOP/Alon), Linux reserves some space at the end of the
261 device for the Bad Block Table (BBT). If you have existing INFTL
262 data on your device (created by non-Linux tools such as M-Systems'
263 DOS drivers), your data might overlap the area Linux wants to use for
264 the BBT. If this is a concern for you, leave this option disabled and
265 Linux will not write BBT data into this area.
266 The downside of leaving this option disabled is that if bad blocks
267 are detected by Linux, they will not be recorded in the BBT, which
268 could cause future problems.
269 Once you enable this option, new filesystems (INFTL or others, created
270 in Linux or other operating systems) will not use the reserved area.
271 The only reason not to enable this option is to prevent damage to
272 preexisting filesystems.
273 Even if you leave this disabled, you can enable BBT writes at module
274 load time (assuming you build diskonchip as a module) with the module
275 parameter "inftl_bbt_write=1".
1da177e4 276
570469f3 277config MTD_NAND_DOCG4
5d0e137d
KC
278 tristate "Support for DiskOnChip G4"
279 depends on HAS_IOMEM
570469f3
MD
280 select BCH
281 select BITREVERSE
282 help
283 Support for diskonchip G4 nand flash, found in various smartphones and
284 PDAs, among them the Palm Treo680, HTC Prophet and Wizard, Toshiba
285 Portege G900, Asus P526, and O2 XDA Zinc.
286
287 With this driver you will be able to use UBI and create a ubifs on the
288 device, so you may wish to consider enabling UBI and UBIFS as well.
289
290 These devices ship with the Mys/Sandisk SAFTL formatting, for which
291 there is currently no mtd parser, so you may want to use command line
292 partitioning to segregate write-protected blocks. On the Treo680, the
293 first five erase blocks (256KiB each) are write-protected, followed
294 by the block containing the saftl partition table. This is probably
295 typical.
296
54af6b46
AB
297config MTD_NAND_SHARPSL
298 tristate "Support for NAND Flash on Sharp SL Series (C7xx + others)"
ec98c681 299 depends on ARCH_PXA
54af6b46 300
c45aa055 301config MTD_NAND_CAFE
8c61b7a7
SB
302 tristate "NAND support for OLPC CAFÉ chip"
303 depends on PCI
304 select REED_SOLOMON
305 select REED_SOLOMON_DEC16
306 help
8f46c527 307 Use NAND flash attached to the CAFÉ chip designed for the OLPC
8c61b7a7 308 laptop.
c45aa055 309
179fdc3f
DW
310config MTD_NAND_CS553X
311 tristate "NAND support for CS5535/CS5536 (AMD Geode companion chip)"
4272ebfb 312 depends on X86_32
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
76b10467
SW
427config MTD_NAND_FSL_ELBC
428 tristate "NAND support for Freescale eLBC controllers"
be802bf9 429 depends on PPC
3ab8f2a2 430 select FSL_LBC
76b10467
SW
431 help
432 Various Freescale chips, including the 8313, include a NAND Flash
433 Controller Module with built-in hardware ECC capabilities.
434 Enabling this option will enable you to use this to control
435 external NAND devices.
436
82771882
PK
437config MTD_NAND_FSL_IFC
438 tristate "NAND support for Freescale IFC controller"
439 depends on MTD_NAND && FSL_SOC
440 select FSL_IFC
42d87b18 441 select MEMORY
82771882
PK
442 help
443 Various Freescale chips e.g P1010, include a NAND Flash machine
444 with built-in hardware ECC capabilities.
445 Enabling this option will enable you to use this to control
446 external NAND devices.
447
5c249c5a
AV
448config MTD_NAND_FSL_UPM
449 tristate "Support for NAND on Freescale UPM"
8c1a1158 450 depends on PPC_83xx || PPC_85xx
5c249c5a
AV
451 select FSL_LBC
452 help
453 Enables support for NAND Flash chips wired onto Freescale PowerPC
454 processor localbus with User-Programmable Machine support.
455
bb315f74
AG
456config MTD_NAND_MPC5121_NFC
457 tristate "MPC5121 built-in NAND Flash Controller support"
458 depends on PPC_MPC512x
459 help
460 This enables the driver for the NAND flash controller on the
461 MPC5121 SoC.
462
456930d8
SA
463config MTD_NAND_VF610_NFC
464 tristate "Support for Freescale NFC for VF610/MPC5125"
465 depends on (SOC_VF610 || COMPILE_TEST)
466 help
467 Enables support for NAND Flash Controller on some Freescale
468 processors like the VF610, MPC5125, MCF54418 or Kinetis K70.
049f4250
SA
469 The driver supports a maximum 2k page size. With 2k pages and
470 64 bytes or more of OOB, hardware ECC with up to 32-bit error
471 correction is supported. Hardware ECC is only enabled through
472 device tree.
456930d8 473
34f6e157
SH
474config MTD_NAND_MXC
475 tristate "MXC NAND support"
4d363b55 476 depends on ARCH_MXC
34f6e157
SH
477 help
478 This enables the driver for the NAND flash controller on the
479 MXC processors.
480
6028aa01
YS
481config MTD_NAND_SH_FLCTL
482 tristate "Support for NAND on Renesas SuperH FLCTL"
d5c56201 483 depends on SUPERH || COMPILE_TEST
3d44dc23
RW
484 depends on HAS_IOMEM
485 depends on HAS_DMA
6028aa01
YS
486 help
487 Several Renesas SuperH CPU has FLCTL. This option enables support
b79c7adf 488 for NAND Flash using FLCTL.
6028aa01 489
ff4569c7 490config MTD_NAND_DAVINCI
458f3933
IK
491 tristate "Support NAND on DaVinci/Keystone SoC"
492 depends on ARCH_DAVINCI || (ARCH_KEYSTONE && TI_AEMIF)
ff4569c7
DB
493 help
494 Enable the driver for NAND flash chips on Texas Instruments
458f3933 495 DaVinci/Keystone processors.
ff4569c7 496
64fb65ba
AN
497config MTD_NAND_TXX9NDFMC
498 tristate "NAND Flash support for TXx9 SoC"
499 depends on SOC_TX4938 || SOC_TX4939
500 help
501 This enables the NAND flash controller on the TXx9 SoCs.
502
1b578193
WG
503config MTD_NAND_SOCRATES
504 tristate "Support for NAND on Socrates board"
8c1a1158 505 depends on SOCRATES
1b578193
WG
506 help
507 Enables support for NAND Flash chips wired onto Socrates board.
508
bb6a7755
DW
509config MTD_NAND_NUC900
510 tristate "Support for NAND on Nuvoton NUC9xx/w90p910 evaluation boards."
6a8a98b2 511 depends on ARCH_W90X900
8bff82cb
WZ
512 help
513 This enables the driver for the NAND Flash on evaluation board based
bb6a7755 514 on w90p910 / NUC9xx.
8bff82cb 515
ba01d6ec
LPC
516config MTD_NAND_JZ4740
517 tristate "Support for JZ4740 SoC NAND controller"
518 depends on MACH_JZ4740
519 help
520 Enables support for NAND Flash on JZ4740 SoC based boards.
521
ae02ab00
AS
522config MTD_NAND_JZ4780
523 tristate "Support for NAND on JZ4780 SoC"
524 depends on MACH_JZ4780 && JZ4780_NEMC
525 help
526 Enables support for NAND Flash connected to the NEMC on JZ4780 SoC
527 based boards, using the BCH controller for hardware error correction.
528
6c009ab8
LW
529config MTD_NAND_FSMC
530 tristate "Support for NAND on ST Micros FSMC"
694e33a7 531 depends on PLAT_SPEAR || ARCH_NOMADIK || ARCH_U8500 || MACH_U300
6c009ab8
LW
532 help
533 Enables support for NAND Flash chips on the ST Microelectronics
534 Flexible Static Memory Controller (FSMC)
535
99f2b107
JC
536config MTD_NAND_XWAY
537 tristate "Support for NAND on Lantiq XWAY SoC"
538 depends on LANTIQ && SOC_TYPE_XWAY
539 select MTD_NAND_PLATFORM
540 help
541 Enables support for NAND Flash chips on Lantiq XWAY SoCs. NAND is attached
542 to the External Bus Unit (EBU).
543
1fef62c1
BB
544config MTD_NAND_SUNXI
545 tristate "Support for NAND on Allwinner SoCs"
546 depends on ARCH_SUNXI
547 help
548 Enables support for NAND Flash chips on Allwinner SoCs.
549
54f531f6
ZW
550config MTD_NAND_HISI504
551 tristate "Support for NAND controller on Hisilicon SoC Hip04"
5e0899db 552 depends on HAS_DMA
54f531f6
ZW
553 help
554 Enables support for NAND controller on Hisilicon SoC Hip04.
555
ec98c681 556endif # MTD_NAND
This page took 0.563566 seconds and 5 git commands to generate.