blob: ecf90f5c97c2bce84983d2567dc7933c8bb060c4 [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_CONCAT
37 tristate "MTD concatenating support"
Linus Torvalds1da177e2005-04-16 15:20:36 -070038 help
39 Support for concatenating several MTD devices into a single
40 (virtual) one. This allows you to have -for example- a JFFS(2)
41 file system spanning multiple physical flash chips. If unsure,
42 say 'Y'.
43
44config MTD_PARTITIONS
45 bool "MTD partitioning support"
Linus Torvalds1da177e2005-04-16 15:20:36 -070046 help
47 If you have a device which needs to divide its flash chip(s) up
48 into multiple 'partitions', each of which appears to the user as
49 a separate MTD device, you require this option to be enabled. If
50 unsure, say 'Y'.
51
52 Note, however, that you don't need this option for the DiskOnChip
53 devices. Partitioning on NFTL 'devices' is a different - that's the
54 'normal' form of partitioning used on a block device.
55
56config MTD_REDBOOT_PARTS
57 tristate "RedBoot partition table parsing"
58 depends on MTD_PARTITIONS
59 ---help---
60 RedBoot is a ROM monitor and bootloader which deals with multiple
61 'images' in flash devices by putting a table one of the erase
62 blocks on the device, similar to a partition table, which gives
63 the offsets, lengths and names of all the images stored in the
64 flash.
65
66 If you need code which can detect and parse this table, and register
67 MTD 'partitions' corresponding to each image in the table, enable
Thomas Gleixner97894cd2005-11-07 11:15:26 +000068 this option.
Linus Torvalds1da177e2005-04-16 15:20:36 -070069
70 You will still need the parsing functions to be called by the driver
Thomas Gleixner97894cd2005-11-07 11:15:26 +000071 for your particular device. It won't happen automatically. The
72 SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
Linus Torvalds1da177e2005-04-16 15:20:36 -070073 example.
74
75config MTD_REDBOOT_DIRECTORY_BLOCK
76 int "Location of RedBoot partition table"
77 depends on MTD_REDBOOT_PARTS
78 default "-1"
79 ---help---
80 This option is the Linux counterpart to the
81 CYGNUM_REDBOOT_FIS_DIRECTORY_BLOCK RedBoot compile time
82 option.
83
84 The option specifies which Flash sectors holds the RedBoot
Egry Gábor4992a9e2006-05-12 17:35:02 +010085 partition table. A zero or positive value gives an absolute
Linus Torvalds1da177e2005-04-16 15:20:36 -070086 erase block number. A negative value specifies a number of
87 sectors before the end of the device.
Thomas Gleixner97894cd2005-11-07 11:15:26 +000088
Linus Torvalds1da177e2005-04-16 15:20:36 -070089 For example "2" means block number 2, "-1" means the last
90 block and "-2" means the penultimate block.
Thomas Gleixner97894cd2005-11-07 11:15:26 +000091
Linus Torvalds1da177e2005-04-16 15:20:36 -070092config MTD_REDBOOT_PARTS_UNALLOCATED
Roman Zippele55a3e82006-06-08 22:12:49 -070093 bool "Include unallocated flash regions"
Linus Torvalds1da177e2005-04-16 15:20:36 -070094 depends on MTD_REDBOOT_PARTS
95 help
96 If you need to register each unallocated flash region as a MTD
97 'partition', enable this option.
98
99config MTD_REDBOOT_PARTS_READONLY
Roman Zippele55a3e82006-06-08 22:12:49 -0700100 bool "Force read-only for RedBoot system images"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700101 depends on MTD_REDBOOT_PARTS
102 help
103 If you need to force read-only for 'RedBoot', 'RedBoot Config' and
104 'FIS directory' images, enable this option.
105
106config MTD_CMDLINE_PARTS
107 bool "Command line partition table parsing"
David Woodhouse892e4fb2006-09-23 10:24:36 +0100108 depends on MTD_PARTITIONS = "y" && MTD = "y"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700109 ---help---
Egry Gábor4992a9e2006-05-12 17:35:02 +0100110 Allow generic configuration of the MTD partition tables via the kernel
Linus Torvalds1da177e2005-04-16 15:20:36 -0700111 command line. Multiple flash resources are supported for hardware where
Thomas Gleixner97894cd2005-11-07 11:15:26 +0000112 different kinds of flash memory are available.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700113
114 You will still need the parsing functions to be called by the driver
Thomas Gleixner97894cd2005-11-07 11:15:26 +0000115 for your particular device. It won't happen automatically. The
116 SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
Linus Torvalds1da177e2005-04-16 15:20:36 -0700117 example.
118
119 The format for the command line is as follows:
120
121 mtdparts=<mtddef>[;<mtddef]
122 <mtddef> := <mtd-id>:<partdef>[,<partdef>]
123 <partdef> := <size>[@offset][<name>][ro]
124 <mtd-id> := unique id used in mapping driver/device
Thomas Gleixner97894cd2005-11-07 11:15:26 +0000125 <size> := standard linux memsize OR "-" to denote all
Linus Torvalds1da177e2005-04-16 15:20:36 -0700126 remaining space
127 <name> := (NAME)
128
Thomas Gleixner97894cd2005-11-07 11:15:26 +0000129 Due to the way Linux handles the command line, no spaces are
130 allowed in the partition definition, including mtd id's and partition
Linus Torvalds1da177e2005-04-16 15:20:36 -0700131 names.
132
133 Examples:
134
135 1 flash resource (mtd-id "sa1100"), with 1 single writable partition:
136 mtdparts=sa1100:-
137
138 Same flash, but 2 named partitions, the first one being read-only:
139 mtdparts=sa1100:256k(ARMboot)ro,-(root)
140
141 If unsure, say 'N'.
142
143config MTD_AFS_PARTS
144 tristate "ARM Firmware Suite partition parsing"
145 depends on ARM && MTD_PARTITIONS
146 ---help---
147 The ARM Firmware Suite allows the user to divide flash devices into
148 multiple 'images'. Each such image has a header containing its name
149 and offset/size etc.
150
151 If you need code which can detect and parse these tables, and
152 register MTD 'partitions' corresponding to each image detected,
153 enable this option.
154
155 You will still need the parsing functions to be called by the driver
156 for your particular device. It won't happen automatically. The
Paulius Zaleckas0b1b51f2009-04-06 16:10:54 +0300157 'armflash' map driver (CONFIG_MTD_ARM_INTEGRATOR) does this, for
158 example.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700159
Scott Wood9a310d22008-01-15 17:54:43 -0600160config MTD_OF_PARTS
161 tristate "Flash partition map based on OF description"
John Williamsc2a32f02009-08-25 19:19:54 +1000162 depends on (MICROBLAZE || PPC_OF) && MTD_PARTITIONS
Scott Wood9a310d22008-01-15 17:54:43 -0600163 help
164 This provides a partition parsing function which derives
165 the partition map from the children of the flash node,
166 as described in Documentation/powerpc/booting-without-of.txt.
167
Matteo Crocef0797882008-03-12 02:25:06 +0100168config MTD_AR7_PARTS
169 tristate "TI AR7 partitioning support"
170 depends on MTD_PARTITIONS
171 ---help---
172 TI AR7 partitioning support
173
Linus Torvalds1da177e2005-04-16 15:20:36 -0700174comment "User Modules And Translation Layers"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700175
176config MTD_CHAR
177 tristate "Direct char device access to MTD devices"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700178 help
179 This provides a character device for each MTD device present in
180 the system, allowing the user to read and write directly to the
181 memory chips, and also use ioctl() to obtain information about
182 the device, or to erase parts of it.
183
David Brownell34a82442008-07-30 12:35:05 -0700184config HAVE_MTD_OTP
185 bool
186 help
187 Enable access to OTP regions using MTD_CHAR.
188
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600189config MTD_BLKDEVS
190 tristate "Common interface to block layer for MTD 'translation layers'"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500191 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600192 default n
193
Linus Torvalds1da177e2005-04-16 15:20:36 -0700194config MTD_BLOCK
195 tristate "Caching block device access to MTD devices"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500196 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600197 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700198 ---help---
199 Although most flash chips have an erase size too large to be useful
200 as block devices, it is possible to use MTD devices which are based
201 on RAM chips in this manner. This block device is a user of MTD
202 devices performing that function.
203
204 At the moment, it is also required for the Journalling Flash File
205 System(s) to obtain a handle on the MTD device when it's mounted
206 (although JFFS and JFFS2 don't actually use any of the functionality
207 of the mtdblock device).
208
209 Later, it may be extended to perform read/erase/modify/write cycles
210 on flash chips to emulate a smaller block size. Needless to say,
211 this is very unsafe, but could be useful for file systems which are
212 almost never written to.
213
214 You do not need this option for use with the DiskOnChip devices. For
215 those, enable NFTL support (CONFIG_NFTL) instead.
216
217config MTD_BLOCK_RO
218 tristate "Readonly block device access to MTD devices"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500219 depends on MTD_BLOCK!=y && BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600220 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700221 help
222 This allows you to mount read-only file systems (such as cramfs)
223 from an MTD device, without the overhead (and danger) of the caching
224 driver.
225
226 You do not need this option for use with the DiskOnChip devices. For
227 those, enable NFTL support (CONFIG_NFTL) instead.
228
229config FTL
230 tristate "FTL (Flash Translation Layer) support"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500231 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600232 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700233 ---help---
234 This provides support for the original Flash Translation Layer which
235 is part of the PCMCIA specification. It uses a kind of pseudo-
236 file system on a flash device to emulate a block device with
237 512-byte sectors, on top of which you put a 'normal' file system.
238
239 You may find that the algorithms used in this code are patented
240 unless you live in the Free World where software patents aren't
241 legal - in the USA you are only permitted to use this on PCMCIA
242 hardware, although under the terms of the GPL you're obviously
243 permitted to copy, modify and distribute the code as you wish. Just
244 not use it.
245
246config NFTL
247 tristate "NFTL (NAND Flash Translation Layer) support"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500248 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600249 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700250 ---help---
251 This provides support for the NAND Flash Translation Layer which is
252 used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
253 file system on a flash device to emulate a block device with
254 512-byte sectors, on top of which you put a 'normal' file system.
255
256 You may find that the algorithms used in this code are patented
257 unless you live in the Free World where software patents aren't
258 legal - in the USA you are only permitted to use this on DiskOnChip
259 hardware, although under the terms of the GPL you're obviously
260 permitted to copy, modify and distribute the code as you wish. Just
261 not use it.
262
263config NFTL_RW
264 bool "Write support for NFTL"
265 depends on NFTL
266 help
267 Support for writing to the NAND Flash Translation Layer, as used
268 on the DiskOnChip.
269
270config INFTL
271 tristate "INFTL (Inverse NAND Flash Translation Layer) support"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500272 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600273 select MTD_BLKDEVS
Linus Torvalds1da177e2005-04-16 15:20:36 -0700274 ---help---
Thomas Gleixner97894cd2005-11-07 11:15:26 +0000275 This provides support for the Inverse NAND Flash Translation
Linus Torvalds1da177e2005-04-16 15:20:36 -0700276 Layer which is used on M-Systems' newer DiskOnChip devices. It
277 uses a kind of pseudo-file system on a flash device to emulate
278 a block device with 512-byte sectors, on top of which you put
279 a 'normal' file system.
280
281 You may find that the algorithms used in this code are patented
282 unless you live in the Free World where software patents aren't
283 legal - in the USA you are only permitted to use this on DiskOnChip
284 hardware, although under the terms of the GPL you're obviously
285 permitted to copy, modify and distribute the code as you wish. Just
286 not use it.
287
Sean Younge27a9962005-06-16 09:49:33 +0100288config RFD_FTL
289 tristate "Resident Flash Disk (Flash Translation Layer) support"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500290 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600291 select MTD_BLKDEVS
Sean Younge27a9962005-06-16 09:49:33 +0100292 ---help---
Thomas Gleixner97894cd2005-11-07 11:15:26 +0000293 This provides support for the flash translation layer known
294 as the Resident Flash Disk (RFD), as used by the Embedded BIOS
Kyungmin Parkcd5f6342005-07-11 11:41:53 +0100295 of General Software. There is a blurb at:
296
297 http://www.gensw.com/pages/prod/bios/rfd.htm
Sean Younge27a9962005-06-16 09:49:33 +0100298
Claudio Lanconelli51197ab2006-09-22 11:01:37 +0100299config SSFDC
David Woodhouse892e4fb2006-09-23 10:24:36 +0100300 tristate "NAND SSFDC (SmartMedia) read only translation layer"
Jan Engelhardtec98c682007-04-19 16:21:41 -0500301 depends on BLOCK
Josh Boyerf6a7ecb2006-11-20 20:15:36 -0600302 select MTD_BLKDEVS
Claudio Lanconelli51197ab2006-09-22 11:01:37 +0100303 help
304 This enables read only access to SmartMedia formatted NAND
305 flash. You can mount it with FAT file system.
306
Richard Purdie4b23aff2007-05-29 13:31:42 +0100307config MTD_OOPS
308 tristate "Log panic/oops to an MTD buffer"
309 depends on MTD
310 help
311 This enables panic and oops messages to be logged to a circular
312 buffer in a flash partition where it can be read back at some
313 later point.
314
Peter Korsgaard256331d2007-11-06 11:55:00 +0100315 To use, add console=ttyMTDx to the kernel command line,
316 where x is the MTD device number to use.
317
Linus Torvalds1da177e2005-04-16 15:20:36 -0700318source "drivers/mtd/chips/Kconfig"
319
320source "drivers/mtd/maps/Kconfig"
321
322source "drivers/mtd/devices/Kconfig"
323
324source "drivers/mtd/nand/Kconfig"
325
Kyungmin Parkcd5f6342005-07-11 11:41:53 +0100326source "drivers/mtd/onenand/Kconfig"
327
Alexey Korolev60f26522008-12-16 18:24:14 +0000328source "drivers/mtd/lpddr/Kconfig"
329
Artem B. Bityutskiy801c1352006-06-27 12:22:22 +0400330source "drivers/mtd/ubi/Kconfig"
331
Jan Engelhardtec98c682007-04-19 16:21:41 -0500332endif # MTD