bindings/mtd/partition.txt

4 Flash devices can be partitioned into one or more functional ranges (e.g. "boot
8 flash layout set at production time. Some may use on-flash table that describes
13 method is used for a given flash device. To describe the method there should be
15 'compatible' property, which is used to identify the method to use.
20 hierarchical (multi-level) layouts and should be used if there is some
22 another partitioning method.
30 Partitions can be represented by sub-nodes of a flash device. This can be used
32 used for what purposes, but which don't use an on-flash partition table such
37 - compatible : (required) must be "fixed-partitions"
45 #address-cells & #size-cells must both be present in the partitions subnode of the
47 <1>: for partitions that require a single 32-bit cell to represent their
49 <2>: for partitions that require two 32-bit cells to represent their
53 - reg : The partition's offset and size within the flash
56 - label : The label / name for this partition.  If omitted, the label is taken
58 - read-only : This parameter, if present, is a hint to Linux that this
59   partition should only be mounted read-only. This is usually used for flash
60   partitions containing early-boot firmware images or data which should not be
62 - lock : Do not unlock the partition at initialization time (not supported on
64 - slc-mode: This parameter, if present, allows one to emulate SLC mode on a
66   paired-pages corruptions
73 		compatible = "fixed-partitions";
74 		#address-cells = <1>;
75 		#size-cells = <1>;
78 			label = "u-boot";
80 			read-only;
91 		compatible = "fixed-partitions";
92 		#address-cells = <1>;
93 		#size-cells = <2>;
105 		compatible = "fixed-partitions";
106 		#address-cells = <2>;
107 		#size-cells = <2>;
125 		compatible = "fixed-partitions";
126 		#address-cells = <1>;
127 		#size-cells = <1>;
132 			read-only;
144 			compatible = "fixed-partitions";
146 			#address-cells = <1>;
147 			#size-cells = <1>;