summaryrefslogtreecommitdiff
path: root/Bindings/mtd/mtd-physmap.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Bindings/mtd/mtd-physmap.txt')
-rw-r--r--Bindings/mtd/mtd-physmap.txt9
1 files changed, 7 insertions, 2 deletions
diff --git a/Bindings/mtd/mtd-physmap.txt b/Bindings/mtd/mtd-physmap.txt
index 61c5ec850f2f..4a0a48bf4ecb 100644
--- a/Bindings/mtd/mtd-physmap.txt
+++ b/Bindings/mtd/mtd-physmap.txt
@@ -4,8 +4,8 @@ Flash chips (Memory Technology Devices) are often used for solid state
file systems on embedded devices.
- compatible : should contain the specific model of mtd chip(s)
- used, if known, followed by either "cfi-flash", "jedec-flash"
- or "mtd-ram".
+ used, if known, followed by either "cfi-flash", "jedec-flash",
+ "mtd-ram" or "mtd-rom".
- reg : Address range(s) of the mtd chip(s)
It's possible to (optionally) define multiple "reg" tuples so that
non-identical chips can be described in one node.
@@ -36,6 +36,11 @@ are defined:
- vendor-id : Contains the flash chip's vendor id (1 byte).
- device-id : Contains the flash chip's device id (1 byte).
+For ROM compatible devices (and ROM fallback from cfi-flash), the following
+additional (optional) property is defined:
+
+ - erase-size : The chip's physical erase block size in bytes.
+
The device tree may optionally contain sub-nodes describing partitions of the
address space. See partition.txt for more detail.