blob: 4be8373d43e5c6af542c8a5a609fc8402e9b1dc0 [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"
Martin Schwidefskye25df122007-05-10 15:45:57 +02003 depends on HAS_IOMEM
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
Linus Torvalds1da177e2005-04-16 15:20:36 -070015config MTD_DEBUG
16 bool "Debugging"
Linus Torvalds1da177e2005-04-16 15:20:36 -070017 help
18 This turns on low-level debugging for the entire MTD sub-system.
19 Normally, you should say 'N'.
20
21config MTD_DEBUG_VERBOSE
22 int "Debugging verbosity (0 = quiet, 3 = noisy)"
23 depends on MTD_DEBUG
24 default "0"
25 help
26 Determines the verbosity level of the MTD debugging messages.
27
Mike Frysinger80f53da2009-06-13 06:15:18 -040028config MTD_TESTS
29 tristate "MTD tests support"
30 depends on m
31 help
32 This option includes various MTD tests into compilation. The tests
33 should normally be compiled as kernel modules. The modules perform
34 various checks and verifications when loaded.
35
Linus Torvalds1da177e2005-04-16 15:20:36 -070036config MTD_REDBOOT_PARTS
37 tristate "RedBoot partition table parsing"
Linus Torvalds1da177e2005-04-16 15:20:36 -070038 ---help---
39 RedBoot is a ROM monitor and bootloader which deals with multiple
40 'images' in flash devices by putting a table one of the erase
41 blocks on the device, similar to a partition table, which gives
42 the offsets, lengths and names of all the images stored in the
43 flash.
44
45 If you need code which can detect and parse this table, and register
46 MTD 'partitions' corresponding to each image in the table, enable
Thomas Gleixner97894cd2005-11-07 11:15:26 +000047 this option.
Linus Torvalds1da177e2005-04-16 15:20:36 -070048
49 You will still need the parsing functions to be called by the driver
Thomas Gleixner97894cd2005-11-07 11:15:26 +000050 for your particular device. It won't happen automatically. The
51 SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
Linus Torvalds1da177e2005-04-16 15:20:36 -070052 example.
53
Grant Likelyb7b6e082010-10-30 07:35:02 +010054if MTD_REDBOOT_PARTS
55
Linus Torvalds1da177e2005-04-16 15:20:36 -070056config MTD_REDBOOT_DIRECTORY_BLOCK
57 int "Location of RedBoot partition table"
Linus Torvalds1da177e2005-04-16 15:20:36 -070058 default "-1"
59 ---help---
60 This option is the Linux counterpart to the
61 CYGNUM_REDBOOT_FIS_DIRECTORY_BLOCK RedBoot compile time
62 option.
63
64 The option specifies which Flash sectors holds the RedBoot
Egry Gábor4992a9e2006-05-12 17:35:02 +010065 partition table. A zero or positive value gives an absolute
Linus Torvalds1da177e2005-04-16 15:20:36 -070066 erase block number. A negative value specifies a number of
67 sectors before the end of the device.
Thomas Gleixner97894cd2005-11-07 11:15:26 +000068
Linus Torvalds1da177e2005-04-16 15:20:36 -070069 For example "2" means block number 2, "-1" means the last
70 block and "-2" means the penultimate block.
Thomas Gleixner97894cd2005-11-07 11:15:26 +000071
Linus Torvalds1da177e2005-04-16 15:20:36 -070072config MTD_REDBOOT_PARTS_UNALLOCATED
Roman Zippele55a3e82006-06-08 22:12:49 -070073 bool "Include unallocated flash regions"
Linus Torvalds1da177e2005-04-16 15:20:36 -070074 help
75 If you need to register each unallocated flash region as a MTD
76 'partition', enable this option.
77
78config MTD_REDBOOT_PARTS_READONLY
Roman Zippele55a3e82006-06-08 22:12:49 -070079 bool "Force read-only for RedBoot system images"
Linus Torvalds1da177e2005-04-16 15:20:36 -070080 help
81 If you need to force read-only for 'RedBoot', 'RedBoot Config' and
82 'FIS directory' images, enable this option.
83
Grant Likelyb7b6e082010-10-30 07:35:02 +010084endif # MTD_REDBOOT_PARTS
85
Linus Torvalds1da177e2005-04-16 15:20:36 -070086config MTD_CMDLINE_PARTS
87 bool "Command line partition table parsing"
Jamie Iles6a8a98b2011-05-23 10:23:43 +010088 depends on MTD = "y"
Linus Torvalds1da177e2005-04-16 15:20:36 -070089 ---help---
Egry Gábor4992a9e2006-05-12 17:35:02 +010090 Allow generic configuration of the MTD partition tables via the kernel
Linus Torvalds1da177e2005-04-16 15:20:36 -070091 command line. Multiple flash resources are supported for hardware where
Thomas Gleixner97894cd2005-11-07 11:15:26 +000092 different kinds of flash memory are available.
Linus Torvalds1da177e2005-04-16 15:20:36 -070093
94 You will still need the parsing functions to be called by the driver
Thomas Gleixner97894cd2005-11-07 11:15:26 +000095 for your particular device. It won't happen automatically. The
96 SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
Linus Torvalds1da177e2005-04-16 15:20:36 -070097 example.
98
99 The format for the command line is as follows:
100
101 mtdparts=<mtddef>[;<mtddef]
102 <mtddef> := <mtd-id>:<partdef>[,<partdef>]
103 <partdef> := <size>[@offset][<name>][ro]
104 <mtd-id> := unique id used in mapping driver/device
Thomas Gleixner97894cd2005-11-07 11:15:26 +0000105 <size> := standard linux memsize OR "-" to denote all
Linus Torvalds1da177e2005-04-16 15:20:36 -0700106 remaining space
107 <name> := (NAME)
108
Thomas Gleixner97894cd2005-11-07 11:15:26 +0000109 Due to the way Linux handles the command line, no spaces are
110 allowed in the partition definition, including mtd id's and partition
Linus Torvalds1da177e2005-04-16 15:20:36 -0700111 names.
112
113 Examples:
114
115 1 flash resource (mtd-id "sa1100"), with 1 single writable partition:
116 mtdparts=sa1100:-
117
118 Same flash, but 2 named partitions, the first one being read-only:
119 mtdparts=sa1100:256k(ARMboot)ro,-(root)
120
121 If unsure, say 'N'.
122
123config MTD_AFS_PARTS
124 tristate "ARM Firmware Suite partition parsing"
Grant Likelyb7b6e082010-10-30 07:35:02 +0100125 depends on ARM
Linus Torvalds1da177e2005-04-16 15:20:36 -0700126 ---help---
127 The ARM Firmware Suite allows the user to divide flash devices into
128 multiple 'images'. Each such image has a header containing its name
129 and offset/size etc.
130
131 If you need code which can detect and parse these tables, and
132 register MTD 'partitions' corresponding to each image detected,
133 enable this option.
134
135 You will still need the parsing functions to be called by the driver
136 for your particular device. It won't happen automatically. The
Marc Zyngieradf00402011-05-18 10:51:54 +0100137 'physmap' map driver (CONFIG_MTD_PHYSMAP) does this, for example.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700138
Scott Wood9a310d22008-01-15 17:54:43 -0600139config MTD_OF_PARTS
Grant Likelyb7b6e082010-10-30 07:35:02 +0100140 def_bool y
141 depends on OF
Scott Wood9a310d22008-01-15 17:54:43 -0600142 help
143 This provides a partition parsing function which derives
144 the partition map from the children of the flash node,
145 as described in Documentation/powerpc/booting-without-of.txt.
146
Matteo Crocef0797882008-03-12 02:25:06 +0100147config MTD_AR7_PARTS
148 tristate "TI AR7 partitioning support"
Matteo Crocef0797882008-03-12 02:25:06 +0100149 ---help---
150 TI AR7 partitioning support
151
Linus Torvalds1da177e2005-04-16 15:20:36 -0700152comment "User Modules And Translation Layers"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700153
154config MTD_CHAR
155 tristate "Direct char device access to MTD devices"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700156 help
157 This provides a character device for each MTD device present in
158 the system, allowing the user to read and write directly to the
159 memory chips, and also use ioctl() to obtain information about
160 the device, or to erase parts of it.
161
David Brownell34a82442008-07-30 12:35:05 -0700162config HAVE_MTD_OTP
163 bool
164 help
165 Enable access to OTP regions using MTD_CHAR.
166
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600167config MTD_BLKDEVS
168 tristate "Common interface to block layer for MTD 'translation layers'"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500169 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600170 default n
171
Linus Torvalds1da177e2005-04-16 15:20:36 -0700172config MTD_BLOCK
173 tristate "Caching block device access to MTD devices"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500174 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600175 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700176 ---help---
177 Although most flash chips have an erase size too large to be useful
178 as block devices, it is possible to use MTD devices which are based
179 on RAM chips in this manner. This block device is a user of MTD
180 devices performing that function.
181
182 At the moment, it is also required for the Journalling Flash File
183 System(s) to obtain a handle on the MTD device when it's mounted
184 (although JFFS and JFFS2 don't actually use any of the functionality
185 of the mtdblock device).
186
187 Later, it may be extended to perform read/erase/modify/write cycles
188 on flash chips to emulate a smaller block size. Needless to say,
189 this is very unsafe, but could be useful for file systems which are
190 almost never written to.
191
192 You do not need this option for use with the DiskOnChip devices. For
193 those, enable NFTL support (CONFIG_NFTL) instead.
194
195config MTD_BLOCK_RO
196 tristate "Readonly block device access to MTD devices"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500197 depends on MTD_BLOCK!=y && BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600198 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700199 help
200 This allows you to mount read-only file systems (such as cramfs)
201 from an MTD device, without the overhead (and danger) of the caching
202 driver.
203
204 You do not need this option for use with the DiskOnChip devices. For
205 those, enable NFTL support (CONFIG_NFTL) instead.
206
207config FTL
208 tristate "FTL (Flash Translation Layer) support"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500209 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600210 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700211 ---help---
212 This provides support for the original Flash Translation Layer which
213 is part of the PCMCIA specification. It uses a kind of pseudo-
214 file system on a flash device to emulate a block device with
215 512-byte sectors, on top of which you put a 'normal' file system.
216
217 You may find that the algorithms used in this code are patented
218 unless you live in the Free World where software patents aren't
219 legal - in the USA you are only permitted to use this on PCMCIA
220 hardware, although under the terms of the GPL you're obviously
221 permitted to copy, modify and distribute the code as you wish. Just
222 not use it.
223
224config NFTL
225 tristate "NFTL (NAND Flash Translation Layer) support"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500226 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600227 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700228 ---help---
229 This provides support for the NAND Flash Translation Layer which is
230 used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
231 file system on a flash device to emulate a block device with
232 512-byte sectors, on top of which you put a 'normal' file system.
233
234 You may find that the algorithms used in this code are patented
235 unless you live in the Free World where software patents aren't
236 legal - in the USA you are only permitted to use this on DiskOnChip
237 hardware, although under the terms of the GPL you're obviously
238 permitted to copy, modify and distribute the code as you wish. Just
239 not use it.
240
241config NFTL_RW
242 bool "Write support for NFTL"
243 depends on NFTL
244 help
245 Support for writing to the NAND Flash Translation Layer, as used
246 on the DiskOnChip.
247
248config INFTL
249 tristate "INFTL (Inverse NAND Flash Translation Layer) support"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500250 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600251 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700252 ---help---
Thomas Gleixner97894cd2005-11-07 11:15:26 +0000253 This provides support for the Inverse NAND Flash Translation
Linus Torvalds1da177e2005-04-16 15:20:36 -0700254 Layer which is used on M-Systems' newer DiskOnChip devices. It
255 uses a kind of pseudo-file system on a flash device to emulate
256 a block device with 512-byte sectors, on top of which you put
257 a 'normal' file system.
258
259 You may find that the algorithms used in this code are patented
260 unless you live in the Free World where software patents aren't
261 legal - in the USA you are only permitted to use this on DiskOnChip
262 hardware, although under the terms of the GPL you're obviously
263 permitted to copy, modify and distribute the code as you wish. Just
264 not use it.
265
Sean Younge27a9962005-06-16 09:49:33 +0100266config RFD_FTL
267 tristate "Resident Flash Disk (Flash Translation Layer) support"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500268 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600269 select MTD_BLKDEVS
Sean Younge27a9962005-06-16 09:49:33 +0100270 ---help---
Thomas Gleixner97894cd2005-11-07 11:15:26 +0000271 This provides support for the flash translation layer known
272 as the Resident Flash Disk (RFD), as used by the Embedded BIOS
Kyungmin Parkcd5f6342005-07-11 11:41:53 +0100273 of General Software. There is a blurb at:
274
275 http://www.gensw.com/pages/prod/bios/rfd.htm
Sean Younge27a9962005-06-16 09:49:33 +0100276
Claudio Lanconelli51197ab2006-09-22 11:01:37 +0100277config SSFDC
David Woodhouse892e4fb2006-09-23 10:24:36 +0100278 tristate "NAND SSFDC (SmartMedia) read only translation layer"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500279 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600280 select MTD_BLKDEVS
Claudio Lanconelli51197ab2006-09-22 11:01:37 +0100281 help
282 This enables read only access to SmartMedia formatted NAND
283 flash. You can mount it with FAT file system.
284
Maxim Levitsky7d17c022010-02-22 20:39:41 +0200285
286config SM_FTL
287 tristate "SmartMedia/xD new translation layer"
Maxim Levitskye5f710c2010-03-19 17:22:54 +0200288 depends on EXPERIMENTAL && BLOCK
Maxim Levitsky7d17c022010-02-22 20:39:41 +0200289 select MTD_BLKDEVS
Maxim Levitskye5f710c2010-03-19 17:22:54 +0200290 select MTD_NAND_ECC
Maxim Levitsky7d17c022010-02-22 20:39:41 +0200291 help
Maxim Levitsky6f923552010-07-28 18:53:17 +0300292 This enables EXPERIMENTAL R/W support for SmartMedia/xD
David Woodhouse7de6f792010-03-08 18:45:00 -0800293 FTL (Flash translation layer).
Maxim Levitsky6f923552010-07-28 18:53:17 +0300294 Write support is only lightly tested, therefore this driver
295 isn't recommended to use with valuable data (anyway if you have
296 valuable data, do backups regardless of software/hardware you
297 use, because you never know what will eat your data...)
298 If you only need R/O access, you can use older R/O driver
299 (CONFIG_SSFDC)
Maxim Levitsky7d17c022010-02-22 20:39:41 +0200300
Richard Purdie4b23aff2007-05-29 13:31:42 +0100301config MTD_OOPS
302 tristate "Log panic/oops to an MTD buffer"
Richard Purdie4b23aff2007-05-29 13:31:42 +0100303 help
304 This enables panic and oops messages to be logged to a circular
305 buffer in a flash partition where it can be read back at some
306 later point.
307
Peter Korsgaard256331d2007-11-06 11:55:00 +0100308 To use, add console=ttyMTDx to the kernel command line,
309 where x is the MTD device number to use.
310
Jarkko Lavinena3215902011-02-14 16:16:11 +0200311config MTD_SWAP
312 tristate "Swap on MTD device support"
313 depends on MTD && SWAP
314 select MTD_BLKDEVS
315 help
316 Provides volatile block device driver on top of mtd partition
317 suitable for swapping. The mapping of written blocks is not saved.
318 The driver provides wear leveling by storing erase counter into the
319 OOB.
320
Linus Torvalds1da177e2005-04-16 15:20:36 -0700321source "drivers/mtd/chips/Kconfig"
322
323source "drivers/mtd/maps/Kconfig"
324
325source "drivers/mtd/devices/Kconfig"
326
327source "drivers/mtd/nand/Kconfig"
328
Kyungmin Parkcd5f6342005-07-11 11:41:53 +0100329source "drivers/mtd/onenand/Kconfig"
330
Alexey Korolev60f26522008-12-16 18:24:14 +0000331source "drivers/mtd/lpddr/Kconfig"
332
Artem B. Bityutskiy801c1352006-06-27 12:22:22 +0400333source "drivers/mtd/ubi/Kconfig"
334
Jan Engelhardtec98c682007-04-19 16:21:41 -0500335endif # MTD