summaryrefslogtreecommitdiffstats
path: root/dts/Bindings/mtd/partitions/brcm,bcm963xx-cfe-nor-partitions.txt
diff options
context:
space:
mode:
Diffstat (limited to 'dts/Bindings/mtd/partitions/brcm,bcm963xx-cfe-nor-partitions.txt')
-rw-r--r--dts/Bindings/mtd/partitions/brcm,bcm963xx-cfe-nor-partitions.txt24
1 files changed, 24 insertions, 0 deletions
diff --git a/dts/Bindings/mtd/partitions/brcm,bcm963xx-cfe-nor-partitions.txt b/dts/Bindings/mtd/partitions/brcm,bcm963xx-cfe-nor-partitions.txt
new file mode 100644
index 0000000..9f630e9
--- /dev/null
+++ b/dts/Bindings/mtd/partitions/brcm,bcm963xx-cfe-nor-partitions.txt
@@ -0,0 +1,24 @@
+Broadcom BCM963XX CFE Loader NOR Flash Partitions
+=================================================
+
+Most Broadcom BCM63XX SoC based devices follow the Broadcom reference layout for
+NOR. The first erase block used for the CFE bootloader, the last for an
+NVRAM partition, and the remainder in-between for one to two firmware partitions
+at fixed offsets. A valid firmware partition is identified by the ImageTag
+header found at beginning of the second erase block, containing the rootfs and
+kernel offsets and sizes within the firmware partition.
+
+Required properties:
+- compatible : must be "brcm,bcm963xx-cfe-nor-partitions"
+
+Example:
+
+flash@1fc00000 {
+ compatible = "cfi-flash";
+ reg = <0x1fc00000 0x400000>;
+ bank-width = <2>;
+
+ partitions {
+ compatible = "brcm,bcm963xx-cfe-nor-partitions";
+ };
+};