From: Ray Jui <ray.jui@broadcom.com>
To: Lee Jones <lee.jones@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>
Cc: bcm-kernel-feedback-list@broadcom.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ray Jui <ray.jui@broadcom.com>
Subject: [PATCH 1/2] syscon: dt-bindings: Add binding doc for Broadcom iProc CDRU
Date: Wed,  6 Sep 2017 17:27:41 -0700	[thread overview]
Message-ID: <1504744062-5941-2-git-send-email-ray.jui@broadcom.com> (raw)
In-Reply-To: <1504744062-5941-1-git-send-email-ray.jui@broadcom.com>
Add binding document for Broadcom iProc's Chip Device Resource Unit
(CDRU). Multiple iProc based chips have this CDRU block that contains
miscellaneous registers for chip or device configurations. Start with
Stingray specific compatible string for the initial binding
Signed-off-by: Ray Jui <ray.jui@broadcom.com>
Reviewed-by: Scott Branden <scott.branden@broadcom.com>
---
 .../devicetree/bindings/mfd/brcm,iproc-cdru.txt          | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/mfd/brcm,iproc-cdru.txt
diff --git a/Documentation/devicetree/bindings/mfd/brcm,iproc-cdru.txt b/Documentation/devicetree/bindings/mfd/brcm,iproc-cdru.txt
new file mode 100644
index 0000000..82f82e0
--- /dev/null
+++ b/Documentation/devicetree/bindings/mfd/brcm,iproc-cdru.txt
@@ -0,0 +1,16 @@
+Broadcom iProc Chip Device Resource Unit (CDRU)
+
+Various Broadcom iProc SoCs have a set of registers that provide various
+chip specific device and resource configurations. This node allows access to
+these CDRU registers via syscon.
+
+Required properties:
+- compatible: should contain:
+		"brcm,sr-cdru", "syscon" for Stingray
+- reg: base address and range of the CDRU registers
+
+Example:
+	cdru: syscon@6641d000 {
+		compatible = "brcm,sr-cdru", "syscon";
+		reg = <0 0x6641d000 0 0x400>;
+	};
-- 
2.1.4
next prev parent reply	other threads:[~2017-09-07  0:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-07  0:27 [PATCH 0/2] Binding document for iProc CDRU and MHB Ray Jui
2017-09-07  0:27 ` Ray Jui [this message]
2017-09-07  7:59   ` [PATCH 1/2] syscon: dt-bindings: Add binding doc for Broadcom iProc CDRU Lee Jones
     [not found] ` <1504744062-5941-1-git-send-email-ray.jui-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2017-09-07  0:27   ` [PATCH 2/2] syscon: dt-bindings: Add binding document for iProc MHB block Ray Jui
     [not found]     ` <1504744062-5941-3-git-send-email-ray.jui-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2017-09-07  7:59       ` Lee Jones
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=1504744062-5941-2-git-send-email-ray.jui@broadcom.com \
    --to=ray.jui@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.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).