summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/arm/bcm/brcm,bcm23550-cpu-method.txt
diff options
context:
space:
mode:
authorFlorian Fainelli <f.fainelli@gmail.com>2020-02-04 15:55:51 -0800
committerFlorian Fainelli <f.fainelli@gmail.com>2020-03-10 12:43:15 -0700
commit14e1eb5a91a96d9e1ce8051f752b7b6645bc8e10 (patch)
treed98e7da1b457dee899bbb6ff04a04c39e7b1184b /Documentation/devicetree/bindings/arm/bcm/brcm,bcm23550-cpu-method.txt
parentb63b50ab0613a3e8b53441668219e96a61a17b6b (diff)
dt-bindings: arm: Document Broadcom SoCs 'secondary-boot-reg'
Consolidate and move the 'secondary-boot-reg' property from the 3 existing binding documents into the main cpus.yaml documentation, also make sure that the property is enforced when relevant. Acked-by: Maxime Ripard <mripard@kernel.org> Acked-by: Scott Branden <scott.branden@broadcom.com> Reviewed-by: Rob Herring <robh@kernel.org> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Diffstat (limited to 'Documentation/devicetree/bindings/arm/bcm/brcm,bcm23550-cpu-method.txt')
-rw-r--r--Documentation/devicetree/bindings/arm/bcm/brcm,bcm23550-cpu-method.txt36
1 files changed, 0 insertions, 36 deletions
diff --git a/Documentation/devicetree/bindings/arm/bcm/brcm,bcm23550-cpu-method.txt b/Documentation/devicetree/bindings/arm/bcm/brcm,bcm23550-cpu-method.txt
deleted file mode 100644
index a3af54c0e404..000000000000
--- a/Documentation/devicetree/bindings/arm/bcm/brcm,bcm23550-cpu-method.txt
+++ /dev/null
@@ -1,36 +0,0 @@
-Broadcom Kona Family CPU Enable Method
---------------------------------------
-This binding defines the enable method used for starting secondary
-CPUs in the following Broadcom SoCs:
- BCM23550
-
-The enable method is specified by defining the following required
-properties in the "cpu" device tree node:
- - enable-method = "brcm,bcm23550";
- - secondary-boot-reg = <...>;
-
-The secondary-boot-reg property is a u32 value that specifies the
-physical address of the register used to request the ROM holding pen
-code release a secondary CPU. The value written to the register is
-formed by encoding the target CPU id into the low bits of the
-physical start address it should jump to.
-
-Example:
- cpus {
- #address-cells = <1>;
- #size-cells = <0>;
-
- cpu0: cpu@0 {
- device_type = "cpu";
- compatible = "arm,cortex-a9";
- reg = <0>;
- };
-
- cpu1: cpu@1 {
- device_type = "cpu";
- compatible = "arm,cortex-a9";
- reg = <1>;
- enable-method = "brcm,bcm23550";
- secondary-boot-reg = <0x3500417c>;
- };
- };