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 4/5] memory: brcmstb_dpfe: introduce version-specific compatible strings
Date: Fri, 19 Jan 2024 13:52:27 -0800 [thread overview]
Message-ID: <20240119215231.758844-5-mmayer@broadcom.com> (raw)
In-Reply-To: <20240119215231.758844-1-mmayer@broadcom.com>
Introduce compatible strings brcm,dpfe-cpu-v1 through brcm,dpfe-cpu-v3
to the Broadcom DPFE driver.
Signed-off-by: Markus Mayer <mmayer@broadcom.com>
---
drivers/memory/brcmstb_dpfe.c | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/drivers/memory/brcmstb_dpfe.c b/drivers/memory/brcmstb_dpfe.c
index a7ab3d377206..a44a70d028f6 100644
--- a/drivers/memory/brcmstb_dpfe.c
+++ b/drivers/memory/brcmstb_dpfe.c
@@ -924,7 +924,20 @@ static const struct of_device_id brcmstb_dpfe_of_match[] = {
{ .compatible = "brcm,bcm7271-dpfe-cpu", .data = &dpfe_api_old_v2 },
{ .compatible = "brcm,bcm7278-dpfe-cpu", .data = &dpfe_api_old_v2 },
{ .compatible = "brcm,bcm7211-dpfe-cpu", .data = &dpfe_api_new_v2 },
- /* API v3 is the default going forward */
+
+ /*
+ * Match the DPFE API flavour based on a versioned compatible string
+ * that tells us which API version the hardware speaks.
+ */
+ { .compatible = "brcm,dpfe-cpu-v1", .data = &dpfe_api_old_v2 },
+ { .compatible = "brcm,dpfe-cpu-v2", .data = &dpfe_api_new_v2 },
+ { .compatible = "brcm,dpfe-cpu-v3", .data = &dpfe_api_v3 },
+
+ /*
+ * This "default" compatible string should no longer be used. It has
+ * been removed from the binding but kept here for backward
+ * compatibility.
+ */
{ .compatible = "brcm,dpfe-cpu", .data = &dpfe_api_v3 },
{}
};
--
2.43.0
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 ` [PATCH v2 3/5] dt-bindings: memory: additional compatible strings for Broadcom DPFE Markus Mayer
2024-01-23 21:27 ` Krzysztof Kozlowski
2024-02-01 22:36 ` Markus Mayer
2024-02-02 7:17 ` Krzysztof Kozlowski
2024-01-19 21:52 ` Markus Mayer [this message]
2024-01-23 21:27 ` [PATCH v2 4/5] memory: brcmstb_dpfe: introduce version-specific compatible strings 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-5-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).