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