From: Markus Mayer <mmayer@broadcom.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Rob Herring <robh+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Markus Mayer <mmayer@broadcom.com>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
Device Tree Mailing List <devicetree@vger.kernel.org>
Subject: [PATCH v2 3/5] dt-bindings: memory: additional compatible strings for Broadcom DPFE
Date: Fri, 19 Jan 2024 13:52:26 -0800 [thread overview]
Message-ID: <20240119215231.758844-4-mmayer@broadcom.com> (raw)
In-Reply-To: <20240119215231.758844-1-mmayer@broadcom.com>
Add versioned compatible strings for Broadcom DPFE. These take the form
brcm,dpfe-cpu-v<N> where <N> is a number from 1 to 4.
The chip-specific strings have been kept for compatibility purposes
(hardware is in the field). For new chips, the properly versioned
compatible string should be used.
Signed-off-by: Markus Mayer <mmayer@broadcom.com>
---
.../memory-controllers/brcm,dpfe-cpu.yaml | 21 ++++++++++++++++++-
1 file changed, 20 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/memory-controllers/brcm,dpfe-cpu.yaml b/Documentation/devicetree/bindings/memory-controllers/brcm,dpfe-cpu.yaml
index 3f00bc2fd3ec..42c8160d95d1 100644
--- a/Documentation/devicetree/bindings/memory-controllers/brcm,dpfe-cpu.yaml
+++ b/Documentation/devicetree/bindings/memory-controllers/brcm,dpfe-cpu.yaml
@@ -10,9 +10,28 @@ maintainers:
- Krzysztof Kozlowski <krzk@kernel.org>
- Markus Mayer <mmayer@broadcom.com>
+description: |
+
+ The DCPU (DDR PHY Front End CPU) interfaces directly with the DDR PHY
+ chip on Broadcom STB SoCs. An API exists for other agents to retrieve
+ or set certain DDR PHY chip parameters by JEDEC.
+
+ Different, incompatible versions of this API have been created over
+ time. The API has changed for the some chips as development progressed
+ and features were added or changed.
+
+ We rely on the boot firmware (which already knows the API version
+ required) to populate Device Tree with the corresponding compatible
+ string.
+
properties:
compatible:
items:
+ - enum:
+ - brcm,dpfe-cpu-v1
+ - brcm,dpfe-cpu-v2
+ - brcm,dpfe-cpu-v3
+ - brcm,dpfe-cpu-v4
- enum:
- brcm,bcm7271-dpfe-cpu
- brcm,bcm7268-dpfe-cpu
@@ -41,7 +60,7 @@ additionalProperties: false
examples:
- |
dpfe-cpu@f1132000 {
- compatible = "brcm,bcm7271-dpfe-cpu";
+ compatible = "brcm,dpfe-cpu-v1", "brcm,bcm7271-dpfe-cpu";
reg = <0xf1132000 0x180>,
<0xf1134000 0x1000>,
<0xf1138000 0x4000>;
--
2.43.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-19 21:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 21:52 [PATCH v2 0/5] memory: brcmstb_dpfe: support DPFE API v4 Markus Mayer
2024-01-19 21:52 ` [PATCH v2 1/5] dt-bindings: memory: remove generic compatible string brcm,dpfe-cpu Markus Mayer
2024-01-23 21:22 ` Krzysztof Kozlowski
2024-02-01 22:01 ` Markus Mayer
2024-01-19 21:52 ` [PATCH v2 2/5] dt-bindings: memory: add two chip-specific compatible string Markus Mayer
2024-01-23 21:23 ` Krzysztof Kozlowski
2024-02-01 22:03 ` Markus Mayer
2024-01-19 21:52 ` Markus Mayer [this message]
2024-01-23 21:27 ` [PATCH v2 3/5] dt-bindings: memory: additional compatible strings for Broadcom DPFE Krzysztof Kozlowski
2024-02-01 22:36 ` Markus Mayer
2024-02-02 7:17 ` Krzysztof Kozlowski
2024-01-19 21:52 ` [PATCH v2 4/5] memory: brcmstb_dpfe: introduce version-specific compatible strings Markus Mayer
2024-01-23 21:27 ` Krzysztof Kozlowski
2024-02-01 22:40 ` Markus Mayer
2024-02-02 7:24 ` Krzysztof Kozlowski
2024-01-19 21:52 ` [PATCH v2 5/5] memory: brcmstb_dpfe: support DPFE API v4 Markus Mayer
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=20240119215231.758844-4-mmayer@broadcom.com \
--to=mmayer@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--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).