From: Christophe Kerello <christophe.kerello@foss.st.com>
To: <krzysztof.kozlowski@linaro.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<devicetree@vger.kernel.org>,
Christophe Kerello <christophe.kerello@foss.st.com>
Subject: [PATCH v2 1/5] dt-bindings: memory-controller: st,stm32: add MP25 support
Date: Mon, 19 Feb 2024 15:01:58 +0100 [thread overview]
Message-ID: <20240219140202.85680-2-christophe.kerello@foss.st.com> (raw)
In-Reply-To: <20240219140202.85680-1-christophe.kerello@foss.st.com>
Add a new compatible string to support MP25 SoC.
On MP1 SoC, RNB signal (NAND controller signal) and NWAIT signal (PSRAM
controller signal) have been integrated together in the SoC. That means
that the NAND controller and the PSRAM controller (if the signal is
used) can not be used at the same time. On MP25 SoC, the 2 signals can
be used outside the SoC, so there is no more restrictions.
MP1 SoC also embeds revision 1.1 of the FMC2 IP when MP25 SoC embeds
revision 2.0 of the FMC2 IP.
MP25 SoC is also using PSCI OS-initiated mode, so allow a single
'power-domains' entry for STM32 FMC2. As MP1 will move on PSCI
OS-initiated mode, add this property as optional for all FMC2 variants.
Signed-off-by: Christophe Kerello <christophe.kerello@foss.st.com>
---
Changes in v2:
- V1 patch 1 and 2 have been squashed and commit message has been updated.
.../bindings/memory-controllers/st,stm32-fmc2-ebi.yaml | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/memory-controllers/st,stm32-fmc2-ebi.yaml b/Documentation/devicetree/bindings/memory-controllers/st,stm32-fmc2-ebi.yaml
index 14f1833d37c9..84ac6f50a6fc 100644
--- a/Documentation/devicetree/bindings/memory-controllers/st,stm32-fmc2-ebi.yaml
+++ b/Documentation/devicetree/bindings/memory-controllers/st,stm32-fmc2-ebi.yaml
@@ -23,7 +23,9 @@ maintainers:
properties:
compatible:
- const: st,stm32mp1-fmc2-ebi
+ enum:
+ - st,stm32mp1-fmc2-ebi
+ - st,stm32mp25-fmc2-ebi
reg:
maxItems: 1
@@ -34,6 +36,9 @@ properties:
resets:
maxItems: 1
+ power-domains:
+ maxItems: 1
+
"#address-cells":
const: 2
--
2.25.1
next prev parent reply other threads:[~2024-02-19 14:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 14:01 [PATCH v2 0/5] memory: stm32-fmc2-ebi: Add MP25 FMC2 support Christophe Kerello
2024-02-19 14:01 ` Christophe Kerello [this message]
2024-02-20 9:56 ` [PATCH v2 1/5] dt-bindings: memory-controller: st,stm32: add MP25 support Krzysztof Kozlowski
2024-02-21 8:27 ` Krzysztof Kozlowski
2024-02-19 14:01 ` [PATCH v2 2/5] memory: stm32-fmc2-ebi: check regmap_read return value Christophe Kerello
2024-02-21 8:29 ` Krzysztof Kozlowski
2024-02-26 8:25 ` Christophe Kerello
2024-02-19 14:02 ` [PATCH v2 3/5] memory: stm32-fmc2-ebi: add MP25 support Christophe Kerello
2024-02-21 8:32 ` Krzysztof Kozlowski
2024-02-26 8:26 ` Christophe Kerello
2024-02-19 14:02 ` [PATCH v2 4/5] memory: stm32-fmc2-ebi: add MP25 RIF support Christophe Kerello
2024-02-19 14:02 ` [PATCH v2 5/5] memory: stm32-fmc2-ebi: keep power domain on Christophe Kerello
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=20240219140202.85680-2-christophe.kerello@foss.st.com \
--to=christophe.kerello@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.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
all inboxes | Powered by JetHome®