From: Dario Binacchi <dario.binacchi@amarulasolutions•com>
To: linux-kernel@vger•kernel.org
Cc: linux-amarula@amarulasolutions•com, michael@amarulasolutions•com,
Dario Binacchi <dario.binacchi@amarulasolutions•com>,
Alexandre Torgue <alexandre.torgue@foss•st.com>,
Conor Dooley <conor+dt@kernel•org>,
Krzysztof Kozlowski <krzk+dt@kernel•org>,
Maxime Coquelin <mcoquelin.stm32@gmail•com>,
Rob Herring <robh@kernel•org>,
devicetree@vger•kernel.org, linux-arm-kernel@lists•infradead.org,
linux-stm32@st-md-mailman•stormreply.com
Subject: [PATCH v2 2/2] arm64: dts: st: add power-domains to sdmmc1 on stm32mp231
Date: Sat, 30 May 2026 15:56:55 +0200 [thread overview]
Message-ID: <20260530135701.3961023-2-dario.binacchi@amarulasolutions.com> (raw)
In-Reply-To: <20260530135701.3961023-1-dario.binacchi@amarulasolutions.com>
The sdmmc1 node was introduced early in the SoC bring-up before power
domains were systematically mapped. Add the missing power-domains
property to align it with the rest of the peripheral nodes.
Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions•com>
---
Changes in v2:
- Add patch. Suggested by Sashiko
arch/arm64/boot/dts/st/stm32mp231.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/st/stm32mp231.dtsi b/arch/arm64/boot/dts/st/stm32mp231.dtsi
index 9e1d240888ff..0feb8943efae 100644
--- a/arch/arm64/boot/dts/st/stm32mp231.dtsi
+++ b/arch/arm64/boot/dts/st/stm32mp231.dtsi
@@ -727,6 +727,7 @@ sdmmc1: mmc@48220000 {
cap-mmc-highspeed;
max-frequency = <120000000>;
access-controllers = <&rifsc 76>;
+ power-domains = <&cluster_pd>;
status = "disabled";
};
--
2.43.0
base-commit: f5e5d3509bffb95c6648eb9795f7f236852ae62d
branch: stm32mp251-sdmmc1-power-domains
prev parent reply other threads:[~2026-05-30 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 13:56 [PATCH v2 1/2] arm64: dts: st: add power-domains to sdmmc1 on stm32mp251 Dario Binacchi
2026-05-30 13:56 ` Dario Binacchi [this message]
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=20260530135701.3961023-2-dario.binacchi@amarulasolutions.com \
--to=dario.binacchi@amarulasolutions$(echo .)com \
--cc=alexandre.torgue@foss$(echo .)st.com \
--cc=conor+dt@kernel$(echo .)org \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=krzk+dt@kernel$(echo .)org \
--cc=linux-amarula@amarulasolutions$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-stm32@st-md-mailman$(echo .)stormreply.com \
--cc=mcoquelin.stm32@gmail$(echo .)com \
--cc=michael@amarulasolutions$(echo .)com \
--cc=robh@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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