From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/9] Documentation: DT: Document SMP DT nodes and properties for BCM63138
Date: Thu, 23 Apr 2015 16:09:56 -0700 [thread overview]
Message-ID: <1429830602-10988-4-git-send-email-f.fainelli@gmail.com> (raw)
In-Reply-To: <1429830602-10988-1-git-send-email-f.fainelli@gmail.com>
Add binding documentation for the additional nodes and properties
required to get the secondary CPU online on the BCM63138 SoC.
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
---
.../devicetree/bindings/arm/bcm/brcm,bcm63138.txt | 42 ++++++++++++++++++++++
1 file changed, 42 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/bcm/brcm,bcm63138.txt b/Documentation/devicetree/bindings/arm/bcm/brcm,bcm63138.txt
index bd49987a8812..999e074b8ac3 100644
--- a/Documentation/devicetree/bindings/arm/bcm/brcm,bcm63138.txt
+++ b/Documentation/devicetree/bindings/arm/bcm/brcm,bcm63138.txt
@@ -7,3 +7,45 @@ following properties:
Required root node property:
compatible: should be "brcm,bcm63138"
+
+An optional Boot lookup table Device Tree node is required for secondary CPU
+initialization as well as a 'resets' phandle to the correct PMB controller as
+defined in reset/brcm,bcm63138-pmb.txt for this secondary CPU, and an
+'enable-method' property.
+
+Required properties for the Boot lookup table node:
+- compatible: should be "brcm,bcm63138-bootlut"
+- reg: register base address and length for the Boot Lookup table
+
+Optional properties for the primary CPU node:
+- enable-method: should be "brcm,bcm63138"
+
+Optional properties for the secondary CPU node:
+- enable-method: should be "brcm,bcm63138"
+- resets: phandle to the relevant PMB controller, one integer indicating the internal
+ bus number, and a second integer indicating the address of the CPU in the PMB
+ internal bus number.
+
+Example:
+
+ cpus {
+ cpu at 0 {
+ compatible = "arm,cotex-a9";
+ reg = <0>;
+ ...
+ enable-method = "brcm,bcm63138";
+ };
+
+ cpu at 1 {
+ compatible = "arm,cortex-a9";
+ reg = <1>;
+ ...
+ enable-method = "brcm,bcm63138";
+ resets = <&pmb0 4 1>;
+ };
+ };
+
+ bootlut: bootlut at 8000 {
+ compatible = "brcm,bcm63138-bootlut";
+ reg = <0x8000 0x50>;
+ };
--
2.1.0
next prev parent reply other threads:[~2015-04-23 23:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 23:09 [PATCH v2 0/9] ARM: BCM63xx: SMP support (v2) Florian Fainelli
2015-04-23 23:09 ` [PATCH v2 1/9] Documentation: DT: Add Broadcom BCM63138 PMB binding Florian Fainelli
2015-04-23 23:09 ` [PATCH v2 2/9] ARM: dts: BCM63xx: Add PMB busses nodes Florian Fainelli
2015-04-23 23:09 ` Florian Fainelli [this message]
2015-04-23 23:09 ` [PATCH v2 4/9] ARM: dts: BCM63xx: Add SMP nodes and required properties Florian Fainelli
2015-04-23 23:09 ` [PATCH v2 5/9] ARM: BCM63xx: Add Broadcom BCM63xx PMB controller helpers Florian Fainelli
2015-04-23 23:09 ` [PATCH v2 6/9] ARM: BCM63xx: Add secondary CPU PMB initialization sequence Florian Fainelli
2015-04-23 23:10 ` [PATCH v2 7/9] ARM: vfp: Add include guards Florian Fainelli
2015-04-23 23:10 ` [PATCH v2 8/9] ARM: vfp: Add vfp_disable for problematic platforms Florian Fainelli
2015-04-23 23:10 ` [PATCH v2 9/9] ARM: BCM63xx: Add SMP support for BCM63138 Florian Fainelli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1429830602-10988-4-git-send-email-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).