blob: 27143e042af5b2dfec767a1d1cf61762fcf2734b [file] [log] [blame]
Jan Engelhardtec98c682007-04-19 16:21:41 -05001menuconfig MTD
Linus Torvalds1da177e2005-04-16 15:20:36 -07002 tristate "Memory Technology Device (MTD) support"
Richard Weinberger9310da02012-02-07 01:22:50 +01003 depends on GENERIC_IO
Linus Torvalds1da177e2005-04-16 15:20:36 -07004 help
5 Memory Technology Devices are flash, RAM and similar chips, often
6 used for solid state file systems on embedded devices. This option
7 will provide the generic support for MTD drivers to register
8 themselves with the kernel and for potential users of MTD devices
9 to enumerate the devices which are present and obtain a handle on
Thomas Gleixner97894cd2005-11-07 11:15:26 +000010 them. It will also allow you to select individual drivers for
Linus Torvalds1da177e2005-04-16 15:20:36 -070011 particular hardware and users of MTD devices. If unsure, say N.
12
Jan Engelhardtec98c682007-04-19 16:21:41 -050013if MTD
14
Mike Frysinger80f53da2009-06-13 06:15:18 -040015config MTD_TESTS
Wolfram Sang48e546b2011-10-30 17:28:49 +010016 tristate "MTD tests support (DANGEROUS)"
Mike Frysinger80f53da2009-06-13 06:15:18 -040017 depends on m
18 help
19 This option includes various MTD tests into compilation. The tests
20 should normally be compiled as kernel modules. The modules perform
21 various checks and verifications when loaded.
22
Wolfram Sang48e546b2011-10-30 17:28:49 +010023 WARNING: some of the tests will ERASE entire MTD device which they
24 test. Do not use these tests unless you really know what you do.
25
Linus Torvalds1da177e2005-04-16 15:20:36 -070026config MTD_REDBOOT_PARTS
27 tristate "RedBoot partition table parsing"
Linus Torvalds1da177e2005-04-16 15:20:36 -070028 ---help---
29 RedBoot is a ROM monitor and bootloader which deals with multiple
30 'images' in flash devices by putting a table one of the erase
31 blocks on the device, similar to a partition table, which gives
32 the offsets, lengths and names of all the images stored in the
33 flash.
34
35 If you need code which can detect and parse this table, and register
36 MTD 'partitions' corresponding to each image in the table, enable
Thomas Gleixner97894cd2005-11-07 11:15:26 +000037 this option.
Linus Torvalds1da177e2005-04-16 15:20:36 -070038
39 You will still need the parsing functions to be called by the driver
Thomas Gleixner97894cd2005-11-07 11:15:26 +000040 for your particular device. It won't happen automatically. The
41 SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
Linus Torvalds1da177e2005-04-16 15:20:36 -070042 example.
43
Grant Likelyb7b6e082010-10-30 07:35:02 +010044if MTD_REDBOOT_PARTS
45
Linus Torvalds1da177e2005-04-16 15:20:36 -070046config MTD_REDBOOT_DIRECTORY_BLOCK
47 int "Location of RedBoot partition table"
Linus Torvalds1da177e2005-04-16 15:20:36 -070048 default "-1"
49 ---help---
50 This option is the Linux counterpart to the
51 CYGNUM_REDBOOT_FIS_DIRECTORY_BLOCK RedBoot compile time
52 option.
53
54 The option specifies which Flash sectors holds the RedBoot
Egry Gábor4992a9e2006-05-12 17:35:02 +010055 partition table. A zero or positive value gives an absolute
Linus Torvalds1da177e2005-04-16 15:20:36 -070056 erase block number. A negative value specifies a number of
57 sectors before the end of the device.
Thomas Gleixner97894cd2005-11-07 11:15:26 +000058
Linus Torvalds1da177e2005-04-16 15:20:36 -070059 For example "2" means block number 2, "-1" means the last
60 block and "-2" means the penultimate block.
Thomas Gleixner97894cd2005-11-07 11:15:26 +000061
Linus Torvalds1da177e2005-04-16 15:20:36 -070062config MTD_REDBOOT_PARTS_UNALLOCATED
Roman Zippele55a3e82006-06-08 22:12:49 -070063 bool "Include unallocated flash regions"
Linus Torvalds1da177e2005-04-16 15:20:36 -070064 help
65 If you need to register each unallocated flash region as a MTD
66 'partition', enable this option.
67
68config MTD_REDBOOT_PARTS_READONLY
Roman Zippele55a3e82006-06-08 22:12:49 -070069 bool "Force read-only for RedBoot system images"
Linus Torvalds1da177e2005-04-16 15:20:36 -070070 help
71 If you need to force read-only for 'RedBoot', 'RedBoot Config' and
72 'FIS directory' images, enable this option.
73
Grant Likelyb7b6e082010-10-30 07:35:02 +010074endif # MTD_REDBOOT_PARTS
75
Linus Torvalds1da177e2005-04-16 15:20:36 -070076config MTD_CMDLINE_PARTS
77 bool "Command line partition table parsing"
Jamie Iles6a8a98b2011-05-23 10:23:43 +010078 depends on MTD = "y"
Linus Torvalds1da177e2005-04-16 15:20:36 -070079 ---help---
Egry Gábor4992a9e2006-05-12 17:35:02 +010080 Allow generic configuration of the MTD partition tables via the kernel
Linus Torvalds1da177e2005-04-16 15:20:36 -070081 command line. Multiple flash resources are supported for hardware where
Thomas Gleixner97894cd2005-11-07 11:15:26 +000082 different kinds of flash memory are available.
Linus Torvalds1da177e2005-04-16 15:20:36 -070083
84 You will still need the parsing functions to be called by the driver
Thomas Gleixner97894cd2005-11-07 11:15:26 +000085 for your particular device. It won't happen automatically. The
86 SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
Linus Torvalds1da177e2005-04-16 15:20:36 -070087 example.
88
89 The format for the command line is as follows:
90
91 mtdparts=<mtddef>[;<mtddef]
92 <mtddef> := <mtd-id>:<partdef>[,<partdef>]
93 <partdef> := <size>[@offset][<name>][ro]
94 <mtd-id> := unique id used in mapping driver/device
Thomas Gleixner97894cd2005-11-07 11:15:26 +000095 <size> := standard linux memsize OR "-" to denote all
Linus Torvalds1da177e2005-04-16 15:20:36 -070096 remaining space
97 <name> := (NAME)
98
Thomas Gleixner97894cd2005-11-07 11:15:26 +000099 Due to the way Linux handles the command line, no spaces are
100 allowed in the partition definition, including mtd id's and partition
Linus Torvalds1da177e2005-04-16 15:20:36 -0700101 names.
102
103 Examples:
104
105 1 flash resource (mtd-id "sa1100"), with 1 single writable partition:
106 mtdparts=sa1100:-
107
108 Same flash, but 2 named partitions, the first one being read-only:
109 mtdparts=sa1100:256k(ARMboot)ro,-(root)
110
111 If unsure, say 'N'.
112
113config MTD_AFS_PARTS
114 tristate "ARM Firmware Suite partition parsing"
Grant Likelyb7b6e082010-10-30 07:35:02 +0100115 depends on ARM
Linus Torvalds1da177e2005-04-16 15:20:36 -0700116 ---help---
117 The ARM Firmware Suite allows the user to divide flash devices into
118 multiple 'images'. Each such image has a header containing its name
119 and offset/size etc.
120
121 If you need code which can detect and parse these tables, and
122 register MTD 'partitions' corresponding to each image detected,
123 enable this option.
124
125 You will still need the parsing functions to be called by the driver
126 for your particular device. It won't happen automatically. The
Marc Zyngieradf00402011-05-18 10:51:54 +0100127 'physmap' map driver (CONFIG_MTD_PHYSMAP) does this, for example.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700128
Scott Wood9a310d22008-01-15 17:54:43 -0600129config MTD_OF_PARTS
Dmitry Eremin-Solenikovd6137ba2011-06-27 01:02:59 +0400130 tristate "OpenFirmware partitioning information support"
Frank Svendsboe2e929d02012-05-17 22:43:09 +0200131 default y
Grant Likelyb7b6e082010-10-30 07:35:02 +0100132 depends on OF
Scott Wood9a310d22008-01-15 17:54:43 -0600133 help
134 This provides a partition parsing function which derives
135 the partition map from the children of the flash node,
Paul Bolle395cf962011-08-15 02:02:26 +0200136 as described in Documentation/devicetree/booting-without-of.txt.
Scott Wood9a310d22008-01-15 17:54:43 -0600137
Matteo Crocef0797882008-03-12 02:25:06 +0100138config MTD_AR7_PARTS
139 tristate "TI AR7 partitioning support"
Matteo Crocef0797882008-03-12 02:25:06 +0100140 ---help---
141 TI AR7 partitioning support
142
Jonas Gorski70a3c162011-12-05 16:08:08 +0100143config MTD_BCM63XX_PARTS
144 tristate "BCM63XX CFE partitioning support"
145 depends on BCM63XX
146 select CRC32
147 help
148 This provides partions parsing for BCM63xx devices with CFE
149 bootloaders.
150
Linus Torvalds1da177e2005-04-16 15:20:36 -0700151comment "User Modules And Translation Layers"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700152
153config MTD_CHAR
154 tristate "Direct char device access to MTD devices"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700155 help
156 This provides a character device for each MTD device present in
157 the system, allowing the user to read and write directly to the
158 memory chips, and also use ioctl() to obtain information about
159 the device, or to erase parts of it.
160
David Brownell34a82442008-07-30 12:35:05 -0700161config HAVE_MTD_OTP
162 bool
163 help
164 Enable access to OTP regions using MTD_CHAR.
165
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600166config MTD_BLKDEVS
167 tristate "Common interface to block layer for MTD 'translation layers'"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500168 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600169 default n
170
Linus Torvalds1da177e2005-04-16 15:20:36 -0700171config MTD_BLOCK
172 tristate "Caching block device access to MTD devices"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500173 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600174 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700175 ---help---
176 Although most flash chips have an erase size too large to be useful
177 as block devices, it is possible to use MTD devices which are based
178 on RAM chips in this manner. This block device is a user of MTD
179 devices performing that function.
180
181 At the moment, it is also required for the Journalling Flash File
182 System(s) to obtain a handle on the MTD device when it's mounted
183 (although JFFS and JFFS2 don't actually use any of the functionality
184 of the mtdblock device).
185
186 Later, it may be extended to perform read/erase/modify/write cycles
187 on flash chips to emulate a smaller block size. Needless to say,
188 this is very unsafe, but could be useful for file systems which are
189 almost never written to.
190
191 You do not need this option for use with the DiskOnChip devices. For
192 those, enable NFTL support (CONFIG_NFTL) instead.
193
194config MTD_BLOCK_RO
195 tristate "Readonly block device access to MTD devices"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500196 depends on MTD_BLOCK!=y && BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600197 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700198 help
199 This allows you to mount read-only file systems (such as cramfs)
200 from an MTD device, without the overhead (and danger) of the caching
201 driver.
202
203 You do not need this option for use with the DiskOnChip devices. For
204 those, enable NFTL support (CONFIG_NFTL) instead.
205
206config FTL
207 tristate "FTL (Flash Translation Layer) support"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500208 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600209 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700210 ---help---
211 This provides support for the original Flash Translation Layer which
212 is part of the PCMCIA specification. It uses a kind of pseudo-
213 file system on a flash device to emulate a block device with
214 512-byte sectors, on top of which you put a 'normal' file system.
215
216 You may find that the algorithms used in this code are patented
217 unless you live in the Free World where software patents aren't
218 legal - in the USA you are only permitted to use this on PCMCIA
219 hardware, although under the terms of the GPL you're obviously
220 permitted to copy, modify and distribute the code as you wish. Just
221 not use it.
222
223config NFTL
224 tristate "NFTL (NAND Flash Translation Layer) support"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500225 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600226 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700227 ---help---
228 This provides support for the NAND Flash Translation Layer which is
229 used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
230 file system on a flash device to emulate a block device with
231 512-byte sectors, on top of which you put a 'normal' file system.
232
233 You may find that the algorithms used in this code are patented
234 unless you live in the Free World where software patents aren't
235 legal - in the USA you are only permitted to use this on DiskOnChip
236 hardware, although under the terms of the GPL you're obviously
237 permitted to copy, modify and distribute the code as you wish. Just
238 not use it.
239
240config NFTL_RW
241 bool "Write support for NFTL"
242 depends on NFTL
243 help
244 Support for writing to the NAND Flash Translation Layer, as used
245 on the DiskOnChip.
246
247config INFTL
248 tristate "INFTL (Inverse NAND Flash Translation Layer) support"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500249 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600250 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700251 ---help---
Thomas Gleixner97894cd2005-11-07 11:15:26 +0000252 This provides support for the Inverse NAND Flash Translation
Linus Torvalds1da177e2005-04-16 15:20:36 -0700253 Layer which is used on M-Systems' newer DiskOnChip devices. It
254 uses a kind of pseudo-file system on a flash device to emulate
255 a block device with 512-byte sectors, on top of which you put
256 a 'normal' file system.
257
258 You may find that the algorithms used in this code are patented
259 unless you live in the Free World where software patents aren't
260 legal - in the USA you are only permitted to use this on DiskOnChip
261 hardware, although under the terms of the GPL you're obviously
262 permitted to copy, modify and distribute the code as you wish. Just
263 not use it.
264
Sean Younge27a9962005-06-16 09:49:33 +0100265config RFD_FTL
266 tristate "Resident Flash Disk (Flash Translation Layer) support"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500267 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600268 select MTD_BLKDEVS
Sean Younge27a9962005-06-16 09:49:33 +0100269 ---help---
Thomas Gleixner97894cd2005-11-07 11:15:26 +0000270 This provides support for the flash translation layer known
271 as the Resident Flash Disk (RFD), as used by the Embedded BIOS
Kyungmin Parkcd5f6342005-07-11 11:41:53 +0100272 of General Software. There is a blurb at:
273
274 http://www.gensw.com/pages/prod/bios/rfd.htm
Sean Younge27a9962005-06-16 09:49:33 +0100275
Claudio Lanconelli51197ab2006-09-22 11:01:37 +0100276config SSFDC
David Woodhouse892e4fb2006-09-23 10:24:36 +0100277 tristate "NAND SSFDC (SmartMedia) read only translation layer"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500278 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600279 select MTD_BLKDEVS
Claudio Lanconelli51197ab2006-09-22 11:01:37 +0100280 help
281 This enables read only access to SmartMedia formatted NAND
282 flash. You can mount it with FAT file system.
283
Maxim Levitsky7d17c022010-02-22 20:39:41 +0200284
285config SM_FTL
286 tristate "SmartMedia/xD new translation layer"
Maxim Levitskye5f710c2010-03-19 17:22:54 +0200287 depends on EXPERIMENTAL && BLOCK
Maxim Levitsky7d17c022010-02-22 20:39:41 +0200288 select MTD_BLKDEVS
Maxim Levitskye5f710c2010-03-19 17:22:54 +0200289 select MTD_NAND_ECC
Maxim Levitsky7d17c022010-02-22 20:39:41 +0200290 help
Maxim Levitsky6f923552010-07-28 18:53:17 +0300291 This enables EXPERIMENTAL R/W support for SmartMedia/xD
David Woodhouse7de6f792010-03-08 18:45:00 -0800292 FTL (Flash translation layer).
Maxim Levitsky6f923552010-07-28 18:53:17 +0300293 Write support is only lightly tested, therefore this driver
294 isn't recommended to use with valuable data (anyway if you have
295 valuable data, do backups regardless of software/hardware you
296 use, because you never know what will eat your data...)
297 If you only need R/O access, you can use older R/O driver
298 (CONFIG_SSFDC)
Maxim Levitsky7d17c022010-02-22 20:39:41 +0200299
Richard Purdie4b23aff2007-05-29 13:31:42 +0100300config MTD_OOPS
301 tristate "Log panic/oops to an MTD buffer"
Richard Purdie4b23aff2007-05-29 13:31:42 +0100302 help
303 This enables panic and oops messages to be logged to a circular
304 buffer in a flash partition where it can be read back at some
305 later point.
306
Jarkko Lavinena3215902011-02-14 16:16:11 +0200307config MTD_SWAP
308 tristate "Swap on MTD device support"
309 depends on MTD && SWAP
310 select MTD_BLKDEVS
311 help
312 Provides volatile block device driver on top of mtd partition
313 suitable for swapping. The mapping of written blocks is not saved.
314 The driver provides wear leveling by storing erase counter into the
315 OOB.
316
Linus Torvalds1da177e2005-04-16 15:20:36 -0700317source "drivers/mtd/chips/Kconfig"
318
319source "drivers/mtd/maps/Kconfig"
320
321source "drivers/mtd/devices/Kconfig"
322
323source "drivers/mtd/nand/Kconfig"
324
Kyungmin Parkcd5f6342005-07-11 11:41:53 +0100325source "drivers/mtd/onenand/Kconfig"
326
Alexey Korolev60f26522008-12-16 18:24:14 +0000327source "drivers/mtd/lpddr/Kconfig"
328
Artem B. Bityutskiy801c1352006-06-27 12:22:22 +0400329source "drivers/mtd/ubi/Kconfig"
330
Jan Engelhardtec98c682007-04-19 16:21:41 -0500331endif # MTD