blob: 35081ce77fbdd0bd4260fd9a812ee6cae8dd08ca [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001menu "Self-contained MTD device drivers"
2 depends on MTD!=n
3
4config MTD_PMC551
5 tristate "Ramix PMC551 PCI Mezzanine RAM card support"
Jan Engelhardtec98c682007-04-19 16:21:41 -05006 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -07007 ---help---
8 This provides a MTD device driver for the Ramix PMC551 RAM PCI card
9 from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.
10 These devices come in memory configurations from 32M - 1G. If you
11 have one, you probably want to enable this.
12
13 If this driver is compiled as a module you get the ability to select
14 the size of the aperture window pointing into the devices memory.
15 What this means is that if you have a 1G card, normally the kernel
16 will use a 1G memory map as its view of the device. As a module,
17 you can select a 1M window into the memory and the driver will
18 "slide" the window around the PMC551's memory. This was
19 particularly useful on the 2.2 kernels on PPC architectures as there
20 was limited kernel space to deal with.
21
22config MTD_PMC551_BUGFIX
23 bool "PMC551 256M DRAM Bugfix"
24 depends on MTD_PMC551
25 help
26 Some of Ramix's PMC551 boards with 256M configurations have invalid
27 column and row mux values. This option will fix them, but will
28 break other memory configurations. If unsure say N.
29
30config MTD_PMC551_DEBUG
31 bool "PMC551 Debugging"
32 depends on MTD_PMC551
33 help
34 This option makes the PMC551 more verbose during its operation and
35 is only really useful if you are developing on this driver or
36 suspect a possible hardware or driver bug. If unsure say N.
37
38config MTD_MS02NV
39 tristate "DEC MS02-NV NVRAM module support"
Jan Engelhardtec98c682007-04-19 16:21:41 -050040 depends on MACH_DECSTATION
Linus Torvalds1da177e2005-04-16 15:20:36 -070041 help
42 This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
43 backed-up NVRAM module. The module was originally meant as an NFS
44 accelerator. Say Y here if you have a DECstation 5000/2x0 or a
45 DECsystem 5900 equipped with such a module.
46
Martin Michlmayrbe21ce12006-03-20 04:40:26 +000047 If you want to compile this driver as a module ( = code which can be
48 inserted in and removed from the running kernel whenever you want),
Alexander E. Patrakov39f5fb32007-03-16 18:28:43 +050049 say M here and read <file:Documentation/kbuild/modules.txt>.
Pavel Machek4737f092009-06-05 00:44:53 +020050 The module will be called ms02-nv.
Martin Michlmayrbe21ce12006-03-20 04:40:26 +000051
David Brownell1d6432f2006-01-08 13:34:22 -080052config MTD_DATAFLASH
53 tristate "Support for AT45xxx DataFlash"
Jan Engelhardtec98c682007-04-19 16:21:41 -050054 depends on SPI_MASTER && EXPERIMENTAL
David Brownell1d6432f2006-01-08 13:34:22 -080055 help
56 This enables access to AT45xxx DataFlash chips, using SPI.
57 Sometimes DataFlash chips are packaged inside MMC-format
58 cards; at this writing, the MMC stack won't handle those.
59
David Brownell8c640382008-08-06 21:55:14 -070060config MTD_DATAFLASH_WRITE_VERIFY
61 bool "Verify DataFlash page writes"
62 depends on MTD_DATAFLASH
63 help
64 This adds an extra check when data is written to the flash.
65 It may help if you are verifying chip setup (timings etc) on
66 your board. There is a rare possibility that even though the
67 device thinks the write was successful, a bit could have been
68 flipped accidentally due to device wear or something else.
69
David Brownell34a82442008-07-30 12:35:05 -070070config MTD_DATAFLASH_OTP
71 bool "DataFlash OTP support (Security Register)"
72 depends on MTD_DATAFLASH
73 select HAVE_MTD_OTP
74 help
75 Newer DataFlash chips (revisions C and D) support 128 bytes of
76 one-time-programmable (OTP) data. The first half may be written
77 (once) with up to 64 bytes of data, such as a serial number or
78 other key product data. The second half is programmed with a
79 unique-to-each-chip bit pattern at the factory.
80
Mike Lavender2f9f7622006-01-08 13:34:27 -080081config MTD_M25P80
David Brownellfa0a8c72007-06-24 15:12:35 -070082 tristate "Support most SPI Flash chips (AT26DF, M25P, W25X, ...)"
Jan Engelhardtec98c682007-04-19 16:21:41 -050083 depends on SPI_MASTER && EXPERIMENTAL
Mike Lavender2f9f7622006-01-08 13:34:27 -080084 help
David Brownellfa0a8c72007-06-24 15:12:35 -070085 This enables access to most modern SPI flash chips, used for
86 program and data storage. Series supported include Atmel AT26DF,
87 Spansion S25SL, SST 25VF, ST M25P, and Winbond W25X. Other chips
88 are supported as well. See the driver source for the current list,
89 or to add other chips.
90
91 Note that the original DataFlash chips (AT45 series, not AT26DF),
92 need an entirely different driver.
93
94 Set up your spi devices with the right board-specific platform data,
95 if you want to specify device partitioning or to use a device which
96 doesn't support the JEDEC ID instruction.
Mike Lavender2f9f7622006-01-08 13:34:27 -080097
Bryan Wu2230b762008-04-25 12:07:32 +080098config M25PXX_USE_FAST_READ
99 bool "Use FAST_READ OPCode allowing SPI CLK <= 50MHz"
100 depends on MTD_M25P80
101 default y
102 help
103 This option enables FAST_READ access supported by ST M25Pxx.
104
Ryan Mallonec77e212009-09-18 12:51:40 -0700105config MTD_SST25L
106 tristate "Support SST25L (non JEDEC) SPI Flash chips"
107 depends on SPI_MASTER
108 help
109 This enables access to the non JEDEC SST25L SPI flash chips, used
110 for program and data storage.
111
112 Set up your spi devices with the right board-specific platform data,
113 if you want to specify device partitioning.
114
Linus Torvalds1da177e2005-04-16 15:20:36 -0700115config MTD_SLRAM
116 tristate "Uncached system RAM"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700117 help
118 If your CPU cannot cache all of the physical memory in your machine,
119 you can still use it for storage or swap by using this driver to
120 present it to the system as a Memory Technology Device.
121
122config MTD_PHRAM
123 tristate "Physical system RAM"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700124 help
125 This is a re-implementation of the slram driver above.
126
127 Use this driver to access physical memory that the kernel proper
128 doesn't have access to, memory beyond the mem=xxx limit, nvram,
129 memory on the video card, etc...
130
131config MTD_LART
132 tristate "28F160xx flash driver for LART"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500133 depends on SA1100_LART
Linus Torvalds1da177e2005-04-16 15:20:36 -0700134 help
135 This enables the flash driver for LART. Please note that you do
136 not need any mapping/chip driver for LART. This one does it all
137 for you, so go disable all of those if you enabled some of them (:
138
139config MTD_MTDRAM
140 tristate "Test driver using RAM"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700141 help
142 This enables a test MTD device driver which uses vmalloc() to
143 provide storage. You probably want to say 'N' unless you're
144 testing stuff.
145
146config MTDRAM_TOTAL_SIZE
147 int "MTDRAM device size in KiB"
148 depends on MTD_MTDRAM
149 default "4096"
150 help
151 This allows you to configure the total size of the MTD device
152 emulated by the MTDRAM driver. If the MTDRAM driver is built
153 as a module, it is also possible to specify this as a parameter when
154 loading the module.
155
156config MTDRAM_ERASE_SIZE
157 int "MTDRAM erase block size in KiB"
158 depends on MTD_MTDRAM
159 default "128"
160 help
161 This allows you to configure the size of the erase blocks in the
162 device emulated by the MTDRAM driver. If the MTDRAM driver is built
163 as a module, it is also possible to specify this as a parameter when
164 loading the module.
165
166#If not a module (I don't want to test it as a module)
167config MTDRAM_ABS_POS
168 hex "SRAM Hexadecimal Absolute position or 0"
169 depends on MTD_MTDRAM=y
170 default "0"
171 help
172 If you have system RAM accessible by the CPU but not used by Linux
173 in normal operation, you can give the physical address at which the
174 available RAM starts, and the MTDRAM driver will use it instead of
Thomas Gleixnere5580fb2005-11-07 11:15:40 +0000175 allocating space from Linux's available memory. Otherwise, leave
Linus Torvalds1da177e2005-04-16 15:20:36 -0700176 this set to zero. Most people will want to leave this as zero.
177
Joern Engelacc8dad2006-04-10 22:54:17 -0700178config MTD_BLOCK2MTD
179 tristate "MTD using block device"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500180 depends on BLOCK
Linus Torvalds1da177e2005-04-16 15:20:36 -0700181 help
182 This driver allows a block device to appear as an MTD. It would
183 generally be used in the following cases:
184
185 Using Compact Flash as an MTD, these usually present themselves to
186 the system as an ATA drive.
187 Testing MTD users (eg JFFS2) on large media and media that might
188 be removed during a write (using the floppy drive).
189
Linus Torvalds1da177e2005-04-16 15:20:36 -0700190comment "Disk-On-Chip Device Drivers"
191
192config MTD_DOC2000
193 tristate "M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED)"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700194 select MTD_DOCPROBE
195 select MTD_NAND_IDS
196 ---help---
197 This provides an MTD device driver for the M-Systems DiskOnChip
198 2000 and Millennium devices. Originally designed for the DiskOnChip
199 2000, it also now includes support for the DiskOnChip Millennium.
200 If you have problems with this driver and the DiskOnChip Millennium,
201 you may wish to try the alternative Millennium driver below. To use
202 the alternative driver, you will need to undefine DOC_SINGLE_DRIVER
203 in the <file:drivers/mtd/devices/docprobe.c> source code.
204
205 If you use this device, you probably also want to enable the NFTL
206 'NAND Flash Translation Layer' option below, which is used to
207 emulate a block device by using a kind of file system on the flash
208 chips.
209
210 NOTE: This driver is deprecated and will probably be removed soon.
211 Please try the new DiskOnChip driver under "NAND Flash Device
212 Drivers".
213
214config MTD_DOC2001
215 tristate "M-Systems Disk-On-Chip Millennium-only alternative driver (DEPRECATED)"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700216 select MTD_DOCPROBE
217 select MTD_NAND_IDS
218 ---help---
Thomas Gleixnere5580fb2005-11-07 11:15:40 +0000219 This provides an alternative MTD device driver for the M-Systems
Linus Torvalds1da177e2005-04-16 15:20:36 -0700220 DiskOnChip Millennium devices. Use this if you have problems with
221 the combined DiskOnChip 2000 and Millennium driver above. To get
222 the DiskOnChip probe code to load and use this driver instead of
223 the other one, you will need to undefine DOC_SINGLE_DRIVER near
224 the beginning of <file:drivers/mtd/devices/docprobe.c>.
225
226 If you use this device, you probably also want to enable the NFTL
227 'NAND Flash Translation Layer' option below, which is used to
228 emulate a block device by using a kind of file system on the flash
229 chips.
230
231 NOTE: This driver is deprecated and will probably be removed soon.
232 Please try the new DiskOnChip driver under "NAND Flash Device
233 Drivers".
234
235config MTD_DOC2001PLUS
236 tristate "M-Systems Disk-On-Chip Millennium Plus"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700237 select MTD_DOCPROBE
238 select MTD_NAND_IDS
239 ---help---
240 This provides an MTD device driver for the M-Systems DiskOnChip
241 Millennium Plus devices.
242
243 If you use this device, you probably also want to enable the INFTL
244 'Inverse NAND Flash Translation Layer' option below, which is used
Thomas Gleixnere5580fb2005-11-07 11:15:40 +0000245 to emulate a block device by using a kind of file system on the
Linus Torvalds1da177e2005-04-16 15:20:36 -0700246 flash chips.
247
248 NOTE: This driver will soon be replaced by the new DiskOnChip driver
249 under "NAND Flash Device Drivers" (currently that driver does not
250 support all Millennium Plus devices).
251
252config MTD_DOCPROBE
253 tristate
254 select MTD_DOCECC
Linus Torvalds1da177e2005-04-16 15:20:36 -0700255
256config MTD_DOCECC
257 tristate
258
259config MTD_DOCPROBE_ADVANCED
260 bool "Advanced detection options for DiskOnChip"
261 depends on MTD_DOCPROBE
262 help
263 This option allows you to specify nonstandard address at which to
264 probe for a DiskOnChip, or to change the detection options. You
265 are unlikely to need any of this unless you are using LinuxBIOS.
266 Say 'N'.
267
268config MTD_DOCPROBE_ADDRESS
269 hex "Physical address of DiskOnChip" if MTD_DOCPROBE_ADVANCED
270 depends on MTD_DOCPROBE
271 default "0x0000" if MTD_DOCPROBE_ADVANCED
272 default "0" if !MTD_DOCPROBE_ADVANCED
273 ---help---
274 By default, the probe for DiskOnChip devices will look for a
275 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
276 This option allows you to specify a single address at which to probe
277 for the device, which is useful if you have other devices in that
278 range which get upset when they are probed.
279
280 (Note that on PowerPC, the normal probe will only check at
281 0xE4000000.)
282
283 Normally, you should leave this set to zero, to allow the probe at
284 the normal addresses.
285
286config MTD_DOCPROBE_HIGH
287 bool "Probe high addresses"
288 depends on MTD_DOCPROBE_ADVANCED
289 help
290 By default, the probe for DiskOnChip devices will look for a
291 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
292 This option changes to make it probe between 0xFFFC8000 and
293 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
294 useful to you. Say 'N'.
295
296config MTD_DOCPROBE_55AA
297 bool "Probe for 0x55 0xAA BIOS Extension Signature"
298 depends on MTD_DOCPROBE_ADVANCED
299 help
300 Check for the 0x55 0xAA signature of a DiskOnChip, and do not
301 continue with probing if it is absent. The signature will always be
302 present for a DiskOnChip 2000 or a normal DiskOnChip Millennium.
303 Only if you have overwritten the first block of a DiskOnChip
304 Millennium will it be absent. Enable this option if you are using
305 LinuxBIOS or if you need to recover a DiskOnChip Millennium on which
306 you have managed to wipe the first block.
307
308endmenu