0001 menuconfig MTD
0002 tristate "Memory Technology Device (MTD) support"
0003 imply NVMEM
0004 help
0005 Memory Technology Devices are flash, RAM and similar chips, often
0006 used for solid state file systems on embedded devices. This option
0007 will provide the generic support for MTD drivers to register
0008 themselves with the kernel and for potential users of MTD devices
0009 to enumerate the devices which are present and obtain a handle on
0010 them. It will also allow you to select individual drivers for
0011 particular hardware and users of MTD devices. If unsure, say N.
0012
0013 if MTD
0014
0015 config MTD_TESTS
0016 tristate "MTD tests support (DANGEROUS)"
0017 depends on m
0018 help
0019 This option includes various MTD tests into compilation. The tests
0020 should normally be compiled as kernel modules. The modules perform
0021 various checks and verifications when loaded.
0022
0023 WARNING: some of the tests will ERASE entire MTD device which they
0024 test. Do not use these tests unless you really know what you do.
0025
0026 menu "Partition parsers"
0027 source "drivers/mtd/parsers/Kconfig"
0028 endmenu
0029
0030 comment "User Modules And Translation Layers"
0031
0032 #
0033 # MTD block device support is select'ed if needed
0034 #
0035 config MTD_BLKDEVS
0036 tristate
0037
0038 config MTD_BLOCK
0039 tristate "Caching block device access to MTD devices"
0040 depends on BLOCK
0041 select MTD_BLKDEVS
0042 help
0043 Although most flash chips have an erase size too large to be useful
0044 as block devices, it is possible to use MTD devices which are based
0045 on RAM chips in this manner. This block device is a user of MTD
0046 devices performing that function.
0047
0048 Note that mounting a JFFS2 filesystem doesn't require using mtdblock.
0049 It's possible to mount a rootfs using the MTD device on the "root="
0050 bootargs as "root=mtd2" or "root=mtd:name_of_device".
0051
0052 Later, it may be extended to perform read/erase/modify/write cycles
0053 on flash chips to emulate a smaller block size. Needless to say,
0054 this is very unsafe, but could be useful for file systems which are
0055 almost never written to.
0056
0057 You do not need this option for use with the DiskOnChip devices. For
0058 those, enable NFTL support (CONFIG_NFTL) instead.
0059
0060 config MTD_BLOCK_RO
0061 tristate "Readonly block device access to MTD devices"
0062 depends on MTD_BLOCK!=y && BLOCK
0063 select MTD_BLKDEVS
0064 help
0065 This allows you to mount read-only file systems (such as cramfs)
0066 from an MTD device, without the overhead (and danger) of the caching
0067 driver.
0068
0069 You do not need this option for use with the DiskOnChip devices. For
0070 those, enable NFTL support (CONFIG_NFTL) instead.
0071
0072 comment "Note that in some cases UBI block is preferred. See MTD_UBI_BLOCK."
0073 depends on MTD_BLOCK || MTD_BLOCK_RO
0074
0075 config FTL
0076 tristate "FTL (Flash Translation Layer) support"
0077 depends on BLOCK
0078 select MTD_BLKDEVS
0079 help
0080 This provides support for the original Flash Translation Layer which
0081 is part of the PCMCIA specification. It uses a kind of pseudo-
0082 file system on a flash device to emulate a block device with
0083 512-byte sectors, on top of which you put a 'normal' file system.
0084
0085 You may find that the algorithms used in this code are patented
0086 unless you live in the Free World where software patents aren't
0087 legal - in the USA you are only permitted to use this on PCMCIA
0088 hardware, although under the terms of the GPL you're obviously
0089 permitted to copy, modify and distribute the code as you wish. Just
0090 not use it.
0091
0092 config NFTL
0093 tristate "NFTL (NAND Flash Translation Layer) support"
0094 depends on BLOCK
0095 select MTD_BLKDEVS
0096 help
0097 This provides support for the NAND Flash Translation Layer which is
0098 used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
0099 file system on a flash device to emulate a block device with
0100 512-byte sectors, on top of which you put a 'normal' file system.
0101
0102 You may find that the algorithms used in this code are patented
0103 unless you live in the Free World where software patents aren't
0104 legal - in the USA you are only permitted to use this on DiskOnChip
0105 hardware, although under the terms of the GPL you're obviously
0106 permitted to copy, modify and distribute the code as you wish. Just
0107 not use it.
0108
0109 config NFTL_RW
0110 bool "Write support for NFTL"
0111 depends on NFTL
0112 help
0113 Support for writing to the NAND Flash Translation Layer, as used
0114 on the DiskOnChip.
0115
0116 config INFTL
0117 tristate "INFTL (Inverse NAND Flash Translation Layer) support"
0118 depends on BLOCK
0119 select MTD_BLKDEVS
0120 help
0121 This provides support for the Inverse NAND Flash Translation
0122 Layer which is used on M-Systems' newer DiskOnChip devices. It
0123 uses a kind of pseudo-file system on a flash device to emulate
0124 a block device with 512-byte sectors, on top of which you put
0125 a 'normal' file system.
0126
0127 You may find that the algorithms used in this code are patented
0128 unless you live in the Free World where software patents aren't
0129 legal - in the USA you are only permitted to use this on DiskOnChip
0130 hardware, although under the terms of the GPL you're obviously
0131 permitted to copy, modify and distribute the code as you wish. Just
0132 not use it.
0133
0134 config RFD_FTL
0135 tristate "Resident Flash Disk (Flash Translation Layer) support"
0136 depends on BLOCK
0137 select MTD_BLKDEVS
0138 help
0139 This provides support for the flash translation layer known
0140 as the Resident Flash Disk (RFD), as used by the Embedded BIOS
0141 of General Software. There is a blurb at:
0142
0143 http://www.gensw.com/pages/prod/bios/rfd.htm
0144
0145 config SSFDC
0146 tristate "NAND SSFDC (SmartMedia) read only translation layer"
0147 depends on BLOCK
0148 select MTD_BLKDEVS
0149 help
0150 This enables read only access to SmartMedia formatted NAND
0151 flash. You can mount it with FAT file system.
0152
0153 config SM_FTL
0154 tristate "SmartMedia/xD new translation layer"
0155 depends on BLOCK
0156 select MTD_BLKDEVS
0157 select MTD_NAND_CORE
0158 select MTD_NAND_ECC_SW_HAMMING
0159 help
0160 This enables EXPERIMENTAL R/W support for SmartMedia/xD
0161 FTL (Flash translation layer).
0162 Write support is only lightly tested, therefore this driver
0163 isn't recommended to use with valuable data (anyway if you have
0164 valuable data, do backups regardless of software/hardware you
0165 use, because you never know what will eat your data...)
0166 If you only need R/O access, you can use older R/O driver
0167 (CONFIG_SSFDC)
0168
0169 config MTD_OOPS
0170 tristate "Log panic/oops to an MTD buffer"
0171 help
0172 This enables panic and oops messages to be logged to a circular
0173 buffer in a flash partition where it can be read back at some
0174 later point.
0175
0176 config MTD_PSTORE
0177 tristate "Log panic/oops to an MTD buffer based on pstore"
0178 depends on PSTORE_BLK
0179 help
0180 This enables panic and oops messages to be logged to a circular
0181 buffer in a flash partition where it can be read back as files after
0182 mounting pstore filesystem.
0183
0184 If unsure, say N.
0185
0186 config MTD_SWAP
0187 tristate "Swap on MTD device support"
0188 depends on MTD && SWAP
0189 select MTD_BLKDEVS
0190 help
0191 Provides volatile block device driver on top of mtd partition
0192 suitable for swapping. The mapping of written blocks is not saved.
0193 The driver provides wear leveling by storing erase counter into the
0194 OOB.
0195
0196 config MTD_PARTITIONED_MASTER
0197 bool "Retain master device when partitioned"
0198 default n
0199 depends on MTD
0200 help
0201 For historical reasons, by default, either a master is present or
0202 several partitions are present, but not both. The concern was that
0203 data listed in multiple partitions was dangerous; however, SCSI does
0204 this and it is frequently useful for applications. This config option
0205 leaves the master in even if the device is partitioned. It also makes
0206 the parent of the partition device be the master device, rather than
0207 what lies behind the master.
0208
0209 source "drivers/mtd/chips/Kconfig"
0210
0211 source "drivers/mtd/maps/Kconfig"
0212
0213 source "drivers/mtd/devices/Kconfig"
0214
0215 source "drivers/mtd/nand/Kconfig"
0216
0217 source "drivers/mtd/lpddr/Kconfig"
0218
0219 source "drivers/mtd/spi-nor/Kconfig"
0220
0221 source "drivers/mtd/ubi/Kconfig"
0222
0223 source "drivers/mtd/hyperbus/Kconfig"
0224
0225 endif # MTD
