2007-04-20 05:21:41 +08:00
|
|
|
menuconfig MTD
|
2005-04-17 06:20:36 +08:00
|
|
|
tristate "Memory Technology Device (MTD) support"
|
2018-11-13 22:01:10 +08:00
|
|
|
imply NVMEM
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
Memory Technology Devices are flash, RAM and similar chips, often
|
|
|
|
|
used for solid state file systems on embedded devices. This option
|
|
|
|
|
will provide the generic support for MTD drivers to register
|
|
|
|
|
themselves with the kernel and for potential users of MTD devices
|
|
|
|
|
to enumerate the devices which are present and obtain a handle on
|
2005-11-07 19:15:26 +08:00
|
|
|
them. It will also allow you to select individual drivers for
|
2005-04-17 06:20:36 +08:00
|
|
|
particular hardware and users of MTD devices. If unsure, say N.
|
|
|
|
|
|
2007-04-20 05:21:41 +08:00
|
|
|
if MTD
|
|
|
|
|
|
2009-06-13 18:15:18 +08:00
|
|
|
config MTD_TESTS
|
2011-10-31 00:28:49 +08:00
|
|
|
tristate "MTD tests support (DANGEROUS)"
|
2009-06-13 18:15:18 +08:00
|
|
|
depends on m
|
|
|
|
|
help
|
|
|
|
|
This option includes various MTD tests into compilation. The tests
|
|
|
|
|
should normally be compiled as kernel modules. The modules perform
|
|
|
|
|
various checks and verifications when loaded.
|
|
|
|
|
|
2011-10-31 00:28:49 +08:00
|
|
|
WARNING: some of the tests will ERASE entire MTD device which they
|
|
|
|
|
test. Do not use these tests unless you really know what you do.
|
|
|
|
|
|
2017-06-21 14:26:47 +08:00
|
|
|
menu "Partition parsers"
|
|
|
|
|
source "drivers/mtd/parsers/Kconfig"
|
|
|
|
|
endmenu
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
comment "User Modules And Translation Layers"
|
|
|
|
|
|
2013-12-13 21:58:44 +08:00
|
|
|
#
|
|
|
|
|
# MTD block device support is select'ed if needed
|
|
|
|
|
#
|
2006-11-21 10:15:36 +08:00
|
|
|
config MTD_BLKDEVS
|
2013-12-13 21:58:44 +08:00
|
|
|
tristate
|
2006-11-21 10:15:36 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config MTD_BLOCK
|
|
|
|
|
tristate "Caching block device access to MTD devices"
|
2007-04-20 05:21:41 +08:00
|
|
|
depends on BLOCK
|
2006-11-21 10:15:36 +08:00
|
|
|
select MTD_BLKDEVS
|
2018-07-18 23:09:52 +08:00
|
|
|
help
|
2005-04-17 06:20:36 +08:00
|
|
|
Although most flash chips have an erase size too large to be useful
|
|
|
|
|
as block devices, it is possible to use MTD devices which are based
|
|
|
|
|
on RAM chips in this manner. This block device is a user of MTD
|
|
|
|
|
devices performing that function.
|
|
|
|
|
|
|
|
|
|
At the moment, it is also required for the Journalling Flash File
|
|
|
|
|
System(s) to obtain a handle on the MTD device when it's mounted
|
|
|
|
|
(although JFFS and JFFS2 don't actually use any of the functionality
|
|
|
|
|
of the mtdblock device).
|
|
|
|
|
|
|
|
|
|
Later, it may be extended to perform read/erase/modify/write cycles
|
|
|
|
|
on flash chips to emulate a smaller block size. Needless to say,
|
|
|
|
|
this is very unsafe, but could be useful for file systems which are
|
|
|
|
|
almost never written to.
|
|
|
|
|
|
|
|
|
|
You do not need this option for use with the DiskOnChip devices. For
|
|
|
|
|
those, enable NFTL support (CONFIG_NFTL) instead.
|
|
|
|
|
|
|
|
|
|
config MTD_BLOCK_RO
|
|
|
|
|
tristate "Readonly block device access to MTD devices"
|
2007-04-20 05:21:41 +08:00
|
|
|
depends on MTD_BLOCK!=y && BLOCK
|
2006-11-21 10:15:36 +08:00
|
|
|
select MTD_BLKDEVS
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
This allows you to mount read-only file systems (such as cramfs)
|
|
|
|
|
from an MTD device, without the overhead (and danger) of the caching
|
|
|
|
|
driver.
|
|
|
|
|
|
|
|
|
|
You do not need this option for use with the DiskOnChip devices. For
|
|
|
|
|
those, enable NFTL support (CONFIG_NFTL) instead.
|
|
|
|
|
|
|
|
|
|
config FTL
|
|
|
|
|
tristate "FTL (Flash Translation Layer) support"
|
2007-04-20 05:21:41 +08:00
|
|
|
depends on BLOCK
|
2006-11-21 10:15:36 +08:00
|
|
|
select MTD_BLKDEVS
|
2018-07-18 23:09:52 +08:00
|
|
|
help
|
2005-04-17 06:20:36 +08:00
|
|
|
This provides support for the original Flash Translation Layer which
|
|
|
|
|
is part of the PCMCIA specification. It uses a kind of pseudo-
|
|
|
|
|
file system on a flash device to emulate a block device with
|
|
|
|
|
512-byte sectors, on top of which you put a 'normal' file system.
|
|
|
|
|
|
|
|
|
|
You may find that the algorithms used in this code are patented
|
|
|
|
|
unless you live in the Free World where software patents aren't
|
|
|
|
|
legal - in the USA you are only permitted to use this on PCMCIA
|
|
|
|
|
hardware, although under the terms of the GPL you're obviously
|
|
|
|
|
permitted to copy, modify and distribute the code as you wish. Just
|
|
|
|
|
not use it.
|
|
|
|
|
|
|
|
|
|
config NFTL
|
|
|
|
|
tristate "NFTL (NAND Flash Translation Layer) support"
|
2007-04-20 05:21:41 +08:00
|
|
|
depends on BLOCK
|
2006-11-21 10:15:36 +08:00
|
|
|
select MTD_BLKDEVS
|
2018-07-18 23:09:52 +08:00
|
|
|
help
|
2005-04-17 06:20:36 +08:00
|
|
|
This provides support for the NAND Flash Translation Layer which is
|
|
|
|
|
used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
|
|
|
|
|
file system on a flash device to emulate a block device with
|
|
|
|
|
512-byte sectors, on top of which you put a 'normal' file system.
|
|
|
|
|
|
|
|
|
|
You may find that the algorithms used in this code are patented
|
|
|
|
|
unless you live in the Free World where software patents aren't
|
|
|
|
|
legal - in the USA you are only permitted to use this on DiskOnChip
|
|
|
|
|
hardware, although under the terms of the GPL you're obviously
|
|
|
|
|
permitted to copy, modify and distribute the code as you wish. Just
|
|
|
|
|
not use it.
|
|
|
|
|
|
|
|
|
|
config NFTL_RW
|
|
|
|
|
bool "Write support for NFTL"
|
|
|
|
|
depends on NFTL
|
|
|
|
|
help
|
|
|
|
|
Support for writing to the NAND Flash Translation Layer, as used
|
|
|
|
|
on the DiskOnChip.
|
|
|
|
|
|
|
|
|
|
config INFTL
|
|
|
|
|
tristate "INFTL (Inverse NAND Flash Translation Layer) support"
|
2007-04-20 05:21:41 +08:00
|
|
|
depends on BLOCK
|
2006-11-21 10:15:36 +08:00
|
|
|
select MTD_BLKDEVS
|
2018-07-18 23:09:52 +08:00
|
|
|
help
|
2005-11-07 19:15:26 +08:00
|
|
|
This provides support for the Inverse NAND Flash Translation
|
2005-04-17 06:20:36 +08:00
|
|
|
Layer which is used on M-Systems' newer DiskOnChip devices. It
|
|
|
|
|
uses a kind of pseudo-file system on a flash device to emulate
|
|
|
|
|
a block device with 512-byte sectors, on top of which you put
|
|
|
|
|
a 'normal' file system.
|
|
|
|
|
|
|
|
|
|
You may find that the algorithms used in this code are patented
|
|
|
|
|
unless you live in the Free World where software patents aren't
|
|
|
|
|
legal - in the USA you are only permitted to use this on DiskOnChip
|
|
|
|
|
hardware, although under the terms of the GPL you're obviously
|
|
|
|
|
permitted to copy, modify and distribute the code as you wish. Just
|
|
|
|
|
not use it.
|
|
|
|
|
|
2005-06-16 16:49:33 +08:00
|
|
|
config RFD_FTL
|
2018-07-18 23:09:52 +08:00
|
|
|
tristate "Resident Flash Disk (Flash Translation Layer) support"
|
2007-04-20 05:21:41 +08:00
|
|
|
depends on BLOCK
|
2006-11-21 10:15:36 +08:00
|
|
|
select MTD_BLKDEVS
|
2018-07-18 23:09:52 +08:00
|
|
|
help
|
2005-11-07 19:15:26 +08:00
|
|
|
This provides support for the flash translation layer known
|
|
|
|
|
as the Resident Flash Disk (RFD), as used by the Embedded BIOS
|
2005-07-11 18:41:53 +08:00
|
|
|
of General Software. There is a blurb at:
|
|
|
|
|
|
|
|
|
|
http://www.gensw.com/pages/prod/bios/rfd.htm
|
2005-06-16 16:49:33 +08:00
|
|
|
|
2006-09-22 18:01:37 +08:00
|
|
|
config SSFDC
|
2006-09-23 17:24:36 +08:00
|
|
|
tristate "NAND SSFDC (SmartMedia) read only translation layer"
|
2007-04-20 05:21:41 +08:00
|
|
|
depends on BLOCK
|
2006-11-21 10:15:36 +08:00
|
|
|
select MTD_BLKDEVS
|
2006-09-22 18:01:37 +08:00
|
|
|
help
|
|
|
|
|
This enables read only access to SmartMedia formatted NAND
|
|
|
|
|
flash. You can mount it with FAT file system.
|
|
|
|
|
|
2010-02-23 02:39:41 +08:00
|
|
|
config SM_FTL
|
|
|
|
|
tristate "SmartMedia/xD new translation layer"
|
2012-10-03 02:17:47 +08:00
|
|
|
depends on BLOCK
|
2010-02-23 02:39:41 +08:00
|
|
|
select MTD_BLKDEVS
|
2019-02-08 15:48:37 +08:00
|
|
|
select MTD_NAND_ECC_SW_HAMMING
|
2010-02-23 02:39:41 +08:00
|
|
|
help
|
2010-07-28 23:53:17 +08:00
|
|
|
This enables EXPERIMENTAL R/W support for SmartMedia/xD
|
2010-03-09 10:45:00 +08:00
|
|
|
FTL (Flash translation layer).
|
2010-07-28 23:53:17 +08:00
|
|
|
Write support is only lightly tested, therefore this driver
|
|
|
|
|
isn't recommended to use with valuable data (anyway if you have
|
|
|
|
|
valuable data, do backups regardless of software/hardware you
|
|
|
|
|
use, because you never know what will eat your data...)
|
|
|
|
|
If you only need R/O access, you can use older R/O driver
|
|
|
|
|
(CONFIG_SSFDC)
|
2010-02-23 02:39:41 +08:00
|
|
|
|
2007-05-29 20:31:42 +08:00
|
|
|
config MTD_OOPS
|
|
|
|
|
tristate "Log panic/oops to an MTD buffer"
|
|
|
|
|
help
|
|
|
|
|
This enables panic and oops messages to be logged to a circular
|
|
|
|
|
buffer in a flash partition where it can be read back at some
|
|
|
|
|
later point.
|
|
|
|
|
|
mtd: Support kmsg dumper based on pstore/blk
This introduces mtdpstore, which is similar to mtdoops but more
powerful. It uses pstore/blk, and aims to store panic and oops logs to
a flash partition, where pstore can later read back and present as files
in the mounted pstore filesystem.
To make mtdpstore work, the "blkdev" of pstore/blk should be set
as MTD device name or MTD device number. For more details, see
Documentation/admin-guide/pstore-blk.rst
This solves a number of issues:
- Work duplication: both of pstore and mtdoops do the same job storing
panic/oops log. They have very similar logic, registering to kmsg
dumper and storing logs to several chunks one by one.
- Layer violations: drivers should provides methods instead of polices.
MTD should provide read/write/erase operations, and allow a higher
level drivers to provide the chunk management, kmsg dump
configuration, etc.
- Missing features: pstore provides many additional features, including
presenting the logs as files, logging dump time and count, and
supporting other frontends like pmsg, console, etc.
Signed-off-by: WeiXiong Liao <liaoweixiong@allwinnertech.com>
Link: https://lore.kernel.org/lkml/20200511233229.27745-11-keescook@chromium.org/
Link: https://lore.kernel.org/r/1589266715-4168-1-git-send-email-liaoweixiong@allwinnertech.com
Signed-off-by: Kees Cook <keescook@chromium.org>
2020-03-25 16:55:06 +08:00
|
|
|
config MTD_PSTORE
|
|
|
|
|
tristate "Log panic/oops to an MTD buffer based on pstore"
|
|
|
|
|
depends on PSTORE_BLK
|
|
|
|
|
help
|
|
|
|
|
This enables panic and oops messages to be logged to a circular
|
|
|
|
|
buffer in a flash partition where it can be read back as files after
|
|
|
|
|
mounting pstore filesystem.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2011-02-14 22:16:11 +08:00
|
|
|
config MTD_SWAP
|
|
|
|
|
tristate "Swap on MTD device support"
|
|
|
|
|
depends on MTD && SWAP
|
|
|
|
|
select MTD_BLKDEVS
|
|
|
|
|
help
|
|
|
|
|
Provides volatile block device driver on top of mtd partition
|
2018-07-18 23:09:52 +08:00
|
|
|
suitable for swapping. The mapping of written blocks is not saved.
|
2011-02-14 22:16:11 +08:00
|
|
|
The driver provides wear leveling by storing erase counter into the
|
|
|
|
|
OOB.
|
|
|
|
|
|
2015-04-03 06:15:10 +08:00
|
|
|
config MTD_PARTITIONED_MASTER
|
|
|
|
|
bool "Retain master device when partitioned"
|
|
|
|
|
default n
|
|
|
|
|
depends on MTD
|
|
|
|
|
help
|
|
|
|
|
For historical reasons, by default, either a master is present or
|
|
|
|
|
several partitions are present, but not both. The concern was that
|
|
|
|
|
data listed in multiple partitions was dangerous; however, SCSI does
|
|
|
|
|
this and it is frequently useful for applications. This config option
|
|
|
|
|
leaves the master in even if the device is partitioned. It also makes
|
|
|
|
|
the parent of the partition device be the master device, rather than
|
|
|
|
|
what lies behind the master.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
source "drivers/mtd/chips/Kconfig"
|
|
|
|
|
|
|
|
|
|
source "drivers/mtd/maps/Kconfig"
|
|
|
|
|
|
|
|
|
|
source "drivers/mtd/devices/Kconfig"
|
|
|
|
|
|
|
|
|
|
source "drivers/mtd/nand/Kconfig"
|
|
|
|
|
|
2008-12-17 02:24:14 +08:00
|
|
|
source "drivers/mtd/lpddr/Kconfig"
|
|
|
|
|
|
2014-02-24 18:37:37 +08:00
|
|
|
source "drivers/mtd/spi-nor/Kconfig"
|
|
|
|
|
|
UBI: Unsorted Block Images
UBI (Latin: "where?") manages multiple logical volumes on a single
flash device, specifically supporting NAND flash devices. UBI provides
a flexible partitioning concept which still allows for wear-levelling
across the whole flash device.
In a sense, UBI may be compared to the Logical Volume Manager
(LVM). Whereas LVM maps logical sector numbers to physical HDD sector
numbers, UBI maps logical eraseblocks to physical eraseblocks.
More information may be found at
http://www.linux-mtd.infradead.org/doc/ubi.html
Partitioning/Re-partitioning
An UBI volume occupies a certain number of erase blocks. This is
limited by a configured maximum volume size, which could also be
viewed as the partition size. Each individual UBI volume's size can
be changed independently of the other UBI volumes, provided that the
sum of all volume sizes doesn't exceed a certain limit.
UBI supports dynamic volumes and static volumes. Static volumes are
read-only and their contents are protected by CRC check sums.
Bad eraseblocks handling
UBI transparently handles bad eraseblocks. When a physical
eraseblock becomes bad, it is substituted by a good physical
eraseblock, and the user does not even notice this.
Scrubbing
On a NAND flash bit flips can occur on any write operation,
sometimes also on read. If bit flips persist on the device, at first
they can still be corrected by ECC, but once they accumulate,
correction will become impossible. Thus it is best to actively scrub
the affected eraseblock, by first copying it to a free eraseblock
and then erasing the original. The UBI layer performs this type of
scrubbing under the covers, transparently to the UBI volume users.
Erase Counts
UBI maintains an erase count header per eraseblock. This frees
higher-level layers (like file systems) from doing this and allows
for centralized erase count management instead. The erase counts are
used by the wear-levelling algorithm in the UBI layer. The algorithm
itself is exchangeable.
Booting from NAND
For booting directly from NAND flash the hardware must at least be
capable of fetching and executing a small portion of the NAND
flash. Some NAND flash controllers have this kind of support. They
usually limit the window to a few kilobytes in erase block 0. This
"initial program loader" (IPL) must then contain sufficient logic to
load and execute the next boot phase.
Due to bad eraseblocks, which may be randomly scattered over the
flash device, it is problematic to store the "secondary program
loader" (SPL) statically. Also, due to bit-flips it may become
corrupted over time. UBI allows to solve this problem gracefully by
storing the SPL in a small static UBI volume.
UBI volumes vs. static partitions
UBI volumes are still very similar to static MTD partitions:
* both consist of eraseblocks (logical eraseblocks in case of UBI
volumes, and physical eraseblocks in case of static partitions;
* both support three basic operations - read, write, erase.
But UBI volumes have the following advantages over traditional
static MTD partitions:
* there are no eraseblock wear-leveling constraints in case of UBI
volumes, so the user should not care about this;
* there are no bit-flips and bad eraseblocks in case of UBI volumes.
So, UBI volumes may be considered as flash devices with relaxed
restrictions.
Where can it be found?
Documentation, kernel code and applications can be found in the MTD
gits.
What are the applications for?
The applications help to create binary flash images for two purposes: pfi
files (partial flash images) for in-system update of UBI volumes, and plain
binary images, with or without OOB data in case of NAND, for a manufacturing
step. Furthermore some tools are/and will be created that allow flash content
analysis after a system has crashed..
Who did UBI?
The original ideas, where UBI is based on, were developed by Andreas
Arnez, Frank Haverkamp and Thomas Gleixner. Josh W. Boyer and some others
were involved too. The implementation of the kernel layer was done by Artem
B. Bityutskiy. The user-space applications and tools were written by Oliver
Lohmann with contributions from Frank Haverkamp, Andreas Arnez, and Artem.
Joern Engel contributed a patch which modifies JFFS2 so that it can be run on
a UBI volume. Thomas Gleixner did modifications to the NAND layer. Alexander
Schmidt made some testing work as well as core functionality improvements.
Signed-off-by: Artem B. Bityutskiy <dedekind@linutronix.de>
Signed-off-by: Frank Haverkamp <haver@vnet.ibm.com>
2006-06-27 16:22:22 +08:00
|
|
|
source "drivers/mtd/ubi/Kconfig"
|
|
|
|
|
|
mtd: Add support for HyperBus memory devices
Cypress' HyperBus is Low Signal Count, High Performance Double Data Rate
Bus interface between a host system master and one or more slave
interfaces. HyperBus is used to connect microprocessor, microcontroller,
or ASIC devices with random access NOR flash memory (called HyperFlash)
or self refresh DRAM (called HyperRAM).
Its a 8-bit data bus (DQ[7:0]) with Read-Write Data Strobe (RWDS)
signal and either Single-ended clock(3.0V parts) or Differential clock
(1.8V parts). It uses ChipSelect lines to select b/w multiple slaves.
At bus level, it follows a separate protocol described in HyperBus
specification[1].
HyperFlash follows CFI AMD/Fujitsu Extended Command Set (0x0002) similar
to that of existing parallel NORs. Since HyperBus is x8 DDR bus,
its equivalent to x16 parallel NOR flash with respect to bits per clock
cycle. But HyperBus operates at >166MHz frequencies.
HyperRAM provides direct random read/write access to flash memory
array.
But, HyperBus memory controllers seem to abstract implementation details
and expose a simple MMIO interface to access connected flash.
Add support for registering HyperFlash devices with MTD framework. MTD
maps framework along with CFI chip support framework are used to support
communicating with flash.
Framework is modelled along the lines of spi-nor framework. HyperBus
memory controller (HBMC) drivers calls hyperbus_register_device() to
register a single HyperFlash device. HyperFlash core parses MMIO access
information from DT, sets up the map_info struct, probes CFI flash and
registers it with MTD framework.
Some HBMC masters need calibration/training sequence[3] to be carried
out, in order for DLL inside the controller to lock, by reading a known
string/pattern. This is done by repeatedly reading CFI Query
Identification String. Calibration needs to be done before trying to detect
flash as part of CFI flash probe.
HyperRAM is not supported at the moment.
HyperBus specification can be found at[1]
HyperFlash datasheet can be found at[2]
[1] https://www.cypress.com/file/213356/download
[2] https://www.cypress.com/file/213346/download
[3] http://www.ti.com/lit/ug/spruid7b/spruid7b.pdf
Table 12-5741. HyperFlash Access Sequence
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
2019-06-25 15:57:44 +08:00
|
|
|
source "drivers/mtd/hyperbus/Kconfig"
|
|
|
|
|
|
2007-04-20 05:21:41 +08:00
|
|
|
endif # MTD
|