devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Markus Mayer <code@mmayer.net>
To: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Gregory Fong <gregory.0xf0@gmail.com>
Cc: Device Tree List <devicetree@vger.kernel.org>,
	Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
	ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
	Markus Mayer <mmayer@broadcom.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH v2 1/2] dt/bindings: Add bindings for Broadcom STB DRAM Sensors
Date: Tue, 13 Jun 2017 15:37:09 -0700	[thread overview]
Message-ID: <20170613223710.31719-2-code@mmayer.net> (raw)
In-Reply-To: <20170613223710.31719-1-code@mmayer.net>

From: Markus Mayer <mmayer@broadcom.com>

Provide bindings for the Broadcom STB DDR PHY Front End (DPFE).

Signed-off-by: Markus Mayer <mmayer@broadcom.com>
---
 .../devicetree/bindings/soc/bcm/brcm,dpfe-cpu.txt  | 27 ++++++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/soc/bcm/brcm,dpfe-cpu.txt

diff --git a/Documentation/devicetree/bindings/soc/bcm/brcm,dpfe-cpu.txt b/Documentation/devicetree/bindings/soc/bcm/brcm,dpfe-cpu.txt
new file mode 100644
index 0000000..82d923e
--- /dev/null
+++ b/Documentation/devicetree/bindings/soc/bcm/brcm,dpfe-cpu.txt
@@ -0,0 +1,27 @@
+DDR PHY Front End (DPFE) for Broadcom STB
+=========================================
+
+DPFE and the DPFE firmware provide an interface for the host CPU to
+communicate with the DCPU, which resides inside the DDR PHY.
+
+There are three memory regions for interacting with the DCPU. These are
+specified in a single reg property.
+
+Required properties:
+  - compatible: must be "brcm,bcm7271-dpfe-cpu", "brcm,bcm7268-dpfe-cpu"
+    or "brcm,dpfe-cpu"
+  - reg: must reference three register ranges
+      - start address and length of the DCPU register space
+      - start address and length of the DCPU data memory space
+      - start address and length of the DCPU instruction memory space
+  - reg-names: must contain "dpfe-cpu", "dpfe-dmem", and "dpfe-imem";
+        they must be in the same order as the register declarations
+
+Example:
+	dpfe_cpu0: dpfe-cpu@f1132000 {
+		compatible = "brcm,bcm7271-dpfe-cpu", "brcm,dpfe-cpu";
+		reg =  <0xf1132000 0x180
+			0xf1134000 0x1000
+			0xf1138000 0x4000>;
+		reg-names = "dpfe-cpu", "dpfe-dmem", "dpfe-imem";
+	};
-- 
2.7.4

  reply	other threads:[~2017-06-13 22:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 22:37 [PATCH v2 0/2] SoC driver for Broadcom STB DPFE Markus Mayer
2017-06-13 22:37 ` Markus Mayer [this message]
2017-06-18 14:05   ` [PATCH v2 1/2] dt/bindings: Add bindings for Broadcom STB DRAM Sensors Rob Herring
2017-06-19 17:26     ` Markus Mayer
     [not found]       ` <CANEuBv6YEoTBBzPA5fkrveD05RZNtTBTak-qmxz7BvnrED5pbg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-21 20:44         ` Florian Fainelli
     [not found]   ` <20170613223710.31719-2-code-7CzEARzsJhSsTnJN9+BGXg@public.gmane.org>
2017-06-21 21:02     ` Florian Fainelli
2017-06-13 22:37 ` [PATCH v2 2/2] soc: brcmstb: Add driver for DPFE Markus Mayer
     [not found]   ` <20170613223710.31719-3-code-7CzEARzsJhSsTnJN9+BGXg@public.gmane.org>
2017-06-14  0:03     ` Florian Fainelli
     [not found]       ` <5b79dee6-bb84-30b3-1bb2-287b24d42534-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-06-14 16:34         ` Markus Mayer
     [not found]           ` <CANEuBv6N3TTNzSuDQXk-eiEV_fvGtVJZhdWUO_XdgPj6+j7q5A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-14 21:32             ` Florian Fainelli
2017-06-21 21:00               ` Florian Fainelli
     [not found]                 ` <a59aab64-b351-2e16-a5ab-b2ac41ffbf5e-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-06-21 21:01                   ` 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=20170613223710.31719-2-code@mmayer.net \
    --to=code@mmayer.net \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregory.0xf0@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mmayer@broadcom.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).