Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # drivers/mtd/nand/Kconfig |
2 | # $Id: Kconfig,v 1.26 2005/01/05 12:42:24 dwmw2 Exp $ | |
3 | ||
4 | menu "NAND Flash Device Drivers" | |
5 | depends on MTD!=n | |
6 | ||
7 | config MTD_NAND | |
8 | tristate "NAND Device Support" | |
9 | depends on MTD | |
10 | select MTD_NAND_IDS | |
11 | help | |
12 | This enables support for accessing all type of NAND flash | |
13 | devices. For further information see | |
14 | <http://www.linux-mtd.infradead.org/tech/nand.html>. | |
15 | ||
16 | config MTD_NAND_VERIFY_WRITE | |
17 | bool "Verify NAND page writes" | |
18 | depends on MTD_NAND | |
19 | help | |
20 | This adds an extra check when data is written to the flash. The | |
21 | NAND flash device internally checks only bits transitioning | |
22 | from 1 to 0. There is a rare possibility that even though the | |
23 | device thinks the write was successful, a bit could have been | |
24 | flipped accidentaly due to device wear or something else. | |
25 | ||
26 | config MTD_NAND_AUTCPU12 | |
27 | tristate "SmartMediaCard on autronix autcpu12 board" | |
28 | depends on ARM && MTD_NAND && ARCH_AUTCPU12 | |
29 | help | |
30 | This enables the driver for the autronix autcpu12 board to | |
31 | access the SmartMediaCard. | |
32 | ||
33 | config MTD_NAND_EDB7312 | |
34 | tristate "Support for Cirrus Logic EBD7312 evaluation board" | |
35 | depends on ARM && MTD_NAND && ARCH_EDB7312 | |
36 | help | |
37 | This enables the driver for the Cirrus Logic EBD7312 evaluation | |
38 | board to access the onboard NAND Flash. | |
39 | ||
40 | config MTD_NAND_H1900 | |
41 | tristate "iPAQ H1900 flash" | |
42 | depends on ARM && MTD_NAND && ARCH_PXA && MTD_PARTITIONS | |
43 | help | |
44 | This enables the driver for the iPAQ h1900 flash. | |
45 | ||
46 | config MTD_NAND_SPIA | |
47 | tristate "NAND Flash device on SPIA board" | |
48 | depends on ARM && ARCH_P720T && MTD_NAND | |
49 | help | |
50 | If you had to ask, you don't have one. Say 'N'. | |
51 | ||
52 | config MTD_NAND_TOTO | |
53 | tristate "NAND Flash device on TOTO board" | |
54 | depends on ARM && ARCH_OMAP && MTD_NAND | |
55 | help | |
56 | Support for NAND flash on Texas Instruments Toto platform. | |
57 | ||
58 | config MTD_NAND_IDS | |
59 | tristate | |
60 | ||
61 | config MTD_NAND_TX4925NDFMC | |
62 | tristate "SmartMedia Card on Toshiba RBTX4925 reference board" | |
63 | depends on TOSHIBA_RBTX4925 && MTD_NAND && TOSHIBA_RBTX4925_MPLEX_NAND | |
64 | help | |
65 | This enables the driver for the NAND flash device found on the | |
66 | Toshiba RBTX4925 reference board, which is a SmartMediaCard. | |
67 | ||
68 | config MTD_NAND_TX4938NDFMC | |
69 | tristate "NAND Flash device on Toshiba RBTX4938 reference board" | |
70 | depends on TOSHIBA_RBTX4938 && MTD_NAND && TOSHIBA_RBTX4938_MPLEX_NAND | |
71 | help | |
72 | This enables the driver for the NAND flash device found on the | |
73 | Toshiba RBTX4938 reference board. | |
74 | ||
75 | config MTD_NAND_AU1550 | |
76 | tristate "Au1550 NAND support" | |
77 | depends on SOC_AU1550 && MTD_NAND | |
78 | help | |
79 | This enables the driver for the NAND flash controller on the | |
80 | AMD/Alchemy 1550 SOC. | |
81 | ||
82 | config MTD_NAND_RTC_FROM4 | |
83 | tristate "Renesas Flash ROM 4-slot interface board (FROM_BOARD4)" | |
84 | depends on MTD_NAND && SH_SOLUTION_ENGINE | |
85 | select REED_SOLOMON | |
86 | select REED_SOLOMON_DEC8 | |
87 | help | |
88 | This enables the driver for the Renesas Technology AG-AND | |
89 | flash interface board (FROM_BOARD4) | |
90 | ||
91 | config MTD_NAND_PPCHAMELEONEVB | |
92 | tristate "NAND Flash device on PPChameleonEVB board" | |
93 | depends on PPCHAMELEONEVB && MTD_NAND | |
94 | help | |
95 | This enables the NAND flash driver on the PPChameleon EVB Board. | |
96 | ||
97 | config MTD_NAND_S3C2410 | |
98 | tristate "NAND Flash support for S3C2410 SoC" | |
99 | depends on ARCH_S3C2410 && MTD_NAND | |
100 | help | |
101 | This enables the NAND flash controller on the S3C2410. | |
102 | ||
103 | No board specfic support is done by this driver, each board | |
104 | must advertise a platform_device for the driver to attach. | |
105 | ||
106 | config MTD_NAND_S3C2410_DEBUG | |
107 | bool "S3C2410 NAND driver debug" | |
108 | depends on MTD_NAND_S3C2410 | |
109 | help | |
110 | Enable debugging of the S3C2410 NAND driver | |
111 | ||
112 | config MTD_NAND_S3C2410_HWECC | |
113 | bool "S3C2410 NAND Hardware ECC" | |
114 | depends on MTD_NAND_S3C2410 | |
115 | help | |
116 | Enable the use of the S3C2410's internal ECC generator when | |
117 | using NAND. Early versions of the chip have had problems with | |
118 | incorrect ECC generation, and if using these, the default of | |
119 | software ECC is preferable. | |
120 | ||
121 | If you lay down a device with the hardware ECC, then you will | |
122 | currently not be able to switch to software, as there is no | |
123 | implementation for ECC method used by the S3C2410 | |
124 | ||
125 | config MTD_NAND_DISKONCHIP | |
126 | tristate "DiskOnChip 2000, Millennium and Millennium Plus (NAND reimplementation) (EXPERIMENTAL)" | |
127 | depends on MTD_NAND && EXPERIMENTAL | |
128 | select REED_SOLOMON | |
129 | select REED_SOLOMON_DEC16 | |
130 | help | |
131 | This is a reimplementation of M-Systems DiskOnChip 2000, | |
132 | Millennium and Millennium Plus as a standard NAND device driver, | |
133 | as opposed to the earlier self-contained MTD device drivers. | |
134 | This should enable, among other things, proper JFFS2 operation on | |
135 | these devices. | |
136 | ||
137 | config MTD_NAND_DISKONCHIP_PROBE_ADVANCED | |
138 | bool "Advanced detection options for DiskOnChip" | |
139 | depends on MTD_NAND_DISKONCHIP | |
140 | help | |
141 | This option allows you to specify nonstandard address at which to | |
142 | probe for a DiskOnChip, or to change the detection options. You | |
143 | are unlikely to need any of this unless you are using LinuxBIOS. | |
144 | Say 'N'. | |
145 | ||
146 | config MTD_NAND_DISKONCHIP_PROBE_ADDRESS | |
147 | hex "Physical address of DiskOnChip" if MTD_NAND_DISKONCHIP_PROBE_ADVANCED | |
148 | depends on MTD_NAND_DISKONCHIP | |
149 | default "0" | |
150 | ---help--- | |
151 | By default, the probe for DiskOnChip devices will look for a | |
152 | DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000. | |
153 | This option allows you to specify a single address at which to probe | |
154 | for the device, which is useful if you have other devices in that | |
155 | range which get upset when they are probed. | |
156 | ||
157 | (Note that on PowerPC, the normal probe will only check at | |
158 | 0xE4000000.) | |
159 | ||
160 | Normally, you should leave this set to zero, to allow the probe at | |
161 | the normal addresses. | |
162 | ||
163 | config MTD_NAND_DISKONCHIP_PROBE_HIGH | |
164 | bool "Probe high addresses" | |
165 | depends on MTD_NAND_DISKONCHIP_PROBE_ADVANCED | |
166 | help | |
167 | By default, the probe for DiskOnChip devices will look for a | |
168 | DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000. | |
169 | This option changes to make it probe between 0xFFFC8000 and | |
170 | 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be | |
171 | useful to you. Say 'N'. | |
172 | ||
173 | config MTD_NAND_DISKONCHIP_BBTWRITE | |
174 | bool "Allow BBT writes on DiskOnChip Millennium and 2000TSOP" | |
175 | depends on MTD_NAND_DISKONCHIP | |
176 | help | |
177 | On DiskOnChip devices shipped with the INFTL filesystem (Millennium | |
178 | and 2000 TSOP/Alon), Linux reserves some space at the end of the | |
179 | device for the Bad Block Table (BBT). If you have existing INFTL | |
180 | data on your device (created by non-Linux tools such as M-Systems' | |
181 | DOS drivers), your data might overlap the area Linux wants to use for | |
182 | the BBT. If this is a concern for you, leave this option disabled and | |
183 | Linux will not write BBT data into this area. | |
184 | The downside of leaving this option disabled is that if bad blocks | |
185 | are detected by Linux, they will not be recorded in the BBT, which | |
186 | could cause future problems. | |
187 | Once you enable this option, new filesystems (INFTL or others, created | |
188 | in Linux or other operating systems) will not use the reserved area. | |
189 | The only reason not to enable this option is to prevent damage to | |
190 | preexisting filesystems. | |
191 | Even if you leave this disabled, you can enable BBT writes at module | |
192 | load time (assuming you build diskonchip as a module) with the module | |
193 | parameter "inftl_bbt_write=1". | |
194 | ||
195 | config MTD_NAND_SHARPSL | |
196 | bool "Support for NAND Flash on Sharp SL Series (C7xx + others)" | |
197 | depends on MTD_NAND && ARCH_PXA | |
198 | ||
199 | config MTD_NAND_NANDSIM | |
200 | bool "Support for NAND Flash Simulator" | |
201 | depends on MTD_NAND && MTD_PARTITIONS | |
202 | ||
203 | help | |
204 | The simulator may simulate verious NAND flash chips for the | |
205 | MTD nand layer. | |
206 | ||
207 | endmenu |