From: jingchang.lu@freescale.com (Jingchang Lu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv5 4/6] dt-bindings: arm: add Freescale LS1021A SoC device tree binding
Date: Mon, 13 Oct 2014 17:36:01 +0800 [thread overview]
Message-ID: <1413192963-11153-5-git-send-email-jingchang.lu@freescale.com> (raw)
In-Reply-To: <1413192963-11153-1-git-send-email-jingchang.lu@freescale.com>
Signed-off-by: Jingchang Lu <jingchang.lu@freescale.com>
---
Documentation/devicetree/bindings/arm/fsl.txt | 38 +++++++++++++++++++++++++++
1 file changed, 38 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/fsl.txt b/Documentation/devicetree/bindings/arm/fsl.txt
index e935d7d..4e8b7df 100644
--- a/Documentation/devicetree/bindings/arm/fsl.txt
+++ b/Documentation/devicetree/bindings/arm/fsl.txt
@@ -74,3 +74,41 @@ Required root node properties:
i.MX6q generic board
Required root node properties:
- compatible = "fsl,imx6q";
+
+
+Freescale LS1021A Platform Device Tree Bindings
+------------------------------------------------
+
+Required root node compatible properties:
+ - compatible = "fsl,ls1021a";
+
+Freescale LS1021A SoC-specific Device Tree Bindings
+-------------------------------------------
+
+Freescale SCFG
+ SCFG is the supplemental configuration unit, that provides SoC specific
+configuration and status registers for the chip. Such as getting PEX port
+status.
+ Required properties:
+ - compatible: should be "fsl,ls1021a-scfg"
+ - reg: should contain base address and length of SCFG memory-mapped registers
+
+Example:
+ scfg: scfg at 1570000 {
+ compatible = "fsl,ls1021a-scfg";
+ reg = <0x0 0x1570000 0x0 0x10000>;
+ };
+
+Freescale DCFG
+ DCFG is the device configuration unit, that provides general purpose
+configuration and status for the device. Such as setting the secondary
+core start address and release the secondary core from holdoff and startup.
+ Required properties:
+ - compatible: should be "fsl,ls1021a-dcfg"
+ - reg : should contain base address and length of DCFG memory-mapped registers
+
+Example:
+ dcfg: dcfg at 1ee0000 {
+ compatible = "fsl,ls1021a-dcfg";
+ reg = <0x0 0x1ee0000 0x0 0x10000>;
+ };
--
1.8.0
next prev parent reply other threads:[~2014-10-13 9:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 9:35 [PATCHv5 0/6] ARM: imx: Add Freescale LS1021A SoC and board support Jingchang Lu
2014-10-13 9:35 ` [PATCHv5 1/6] ARM: dts: Add SoC level device tree support for LS1021A Jingchang Lu
2014-10-19 1:17 ` Shawn Guo
2014-10-19 19:17 ` Arnd Bergmann
2014-10-19 1:37 ` Shawn Guo
2014-10-21 1:53 ` Jingchang Lu
2014-10-13 9:35 ` [PATCHv5 2/6] ARM: dts: Add initial LS1021A QDS board dts support Jingchang Lu
2014-10-19 1:44 ` Shawn Guo
2014-10-13 9:36 ` [PATCHv5 3/6] ARM: dts: Add initial LS1021A TWR " Jingchang Lu
2014-10-19 1:49 ` Shawn Guo
2014-10-13 9:36 ` Jingchang Lu [this message]
2014-10-13 9:36 ` [PATCHv5 5/6] ARM: imx: Add initial support for Freescale LS1021A Jingchang Lu
2014-10-13 9:36 ` [PATCHv5 6/6] ARM: imx: Add Freescale LS1021A SMP support Jingchang Lu
2014-10-16 14:30 ` Kumar Gala
2014-10-17 10:10 ` Jingchang Lu
2014-10-17 12:27 ` Kumar Gala
2014-10-20 11:34 ` Jingchang Lu
2014-10-19 2:19 ` Shawn Guo
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=1413192963-11153-5-git-send-email-jingchang.lu@freescale.com \
--to=jingchang.lu@freescale.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).