hollalinux
/
linux-sg2042
mirror of https://github.com/sophgo/linux-riscv.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: dt: mtd: support partitions in a special 'partitions' subnode 

To avoid conflict with other drivers using subnodes of the mtd device
create only one ofpart-specific node rather than any number of
arbitrary partition subnodes.

Signed-off-by: Michal Suchanek <hramrach@gmail.com>
Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
This commit is contained in:
Michal Suchanek 2015-10-28 15:48:06 -07:00 committed by Brian Norris
parent 4d1ea982a9
commit fe2585e9c2
1 changed files with 42 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

71
Documentation/devicetree/bindings/mtd/partition.txt
View File

@ -4,10 +4,17 @@ Partitions can be represented by sub-nodes of an mtd device. This can be used
on platforms which have strong conventions about which portions of a flash are on platforms which have strong conventions about which portions of a flash are
used for what purposes, but which don't use an on-flash partition table such used for what purposes, but which don't use an on-flash partition table such
as RedBoot. as RedBoot.
NOTE: if the sub-node has a compatible string, then it is not a partition.
#address-cells & #size-cells must both be present in the mtd device. There are The partition table should be a subnode of the mtd node and should be named
two valid values for both: 'partitions'. Partitions are defined in subnodes of the partitions node.
For backwards compatibility partitions as direct subnodes of the mtd device are
supported. This use is discouraged.
NOTE: also for backwards compatibility, direct subnodes that have a compatible
string are not considered partitions, as they may be used for other bindings.
#address-cells & #size-cells must both be present in the partitions subnode of the
mtd device. There are two valid values for both:
<1>: for partitions that require a single 32-bit cell to represent their <1>: for partitions that require a single 32-bit cell to represent their
size/address (aka the value is below 4 GiB) size/address (aka the value is below 4 GiB)
<2>: for partitions that require two 32-bit cells to represent their <2>: for partitions that require two 32-bit cells to represent their
@ -28,44 +35,50 @@ Examples:
flash@0 { flash@0 {
#address-cells = <1>; partitions {
#size-cells = <1>; #address-cells = <1>;
#size-cells = <1>;
partition@0 { partition@0 {
label = "u-boot"; label = "u-boot";
reg = <0x0000000 0x100000>; reg = <0x0000000 0x100000>;
read-only; read-only;
}; };
uimage@100000 { uimage@100000 {
reg = <0x0100000 0x200000>; reg = <0x0100000 0x200000>;
};
}; };
}; };
flash@1 { flash@1 {
#address-cells = <1>; partitions {
#size-cells = <2>; #address-cells = <1>;
#size-cells = <2>;
/* a 4 GiB partition */ /* a 4 GiB partition */
partition@0 { partition@0 {
label = "filesystem"; label = "filesystem";
reg = <0x00000000 0x1 0x00000000>; reg = <0x00000000 0x1 0x00000000>;
};
}; };
}; };
flash@2 { flash@2 {
#address-cells = <2>; partitions {
#size-cells = <2>; #address-cells = <2>;
#size-cells = <2>;
/* an 8 GiB partition */ /* an 8 GiB partition */
partition@0 { partition@0 {
label = "filesystem #1"; label = "filesystem #1";
reg = <0x0 0x00000000 0x2 0x00000000>; reg = <0x0 0x00000000 0x2 0x00000000>;
}; };
/* a 4 GiB partition */ /* a 4 GiB partition */
partition@200000000 { partition@200000000 {
label = "filesystem #2"; label = "filesystem #2";
reg = <0x2 0x00000000 0x1 0x00000000>; reg = <0x2 0x00000000 0x1 0x00000000>;
};
}; };
}; };