blob: a03ad2951c7b423975c566dfce20902b7fd074f0 [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
Lubomir Rintelf5f172d2013-01-16 02:12:49 +010077 tristate "Command line partition table parsing"
78 depends on MTD
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,
Michal Sojkae7606442014-10-10 15:06:17 +0200136 as described in Documentation/devicetree/bindings/mtd/partition.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
Rafał Miłecki3cf7f132012-08-30 07:41:16 +0200151config MTD_BCM47XX_PARTS
152 tristate "BCM47XX partitioning support"
Rafał Miłecki9e3afa52014-02-28 18:02:01 +0100153 depends on BCM47XX || ARCH_BCM_5301X
Rafał Miłecki3cf7f132012-08-30 07:41:16 +0200154 help
155 This provides partitions parser for devices based on BCM47xx
156 boards.
157
Linus Torvalds1da177e2005-04-16 15:20:36 -0700158comment "User Modules And Translation Layers"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700159
Ezequiel Garcia7f11b4d2013-12-13 10:58:44 -0300160#
161# MTD block device support is select'ed if needed
162#
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600163config MTD_BLKDEVS
Ezequiel Garcia7f11b4d2013-12-13 10:58:44 -0300164 tristate
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600165
Linus Torvalds1da177e2005-04-16 15:20:36 -0700166config MTD_BLOCK
167 tristate "Caching block device access to MTD devices"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500168 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600169 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700170 ---help---
171 Although most flash chips have an erase size too large to be useful
172 as block devices, it is possible to use MTD devices which are based
173 on RAM chips in this manner. This block device is a user of MTD
174 devices performing that function.
175
176 At the moment, it is also required for the Journalling Flash File
177 System(s) to obtain a handle on the MTD device when it's mounted
178 (although JFFS and JFFS2 don't actually use any of the functionality
179 of the mtdblock device).
180
181 Later, it may be extended to perform read/erase/modify/write cycles
182 on flash chips to emulate a smaller block size. Needless to say,
183 this is very unsafe, but could be useful for file systems which are
184 almost never written to.
185
186 You do not need this option for use with the DiskOnChip devices. For
187 those, enable NFTL support (CONFIG_NFTL) instead.
188
189config MTD_BLOCK_RO
190 tristate "Readonly block device access to MTD devices"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500191 depends on MTD_BLOCK!=y && BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600192 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700193 help
194 This allows you to mount read-only file systems (such as cramfs)
195 from an MTD device, without the overhead (and danger) of the caching
196 driver.
197
198 You do not need this option for use with the DiskOnChip devices. For
199 those, enable NFTL support (CONFIG_NFTL) instead.
200
201config FTL
202 tristate "FTL (Flash Translation Layer) support"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500203 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600204 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700205 ---help---
206 This provides support for the original Flash Translation Layer which
207 is part of the PCMCIA specification. It uses a kind of pseudo-
208 file system on a flash device to emulate a block device with
209 512-byte sectors, on top of which you put a 'normal' file system.
210
211 You may find that the algorithms used in this code are patented
212 unless you live in the Free World where software patents aren't
213 legal - in the USA you are only permitted to use this on PCMCIA
214 hardware, although under the terms of the GPL you're obviously
215 permitted to copy, modify and distribute the code as you wish. Just
216 not use it.
217
218config NFTL
219 tristate "NFTL (NAND Flash Translation Layer) support"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500220 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600221 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700222 ---help---
223 This provides support for the NAND Flash Translation Layer which is
224 used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
225 file system on a flash device to emulate a block device with
226 512-byte sectors, on top of which you put a 'normal' file system.
227
228 You may find that the algorithms used in this code are patented
229 unless you live in the Free World where software patents aren't
230 legal - in the USA you are only permitted to use this on DiskOnChip
231 hardware, although under the terms of the GPL you're obviously
232 permitted to copy, modify and distribute the code as you wish. Just
233 not use it.
234
235config NFTL_RW
236 bool "Write support for NFTL"
237 depends on NFTL
238 help
239 Support for writing to the NAND Flash Translation Layer, as used
240 on the DiskOnChip.
241
242config INFTL
243 tristate "INFTL (Inverse NAND Flash Translation Layer) support"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500244 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600245 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700246 ---help---
Thomas Gleixner97894cd2005-11-07 11:15:26 +0000247 This provides support for the Inverse NAND Flash Translation
Linus Torvalds1da177e2005-04-16 15:20:36 -0700248 Layer which is used on M-Systems' newer DiskOnChip devices. It
249 uses a kind of pseudo-file system on a flash device to emulate
250 a block device with 512-byte sectors, on top of which you put
251 a 'normal' file system.
252
253 You may find that the algorithms used in this code are patented
254 unless you live in the Free World where software patents aren't
255 legal - in the USA you are only permitted to use this on DiskOnChip
256 hardware, although under the terms of the GPL you're obviously
257 permitted to copy, modify and distribute the code as you wish. Just
258 not use it.
259
Sean Younge27a9962005-06-16 09:49:33 +0100260config RFD_FTL
261 tristate "Resident Flash Disk (Flash Translation Layer) support"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500262 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600263 select MTD_BLKDEVS
Sean Younge27a9962005-06-16 09:49:33 +0100264 ---help---
Thomas Gleixner97894cd2005-11-07 11:15:26 +0000265 This provides support for the flash translation layer known
266 as the Resident Flash Disk (RFD), as used by the Embedded BIOS
Kyungmin Parkcd5f6342005-07-11 11:41:53 +0100267 of General Software. There is a blurb at:
268
269 http://www.gensw.com/pages/prod/bios/rfd.htm
Sean Younge27a9962005-06-16 09:49:33 +0100270
Claudio Lanconelli51197ab2006-09-22 11:01:37 +0100271config SSFDC
David Woodhouse892e4fb2006-09-23 10:24:36 +0100272 tristate "NAND SSFDC (SmartMedia) read only translation layer"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500273 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600274 select MTD_BLKDEVS
Claudio Lanconelli51197ab2006-09-22 11:01:37 +0100275 help
276 This enables read only access to SmartMedia formatted NAND
277 flash. You can mount it with FAT file system.
278
Maxim Levitsky7d17c022010-02-22 20:39:41 +0200279
280config SM_FTL
281 tristate "SmartMedia/xD new translation layer"
Kees Cook63726802012-10-02 11:17:47 -0700282 depends on BLOCK
Maxim Levitsky7d17c022010-02-22 20:39:41 +0200283 select MTD_BLKDEVS
Maxim Levitskye5f710c2010-03-19 17:22:54 +0200284 select MTD_NAND_ECC
Maxim Levitsky7d17c022010-02-22 20:39:41 +0200285 help
Maxim Levitsky6f923552010-07-28 18:53:17 +0300286 This enables EXPERIMENTAL R/W support for SmartMedia/xD
David Woodhouse7de6f792010-03-08 18:45:00 -0800287 FTL (Flash translation layer).
Maxim Levitsky6f923552010-07-28 18:53:17 +0300288 Write support is only lightly tested, therefore this driver
289 isn't recommended to use with valuable data (anyway if you have
290 valuable data, do backups regardless of software/hardware you
291 use, because you never know what will eat your data...)
292 If you only need R/O access, you can use older R/O driver
293 (CONFIG_SSFDC)
Maxim Levitsky7d17c022010-02-22 20:39:41 +0200294
Richard Purdie4b23aff2007-05-29 13:31:42 +0100295config MTD_OOPS
296 tristate "Log panic/oops to an MTD buffer"
Richard Purdie4b23aff2007-05-29 13:31:42 +0100297 help
298 This enables panic and oops messages to be logged to a circular
299 buffer in a flash partition where it can be read back at some
300 later point.
301
Jarkko Lavinena3215902011-02-14 16:16:11 +0200302config MTD_SWAP
303 tristate "Swap on MTD device support"
304 depends on MTD && SWAP
305 select MTD_BLKDEVS
306 help
307 Provides volatile block device driver on top of mtd partition
308 suitable for swapping. The mapping of written blocks is not saved.
309 The driver provides wear leveling by storing erase counter into the
310 OOB.
311
Dan Ehrenberg727dc612015-04-02 15:15:10 -0700312config MTD_PARTITIONED_MASTER
313 bool "Retain master device when partitioned"
314 default n
315 depends on MTD
316 help
317 For historical reasons, by default, either a master is present or
318 several partitions are present, but not both. The concern was that
319 data listed in multiple partitions was dangerous; however, SCSI does
320 this and it is frequently useful for applications. This config option
321 leaves the master in even if the device is partitioned. It also makes
322 the parent of the partition device be the master device, rather than
323 what lies behind the master.
324
Linus Torvalds1da177e2005-04-16 15:20:36 -0700325source "drivers/mtd/chips/Kconfig"
326
327source "drivers/mtd/maps/Kconfig"
328
329source "drivers/mtd/devices/Kconfig"
330
331source "drivers/mtd/nand/Kconfig"
332
Kyungmin Parkcd5f6342005-07-11 11:41:53 +0100333source "drivers/mtd/onenand/Kconfig"
334
Alexey Korolev60f26522008-12-16 18:24:14 +0000335source "drivers/mtd/lpddr/Kconfig"
336
Huang Shijieb1994892014-02-24 18:37:37 +0800337source "drivers/mtd/spi-nor/Kconfig"
338
Artem B. Bityutskiy801c1352006-06-27 12:22:22 +0400339source "drivers/mtd/ubi/Kconfig"
340
Jan Engelhardtec98c682007-04-19 16:21:41 -0500341endif # MTD