mirrors/linux-stable
1
0
Fork 0
mirror of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git synced 2024-09-29 22:02:02 +00:00
Code Issues Releases Wiki Activity

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

Browse source 
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

19
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,6 +35,7 @@ Examples:
flash@0 { flash@0 {
partitions {
#address-cells = <1>; #address-cells = <1>;
#size-cells = <1>; #size-cells = <1>;
@ -41,8 +49,10 @@ flash@0 {
reg = <0x0100000 0x200000>; reg = <0x0100000 0x200000>;
}; };
}; };
};
flash@1 { flash@1 {
partitions {
#address-cells = <1>; #address-cells = <1>;
#size-cells = <2>; #size-cells = <2>;
@ -52,8 +62,10 @@ flash@1 {
reg = <0x00000000 0x1 0x00000000>; reg = <0x00000000 0x1 0x00000000>;
}; };
}; };
};
flash@2 { flash@2 {
partitions {
#address-cells = <2>; #address-cells = <2>;
#size-cells = <2>; #size-cells = <2>;
@ -69,3 +81,4 @@ flash@2 {
reg = <0x2 0x00000000 0x1 0x00000000>; reg = <0x2 0x00000000 0x1 0x00000000>;
}; };
}; };
};