1 Representing flash partitions in devicetree
3 Partitions can be represented by sub-nodes of an mtd device. This can be used
4 on platforms which have strong conventions about which portions of a flash are
5 used for what purposes, but which don't use an on-flash partition table such
8 The partition table should be a subnode of the mtd node and should be named
9 'partitions'. Partitions are defined in subnodes of the partitions node.
11 For backwards compatibility partitions as direct subnodes of the mtd device are
12 supported. This use is discouraged.
13 NOTE: also for backwards compatibility, direct subnodes that have a compatible
14 string are not considered partitions, as they may be used for other bindings.
16 #address-cells & #size-cells must both be present in the partitions subnode of the
17 mtd device. There are two valid values for both:
18 <1>: for partitions that require a single 32-bit cell to represent their
19 size/address (aka the value is below 4 GiB)
20 <2>: for partitions that require two 32-bit cells to represent their
21 size/address (aka the value is 4 GiB or greater).
24 - reg : The partition's offset and size within the mtd bank.
27 - label : The label / name for this partition. If omitted, the label is taken
28 from the node name (excluding the unit address).
29 - read-only : This parameter, if present, is a hint to Linux that this
30 partition should only be mounted read-only. This is usually used for flash
31 partitions containing early-boot firmware images or data which should not be
44 reg = <0x0000000 0x100000>;
49 reg = <0x0100000 0x200000>;
59 /* a 4 GiB partition */
62 reg = <0x00000000 0x1 0x00000000>;
72 /* an 8 GiB partition */
74 label = "filesystem #1";
75 reg = <0x0 0x00000000 0x2 0x00000000>;
78 /* a 4 GiB partition */
80 label = "filesystem #2";
81 reg = <0x2 0x00000000 0x1 0x00000000>;