From: "Christian Daudt" <csd@broadcom.com>
To: Russell King <linux@arm.linux.org.uk>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
Stephen Warren <swarren@wwwdotorg.org>,
abhimanyu.kapur@outlook.com,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
Rob Landley <rob@landley.net>
Cc: Christian Daudt <csd@broadcom.com>,
csd_b@daudt.org, devicetree-discuss@lists.ozlabs.org,
"arm@kernel.org" <arm@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 2/2] ARM: bcm281xx: Add DT support for SMC handler
Date: Thu, 14 Mar 2013 15:14:28 -0700 [thread overview]
Message-ID: <1363299268-10506-2-git-send-email-csd@broadcom.com> (raw)
In-Reply-To: <1363299268-10506-1-git-send-email-csd@broadcom.com>
- Adds devicetree binding and documentation for the smc handler
Updates from V1:
- Created this separate patch for the DT portion
- Added SoC compatible to smc binding
Signed-off-by: Christian Daudt <csd@broadcom.com>
diff --git a/Documentation/devicetree/bindings/misc/smc.txt b/Documentation/devicetree/bindings/misc/smc.txt
new file mode 100644
index 0000000..02b4281
--- /dev/null
+++ b/Documentation/devicetree/bindings/misc/smc.txt
@@ -0,0 +1,14 @@
+Broadcom Secure Monitor Bounce buffer
+-----------------------------------------------------
+This binding defines the location of the bounce buffer
+used for non-secure to secure communications.
+
+Required properties:
+- compatible : "bcm,kona-smc"
+- reg : Location and size of bounce buffer
+
+Example:
+ smc@0x3404c000 {
+ compatible = "bcm,bcm11351-smc", "bcm,kona-smc";
+ reg = <0x3404c000 0x400>; //1 KiB in SRAM
+ };
diff --git a/arch/arm/boot/dts/bcm11351.dtsi b/arch/arm/boot/dts/bcm11351.dtsi
index 8f71f40..b2b9d80 100644
--- a/arch/arm/boot/dts/bcm11351.dtsi
+++ b/arch/arm/boot/dts/bcm11351.dtsi
@@ -55,4 +55,9 @@
clock-frequency = <32768>;
};
+ smc@0x3404c000 {
+ compatible = "bcm,bcm11351-smc", "bcm,kona-smc";
+ reg = <0x3404c000 0x400>; //1 KiB in SRAM
+ };
+
};
--
1.7.10.4
next prev parent reply other threads:[~2013-03-14 22:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 22:14 [PATCH V2 1/2] ARM: bcm281xx: Add L2 cache enable code Christian Daudt
2013-03-14 22:14 ` Christian Daudt [this message]
[not found] ` <1363299268-10506-2-git-send-email-csd-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2013-04-05 17:16 ` [PATCH V2 2/2] ARM: bcm281xx: Add DT support for SMC handler Christian Daudt
[not found] ` <1363299268-10506-1-git-send-email-csd-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2013-04-03 21:16 ` [PATCH V2 1/2] ARM: bcm281xx: Add L2 cache enable code Christian Daudt
[not found] ` <CAGFynZ9pE_B8KQNQvWsyn4Yz7tdd5VQwm=c76S-SPsGKNgu9ug-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-04 11:23 ` Arnd Bergmann
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=1363299268-10506-2-git-send-email-csd@broadcom.com \
--to=csd@broadcom.com \
--cc=abhimanyu.kapur@outlook.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=csd_b@daudt.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=swarren@wwwdotorg.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).