2 tristate "Memory Technology Device (MTD) support"
4 Memory Technology Devices are flash, RAM and similar chips, often
5 used for solid state file systems on embedded devices. This option
6 will provide the generic support for MTD drivers to register
7 themselves with the kernel and for potential users of MTD devices
8 to enumerate the devices which are present and obtain a handle on
9 them. It will also allow you to select individual drivers for
10 particular hardware and users of MTD devices. If unsure, say N.
15 tristate "MTD tests support (DANGEROUS)"
18 This option includes various MTD tests into compilation. The tests
19 should normally be compiled as kernel modules. The modules perform
20 various checks and verifications when loaded.
22 WARNING: some of the tests will ERASE entire MTD device which they
23 test. Do not use these tests unless you really know what you do.
25 config MTD_CMDLINE_PARTS
26 tristate "Command line partition table parsing"
29 Allow generic configuration of the MTD partition tables via the kernel
30 command line. Multiple flash resources are supported for hardware where
31 different kinds of flash memory are available.
33 You will still need the parsing functions to be called by the driver
34 for your particular device. It won't happen automatically. The
35 SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
38 The format for the command line is as follows:
40 mtdparts=<mtddef>[;<mtddef]
41 <mtddef> := <mtd-id>:<partdef>[,<partdef>]
42 <partdef> := <size>[@offset][<name>][ro]
43 <mtd-id> := unique id used in mapping driver/device
44 <size> := standard linux memsize OR "-" to denote all
48 Due to the way Linux handles the command line, no spaces are
49 allowed in the partition definition, including mtd id's and partition
54 1 flash resource (mtd-id "sa1100"), with 1 single writable partition:
57 Same flash, but 2 named partitions, the first one being read-only:
58 mtdparts=sa1100:256k(ARMboot)ro,-(root)
63 tristate "ARM Firmware Suite partition parsing"
64 depends on (ARM || ARM64)
66 The ARM Firmware Suite allows the user to divide flash devices into
67 multiple 'images'. Each such image has a header containing its name
70 If you need code which can detect and parse these tables, and
71 register MTD 'partitions' corresponding to each image detected,
74 You will still need the parsing functions to be called by the driver
75 for your particular device. It won't happen automatically. The
76 'physmap' map driver (CONFIG_MTD_PHYSMAP) does this, for example.
79 tristate "OpenFirmware partitioning information support"
83 This provides a partition parsing function which derives
84 the partition map from the children of the flash node,
85 as described in Documentation/devicetree/bindings/mtd/partition.txt.
88 tristate "TI AR7 partitioning support"
90 TI AR7 partitioning support
92 config MTD_BCM63XX_PARTS
93 tristate "BCM63XX CFE partitioning support"
94 depends on BCM63XX || BMIPS_GENERIC || COMPILE_TEST
97 This provides partition parsing for BCM63xx devices with CFE
100 config MTD_BCM47XX_PARTS
101 tristate "BCM47XX partitioning support"
102 depends on BCM47XX || ARCH_BCM_5301X
104 This provides partitions parser for devices based on BCM47xx
107 menu "Partition parsers"
108 source "drivers/mtd/parsers/Kconfig"
111 comment "User Modules And Translation Layers"
114 # MTD block device support is select'ed if needed
120 tristate "Caching block device access to MTD devices"
124 Although most flash chips have an erase size too large to be useful
125 as block devices, it is possible to use MTD devices which are based
126 on RAM chips in this manner. This block device is a user of MTD
127 devices performing that function.
129 At the moment, it is also required for the Journalling Flash File
130 System(s) to obtain a handle on the MTD device when it's mounted
131 (although JFFS and JFFS2 don't actually use any of the functionality
132 of the mtdblock device).
134 Later, it may be extended to perform read/erase/modify/write cycles
135 on flash chips to emulate a smaller block size. Needless to say,
136 this is very unsafe, but could be useful for file systems which are
137 almost never written to.
139 You do not need this option for use with the DiskOnChip devices. For
140 those, enable NFTL support (CONFIG_NFTL) instead.
143 tristate "Readonly block device access to MTD devices"
144 depends on MTD_BLOCK!=y && BLOCK
147 This allows you to mount read-only file systems (such as cramfs)
148 from an MTD device, without the overhead (and danger) of the caching
151 You do not need this option for use with the DiskOnChip devices. For
152 those, enable NFTL support (CONFIG_NFTL) instead.
155 tristate "FTL (Flash Translation Layer) support"
159 This provides support for the original Flash Translation Layer which
160 is part of the PCMCIA specification. It uses a kind of pseudo-
161 file system on a flash device to emulate a block device with
162 512-byte sectors, on top of which you put a 'normal' file system.
164 You may find that the algorithms used in this code are patented
165 unless you live in the Free World where software patents aren't
166 legal - in the USA you are only permitted to use this on PCMCIA
167 hardware, although under the terms of the GPL you're obviously
168 permitted to copy, modify and distribute the code as you wish. Just
172 tristate "NFTL (NAND Flash Translation Layer) support"
176 This provides support for the NAND Flash Translation Layer which is
177 used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
178 file system on a flash device to emulate a block device with
179 512-byte sectors, on top of which you put a 'normal' file system.
181 You may find that the algorithms used in this code are patented
182 unless you live in the Free World where software patents aren't
183 legal - in the USA you are only permitted to use this on DiskOnChip
184 hardware, although under the terms of the GPL you're obviously
185 permitted to copy, modify and distribute the code as you wish. Just
189 bool "Write support for NFTL"
192 Support for writing to the NAND Flash Translation Layer, as used
196 tristate "INFTL (Inverse NAND Flash Translation Layer) support"
200 This provides support for the Inverse NAND Flash Translation
201 Layer which is used on M-Systems' newer DiskOnChip devices. It
202 uses a kind of pseudo-file system on a flash device to emulate
203 a block device with 512-byte sectors, on top of which you put
204 a 'normal' file system.
206 You may find that the algorithms used in this code are patented
207 unless you live in the Free World where software patents aren't
208 legal - in the USA you are only permitted to use this on DiskOnChip
209 hardware, although under the terms of the GPL you're obviously
210 permitted to copy, modify and distribute the code as you wish. Just
214 tristate "Resident Flash Disk (Flash Translation Layer) support"
218 This provides support for the flash translation layer known
219 as the Resident Flash Disk (RFD), as used by the Embedded BIOS
220 of General Software. There is a blurb at:
222 http://www.gensw.com/pages/prod/bios/rfd.htm
225 tristate "NAND SSFDC (SmartMedia) read only translation layer"
229 This enables read only access to SmartMedia formatted NAND
230 flash. You can mount it with FAT file system.
234 tristate "SmartMedia/xD new translation layer"
239 This enables EXPERIMENTAL R/W support for SmartMedia/xD
240 FTL (Flash translation layer).
241 Write support is only lightly tested, therefore this driver
242 isn't recommended to use with valuable data (anyway if you have
243 valuable data, do backups regardless of software/hardware you
244 use, because you never know what will eat your data...)
245 If you only need R/O access, you can use older R/O driver
249 tristate "Log panic/oops to an MTD buffer"
251 This enables panic and oops messages to be logged to a circular
252 buffer in a flash partition where it can be read back at some
256 tristate "Swap on MTD device support"
257 depends on MTD && SWAP
260 Provides volatile block device driver on top of mtd partition
261 suitable for swapping. The mapping of written blocks is not saved.
262 The driver provides wear leveling by storing erase counter into the
265 config MTD_PARTITIONED_MASTER
266 bool "Retain master device when partitioned"
270 For historical reasons, by default, either a master is present or
271 several partitions are present, but not both. The concern was that
272 data listed in multiple partitions was dangerous; however, SCSI does
273 this and it is frequently useful for applications. This config option
274 leaves the master in even if the device is partitioned. It also makes
275 the parent of the partition device be the master device, rather than
276 what lies behind the master.
278 source "drivers/mtd/chips/Kconfig"
280 source "drivers/mtd/maps/Kconfig"
282 source "drivers/mtd/devices/Kconfig"
284 source "drivers/mtd/nand/Kconfig"
286 source "drivers/mtd/lpddr/Kconfig"
288 source "drivers/mtd/spi-nor/Kconfig"
290 source "drivers/mtd/ubi/Kconfig"