From: Marek Vasut <marex@nabladev.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Marek Vasut <marex@nabladev.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Bartosz Golaszewski <brgl@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Linus Walleij <linusw@kernel.org>, Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, kernel@dh-electronics.com,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: [PATCH 3/5] arm64: dts: st: Reuse sdmmc1_*_pins_a pinmux
Date: Tue, 29 Sep 2026 21:39:57 +0200 [thread overview]
Message-ID: <20260929194035.496244-3-marex@nabladev.com> (raw)
In-Reply-To: <20260929194035.496244-1-marex@nabladev.com>
It is perfectly possible to use sdmmc1_*_pins_a on the DH electronics
STM32MP23xx/STM32MP25xx DHCOS SoM, the only difference is the slew rate.
Reuse sdmmc1_*_pins_a with updated slew rate on board level.
Fixes: 9b584c92f94f ("arm64: dts: st: Add support for DH electronics STM32MP23xx/STM32MP25xx DHCOS SoM and Breakout Board and DHSBC")
Signed-off-by: Marek Vasut <marex@nabladev.com>
---
Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: Bartosz Golaszewski <brgl@kernel.org>
Cc: Conor Dooley <conor+dt@kernel.org>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: Linus Walleij <linusw@kernel.org>
Cc: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org
Cc: kernel@dh-electronics.com
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-gpio@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: linux-stm32@st-md-mailman.stormreply.com
---
.../boot/dts/st/stm32mp255c-dhcos-dhsbc.dts | 28 +++++++++++++++++--
1 file changed, 26 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/st/stm32mp255c-dhcos-dhsbc.dts b/arch/arm64/boot/dts/st/stm32mp255c-dhcos-dhsbc.dts
index 332a8034cc372..eea7a76953639 100644
--- a/arch/arm64/boot/dts/st/stm32mp255c-dhcos-dhsbc.dts
+++ b/arch/arm64/boot/dts/st/stm32mp255c-dhcos-dhsbc.dts
@@ -145,10 +145,34 @@ &scmi_vddio1 {
regulator-settling-time-down-us = <100000>;
};
+&sdmmc1_b4_pins_a {
+ pins1 {
+ slew-rate = <1>;
+ };
+
+ pins2 {
+ slew-rate = <2>;
+ };
+};
+
+&sdmmc1_b4_od_pins_a {
+ pins1 {
+ slew-rate = <1>;
+ };
+
+ pins2 {
+ slew-rate = <2>;
+ };
+
+ pins3 {
+ slew-rate = <1>;
+ };
+};
+
&sdmmc1 {
pinctrl-names = "default", "opendrain", "sleep";
- pinctrl-0 = <&sdmmc1_b4_pins_b>;
- pinctrl-1 = <&sdmmc1_b4_od_pins_b>;
+ pinctrl-0 = <&sdmmc1_b4_pins_a>;
+ pinctrl-1 = <&sdmmc1_b4_od_pins_a>;
pinctrl-2 = <&sdmmc1_b4_sleep_pins_a>;
cd-gpios = <&ioexp 8 GPIO_ACTIVE_HIGH>;
disable-wp;
--
2.53.0
next prev parent reply other threads:[~2026-09-29 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 19:39 [PATCH 1/5] arm64: dts: st: Add st,io-sync into eth2_rgmii_pins_b Marek Vasut
2026-09-29 19:39 ` [PATCH 2/5] arm64: dts: st: Fix PF7 AF10 comment Marek Vasut
2026-09-29 19:39 ` Marek Vasut [this message]
2026-09-29 19:39 ` [PATCH 4/5] arm64: dts: st: Drop sdmmc1_*_pins_b pinmux Marek Vasut
2026-09-29 19:39 ` [PATCH 5/5] arm64: dts: st: Do not encode path in sdmmc2_*_pins_a/pins2 phandle Marek Vasut
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=20260929194035.496244-3-marex@nabladev.com \
--to=marex@nabladev.com \
--cc=alexandre.torgue@foss.st.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@dh-electronics.com \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=robh@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®