blob: e0f0c0609f8173772a8f4105c829ba665a03fc34 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001menu "Self-contained MTD device drivers"
2 depends on MTD!=n
Richard Weinberger9310da02012-02-07 01:22:50 +01003 depends on HAS_IOMEM
Linus Torvalds1da177e2005-04-16 15:20:36 -07004
5config MTD_PMC551
6 tristate "Ramix PMC551 PCI Mezzanine RAM card support"
Jan Engelhardtec98c682007-04-19 16:21:41 -05007 depends on PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -07008 ---help---
9 This provides a MTD device driver for the Ramix PMC551 RAM PCI card
10 from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.
11 These devices come in memory configurations from 32M - 1G. If you
12 have one, you probably want to enable this.
13
14 If this driver is compiled as a module you get the ability to select
15 the size of the aperture window pointing into the devices memory.
16 What this means is that if you have a 1G card, normally the kernel
17 will use a 1G memory map as its view of the device. As a module,
18 you can select a 1M window into the memory and the driver will
19 "slide" the window around the PMC551's memory. This was
20 particularly useful on the 2.2 kernels on PPC architectures as there
21 was limited kernel space to deal with.
22
23config MTD_PMC551_BUGFIX
24 bool "PMC551 256M DRAM Bugfix"
25 depends on MTD_PMC551
26 help
27 Some of Ramix's PMC551 boards with 256M configurations have invalid
28 column and row mux values. This option will fix them, but will
29 break other memory configurations. If unsure say N.
30
31config MTD_PMC551_DEBUG
32 bool "PMC551 Debugging"
33 depends on MTD_PMC551
34 help
35 This option makes the PMC551 more verbose during its operation and
36 is only really useful if you are developing on this driver or
37 suspect a possible hardware or driver bug. If unsure say N.
38
39config MTD_MS02NV
40 tristate "DEC MS02-NV NVRAM module support"
Jan Engelhardtec98c682007-04-19 16:21:41 -050041 depends on MACH_DECSTATION
Linus Torvalds1da177e2005-04-16 15:20:36 -070042 help
43 This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
44 backed-up NVRAM module. The module was originally meant as an NFS
45 accelerator. Say Y here if you have a DECstation 5000/2x0 or a
46 DECsystem 5900 equipped with such a module.
47
Martin Michlmayrbe21ce12006-03-20 04:40:26 +000048 If you want to compile this driver as a module ( = code which can be
49 inserted in and removed from the running kernel whenever you want),
Alexander E. Patrakov39f5fb32007-03-16 18:28:43 +050050 say M here and read <file:Documentation/kbuild/modules.txt>.
Pavel Machek4737f092009-06-05 00:44:53 +020051 The module will be called ms02-nv.
Martin Michlmayrbe21ce12006-03-20 04:40:26 +000052
Sahitya Tummala3f3f2f92017-06-05 09:03:42 +053053config MTD_MSM_QPIC_NAND
54 tristate "MSM QPIC NAND Device Support"
Sahitya Tummalac15eb762017-06-06 14:52:41 +053055 depends on MTD && (ARCH_QCOM || ARCH_MSM) && !MTD_MSM_NAND
Sahitya Tummala3f3f2f92017-06-05 09:03:42 +053056 select CRC16
57 select BITREVERSE
58 select MTD_NAND_IDS
59 default n
60 help
61 Support for NAND controller in Qualcomm Technologies, Inc.
62 Parallel Interface controller (QPIC). This new controller
63 supports BAM mode and BCH error correction mechanism. Based on the
64 device capabilities either 4 bit or 8 bit BCH ECC will be used.
65
David Brownell1d6432f2006-01-08 13:34:22 -080066config MTD_DATAFLASH
67 tristate "Support for AT45xxx DataFlash"
Kees Cooka11ed372012-10-02 11:17:51 -070068 depends on SPI_MASTER
David Brownell1d6432f2006-01-08 13:34:22 -080069 help
70 This enables access to AT45xxx DataFlash chips, using SPI.
71 Sometimes DataFlash chips are packaged inside MMC-format
72 cards; at this writing, the MMC stack won't handle those.
73
David Brownell8c640382008-08-06 21:55:14 -070074config MTD_DATAFLASH_WRITE_VERIFY
75 bool "Verify DataFlash page writes"
76 depends on MTD_DATAFLASH
77 help
78 This adds an extra check when data is written to the flash.
79 It may help if you are verifying chip setup (timings etc) on
80 your board. There is a rare possibility that even though the
81 device thinks the write was successful, a bit could have been
82 flipped accidentally due to device wear or something else.
83
David Brownell34a82442008-07-30 12:35:05 -070084config MTD_DATAFLASH_OTP
85 bool "DataFlash OTP support (Security Register)"
86 depends on MTD_DATAFLASH
David Brownell34a82442008-07-30 12:35:05 -070087 help
88 Newer DataFlash chips (revisions C and D) support 128 bytes of
89 one-time-programmable (OTP) data. The first half may be written
90 (once) with up to 64 bytes of data, such as a serial number or
91 other key product data. The second half is programmed with a
92 unique-to-each-chip bit pattern at the factory.
93
Mike Lavender2f9f7622006-01-08 13:34:27 -080094config MTD_M25P80
David Brownellfa0a8c72007-06-24 15:12:35 -070095 tristate "Support most SPI Flash chips (AT26DF, M25P, W25X, ...)"
Brian Norrise43b2062014-04-08 20:30:25 -070096 depends on SPI_MASTER && MTD_SPI_NOR
Mike Lavender2f9f7622006-01-08 13:34:27 -080097 help
David Brownellfa0a8c72007-06-24 15:12:35 -070098 This enables access to most modern SPI flash chips, used for
99 program and data storage. Series supported include Atmel AT26DF,
100 Spansion S25SL, SST 25VF, ST M25P, and Winbond W25X. Other chips
101 are supported as well. See the driver source for the current list,
102 or to add other chips.
103
104 Note that the original DataFlash chips (AT45 series, not AT26DF),
105 need an entirely different driver.
106
107 Set up your spi devices with the right board-specific platform data,
108 if you want to specify device partitioning or to use a device which
109 doesn't support the JEDEC ID instruction.
Mike Lavender2f9f7622006-01-08 13:34:27 -0800110
Shiraz Hashimf18dbbb2012-01-12 14:38:57 +0100111config MTD_SPEAR_SMI
112 tristate "SPEAR MTD NOR Support through SMI controller"
113 depends on PLAT_SPEAR
114 default y
115 help
116 This enable SNOR support on SPEAR platforms using SMI controller
117
Ryan Mallonec77e212009-09-18 12:51:40 -0700118config MTD_SST25L
119 tristate "Support SST25L (non JEDEC) SPI Flash chips"
120 depends on SPI_MASTER
121 help
122 This enables access to the non JEDEC SST25L SPI flash chips, used
123 for program and data storage.
124
125 Set up your spi devices with the right board-specific platform data,
126 if you want to specify device partitioning.
127
Rafał Miłecki5fe42d52012-09-17 11:50:49 +0200128config MTD_BCM47XXSFLASH
Rafał Miłecki0a526342016-07-18 12:07:03 +0200129 tristate "Support for serial flash on BCMA bus"
Rafał Miłeckiefacc692016-07-19 09:08:32 +0200130 depends on BCMA_SFLASH && (MIPS || ARM)
Rafał Miłecki5fe42d52012-09-17 11:50:49 +0200131 help
132 BCMA bus can have various flash memories attached, they are
133 registered by bcma as platform devices. This enables driver for
Rafał Miłecki0a526342016-07-18 12:07:03 +0200134 serial flash memories.
Rafał Miłecki5fe42d52012-09-17 11:50:49 +0200135
Linus Torvalds1da177e2005-04-16 15:20:36 -0700136config MTD_SLRAM
137 tristate "Uncached system RAM"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700138 help
139 If your CPU cannot cache all of the physical memory in your machine,
140 you can still use it for storage or swap by using this driver to
141 present it to the system as a Memory Technology Device.
142
143config MTD_PHRAM
144 tristate "Physical system RAM"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700145 help
146 This is a re-implementation of the slram driver above.
147
148 Use this driver to access physical memory that the kernel proper
149 doesn't have access to, memory beyond the mem=xxx limit, nvram,
150 memory on the video card, etc...
151
152config MTD_LART
153 tristate "28F160xx flash driver for LART"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500154 depends on SA1100_LART
Linus Torvalds1da177e2005-04-16 15:20:36 -0700155 help
156 This enables the flash driver for LART. Please note that you do
157 not need any mapping/chip driver for LART. This one does it all
158 for you, so go disable all of those if you enabled some of them (:
159
160config MTD_MTDRAM
161 tristate "Test driver using RAM"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700162 help
163 This enables a test MTD device driver which uses vmalloc() to
164 provide storage. You probably want to say 'N' unless you're
165 testing stuff.
166
167config MTDRAM_TOTAL_SIZE
168 int "MTDRAM device size in KiB"
169 depends on MTD_MTDRAM
170 default "4096"
171 help
172 This allows you to configure the total size of the MTD device
173 emulated by the MTDRAM driver. If the MTDRAM driver is built
174 as a module, it is also possible to specify this as a parameter when
175 loading the module.
176
177config MTDRAM_ERASE_SIZE
178 int "MTDRAM erase block size in KiB"
179 depends on MTD_MTDRAM
180 default "128"
181 help
182 This allows you to configure the size of the erase blocks in the
183 device emulated by the MTDRAM driver. If the MTDRAM driver is built
184 as a module, it is also possible to specify this as a parameter when
185 loading the module.
186
Joern Engelacc8dad2006-04-10 22:54:17 -0700187config MTD_BLOCK2MTD
188 tristate "MTD using block device"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500189 depends on BLOCK
Linus Torvalds1da177e2005-04-16 15:20:36 -0700190 help
191 This driver allows a block device to appear as an MTD. It would
192 generally be used in the following cases:
193
194 Using Compact Flash as an MTD, these usually present themselves to
195 the system as an ATA drive.
196 Testing MTD users (eg JFFS2) on large media and media that might
197 be removed during a write (using the floppy drive).
198
Cyril Bur1cbb4a12015-06-02 14:26:09 +1000199config MTD_POWERNV_FLASH
200 tristate "powernv flash MTD driver"
201 depends on PPC_POWERNV
202 help
203 This provides an MTD device to access flash on powernv OPAL
204 platforms from Linux. This device abstracts away the
205 firmware interface for flash access.
206
Linus Torvalds1da177e2005-04-16 15:20:36 -0700207comment "Disk-On-Chip Device Drivers"
208
Robert Jarzmikefa2ca72011-10-05 15:22:34 +0200209config MTD_DOCG3
210 tristate "M-Systems Disk-On-Chip G3"
Robert Jarzmikd13d19e2011-11-19 16:02:55 +0100211 select BCH
212 select BCH_CONST_PARAMS
Robert Jarzmikbf65aaa2013-01-14 20:01:37 +0100213 select BITREVERSE
Robert Jarzmikefa2ca72011-10-05 15:22:34 +0200214 ---help---
215 This provides an MTD device driver for the M-Systems DiskOnChip
216 G3 devices.
217
218 The driver provides access to G3 DiskOnChip, distributed by
219 M-Systems and now Sandisk. The support is very experimental,
220 and doesn't give access to any write operations.
221
Lee Jonesd90db4a2014-03-20 09:20:33 +0000222config MTD_ST_SPI_FSM
223 tristate "ST Microelectronics SPI FSM Serial Flash Controller"
Brian Norrisdc002f92014-04-16 01:40:17 -0700224 depends on ARCH_STI
Lee Jonesd90db4a2014-03-20 09:20:33 +0000225 help
226 This provides an MTD device driver for the ST Microelectronics
227 SPI Fast Sequence Mode (FSM) Serial Flash Controller and support
228 for a subset of connected Serial Flash devices.
229
Robert Jarzmikd13d19e2011-11-19 16:02:55 +0100230if MTD_DOCG3
231config BCH_CONST_M
232 default 14
233config BCH_CONST_T
234 default 4
235endif
236
Linus Torvalds1da177e2005-04-16 15:20:36 -0700237endmenu