1 # drivers/mtd/chips/Kconfig
2 # $Id: Kconfig,v 1.9 2004/07/16 15:32:14 dwmw2 Exp $
4 menu "RAM/ROM/Flash chip drivers"
8 tristate "Detect flash chips by Common Flash Interface (CFI) probe"
11 The Common Flash Interface specification was developed by Intel,
12 AMD and other flash manufactures that provides a universal method
13 for probing the capabilities of flash devices. If you wish to
14 support any device that is CFI-compliant, you need to enable this
15 option. Visit <http://www.amd.com/products/nvd/overview/cfi.html>
16 for more information on CFI.
19 tristate "Detect non-CFI AMD/JEDEC-compatible flash chips"
22 This option enables JEDEC-style probing of flash chips which are not
23 compatible with the Common Flash Interface, but will use the common
24 CFI-targetted flash drivers for any chips which are identified which
25 are in fact compatible in all but the probe method. This actually
26 covers most AMD/Fujitsu-compatible chips, and will shortly cover also
27 non-CFI Intel chips (that code is in MTD CVS and should shortly be sent
28 for inclusion in Linus' tree)
32 default m if MTD_CFI!=y && !MTD_INTELPROBE && MTD_JEDECPROBE!=y && (MTD_CFI=m || MTD_JEDECPROBE=m)
33 default y if MTD_CFI=y || MTD_INTELPROBE || MTD_JEDECPROBE=y
35 config MTD_CFI_ADV_OPTIONS
36 bool "Flash chip driver advanced configuration options"
37 depends on MTD_GEN_PROBE
39 If you need to specify a specific endianness for access to flash
40 chips, or if you wish to reduce the size of the kernel by including
41 support for only specific arrangements of flash chips, say 'Y'. This
42 option does not directly affect the code, but will enable other
43 configuration options which allow you to do so.
48 prompt "Flash cmd/query data swapping"
49 depends on MTD_CFI_ADV_OPTIONS
50 default MTD_CFI_NOSWAP
55 This option defines the way in which the CPU attempts to arrange
56 data bits when writing the 'magic' commands to the chips. Saying
57 'NO', which is the default when CONFIG_MTD_CFI_ADV_OPTIONS isn't
58 enabled, means that the CPU will not do any swapping; the chips
59 are expected to be wired to the CPU in 'host-endian' form.
60 Specific arrangements are possible with the BIG_ENDIAN_BYTE and
61 LITTLE_ENDIAN_BYTE, if the bytes are reversed.
63 If you have a LART, on which the data (and address) lines were
64 connected in a fashion which ensured that the nets were as short
65 as possible, resulting in a bit-shuffling which seems utterly
66 random to the untrained eye, you need the LART_ENDIAN_BYTE option.
68 Yes, there really exists something sicker than PDP-endian :)
70 config MTD_CFI_BE_BYTE_SWAP
71 bool "BIG_ENDIAN_BYTE"
73 config MTD_CFI_LE_BYTE_SWAP
74 bool "LITTLE_ENDIAN_BYTE"
78 config MTD_CFI_GEOMETRY
79 bool "Specific CFI Flash geometry selection"
80 depends on MTD_CFI_ADV_OPTIONS
82 This option does not affect the code directly, but will enable
83 some other configuration options which would allow you to reduce
84 the size of the kernel by including support for only certain
85 arrangements of CFI chips. If unsure, say 'N' and all options
86 which are supported by the current code will be enabled.
88 config MTD_MAP_BANK_WIDTH_1
89 bool "Support 8-bit buswidth" if MTD_CFI_GEOMETRY
92 If you wish to support CFI devices on a physical bus which is
95 config MTD_MAP_BANK_WIDTH_2
96 bool "Support 16-bit buswidth" if MTD_CFI_GEOMETRY
99 If you wish to support CFI devices on a physical bus which is
100 16 bits wide, say 'Y'.
102 config MTD_MAP_BANK_WIDTH_4
103 bool "Support 32-bit buswidth" if MTD_CFI_GEOMETRY
106 If you wish to support CFI devices on a physical bus which is
107 32 bits wide, say 'Y'.
109 config MTD_MAP_BANK_WIDTH_8
110 bool "Support 64-bit buswidth" if MTD_CFI_GEOMETRY
113 If you wish to support CFI devices on a physical bus which is
114 64 bits wide, say 'Y'.
116 config MTD_MAP_BANK_WIDTH_16
117 bool "Support 128-bit buswidth" if MTD_CFI_GEOMETRY
120 If you wish to support CFI devices on a physical bus which is
121 128 bits wide, say 'Y'.
123 config MTD_MAP_BANK_WIDTH_32
124 bool "Support 256-bit buswidth" if MTD_CFI_GEOMETRY
127 If you wish to support CFI devices on a physical bus which is
128 256 bits wide, say 'Y'.
131 bool "Support 1-chip flash interleave" if MTD_CFI_GEOMETRY
134 If your flash chips are not interleaved - i.e. you only have one
135 flash chip addressed by each bus cycle, then say 'Y'.
138 bool "Support 2-chip flash interleave" if MTD_CFI_GEOMETRY
141 If your flash chips are interleaved in pairs - i.e. you have two
142 flash chips addressed by each bus cycle, then say 'Y'.
145 bool "Support 4-chip flash interleave" if MTD_CFI_GEOMETRY
148 If your flash chips are interleaved in fours - i.e. you have four
149 flash chips addressed by each bus cycle, then say 'Y'.
152 bool "Support 8-chip flash interleave" if MTD_CFI_GEOMETRY
155 If your flash chips are interleaved in eights - i.e. you have eight
156 flash chips addressed by each bus cycle, then say 'Y'.
158 config MTD_CFI_INTELEXT
159 tristate "Support for Intel/Sharp flash chips"
160 depends on MTD_GEN_PROBE
162 The Common Flash Interface defines a number of different command
163 sets which a CFI-compliant chip may claim to implement. This code
164 provides support for one of those command sets, used on Intel
165 StrataFlash and other parts.
167 config MTD_CFI_AMDSTD
168 tristate "Support for AMD/Fujitsu flash chips"
169 depends on MTD_GEN_PROBE
171 The Common Flash Interface defines a number of different command
172 sets which a CFI-compliant chip may claim to implement. This code
173 provides support for one of those command sets, used on chips
174 including the AMD Am29LV320.
176 config MTD_CFI_AMDSTD_RETRY
177 int "Retry failed commands (erase/program)"
178 depends on MTD_CFI_AMDSTD
181 Some chips, when attached to a shared bus, don't properly filter
182 bus traffic that is destined to other devices. This broken
183 behavior causes erase and program sequences to be aborted when
184 the sequences are mixed with traffic for other devices.
186 SST49LF040 (and related) chips are know to be broken.
188 config MTD_CFI_AMDSTD_RETRY_MAX
189 int "Max retries of failed commands (erase/program)"
190 depends on MTD_CFI_AMDSTD_RETRY
193 If you have an SST49LF040 (or related chip) then this value should
194 be set to at least 1. This can also be adjusted at driver load
195 time with the retry_cmd_max module parameter.
198 tristate "Support for ST (Advanced Architecture) flash chips"
199 depends on MTD_GEN_PROBE
201 The Common Flash Interface defines a number of different command
202 sets which a CFI-compliant chip may claim to implement. This code
203 provides support for one of those command sets.
207 default y if MTD_CFI_INTELEXT=y || MTD_CFI_AMDSTD=y || MTD_CFI_STAA=y
208 default m if MTD_CFI_INTELEXT=m || MTD_CFI_AMDSTD=m || MTD_CFI_STAA=m
211 tristate "Support for RAM chips in bus mapping"
214 This option enables basic support for RAM chips accessed through
215 a bus mapping driver.
218 tristate "Support for ROM chips in bus mapping"
221 This option enables basic support for ROM chips accessed through
222 a bus mapping driver.
225 tristate "Support for absent chips in bus mapping"
228 This option enables support for a dummy probing driver used to
229 allocated placeholder MTD devices on systems that have socketed
230 or removable media. Use of this driver as a fallback chip probe
231 preserves the expected registration order of MTD device nodes on
232 the system regardless of media presence. Device nodes created
233 with this driver will return -ENODEV upon access.
235 config MTD_OBSOLETE_CHIPS
236 depends on MTD && BROKEN
237 bool "Older (theoretically obsoleted now) drivers for non-CFI chips"
239 This option does not enable any code directly, but will allow you to
240 select some other chip drivers which are now considered obsolete,
241 because the generic CONFIG_JEDECPROBE code above should now detect
242 the chips which are supported by these drivers, and allow the generic
243 CFI-compatible drivers to drive the chips. Say 'N' here unless you have
244 already tried the CONFIG_JEDECPROBE method and reported its failure
245 to the MTD mailing list at <linux-mtd@lists.infradead.org>
248 tristate "AMD compatible flash chip support (non-CFI)"
249 depends on MTD && MTD_OBSOLETE_CHIPS
251 This option enables support for flash chips using AMD-compatible
252 commands, including some which are not CFI-compatible and hence
253 cannot be used with the CONFIG_MTD_CFI_AMDSTD option.
255 It also works on AMD compatible chips that do conform to CFI.
258 tristate "pre-CFI Sharp chip support"
259 depends on MTD && MTD_OBSOLETE_CHIPS
261 This option enables support for flash chips using Sharp-compatible
262 commands, including some which are not CFI-compatible and hence
263 cannot be used with the CONFIG_MTD_CFI_INTELxxx options.
266 tristate "JEDEC device support"
267 depends on MTD && MTD_OBSOLETE_CHIPS
269 Enable older older JEDEC flash interface devices for self
270 programming flash. It is commonly used in older AMD chips. It is
271 only called JEDEC because the JEDEC association
272 <http://www.jedec.org/> distributes the identification codes for the