From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Marek Vasut <marex@nabladev.com>, <linux-arm-kernel@lists.infradead.org>
Cc: 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: Re: [PATCH 06/10] arm64: dts: st: Add SDMMC2 and SDMMC3 nodes on stm32mp251
Date: Mon, 28 Sep 2026 11:04:44 +0200 [thread overview]
Message-ID: <7d8ee07c-14a5-429d-8c97-6c4ded486f12@foss.st.com> (raw)
In-Reply-To: <20260711210131.236025-7-marex@nabladev.com>
Hi Marek
On 7/11/26 22:59, Marek Vasut wrote:
> Add DT nodes for the remaining SDMMC controllers 2 and 3.
>
> 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
> ---
> arch/arm64/boot/dts/st/stm32mp251.dtsi | 30 ++++++++++++++++++++++++++
> 1 file changed, 30 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/st/stm32mp251.dtsi b/arch/arm64/boot/dts/st/stm32mp251.dtsi
> index 66f3f83b8731f..6e985f115b195 100644
> --- a/arch/arm64/boot/dts/st/stm32mp251.dtsi
> +++ b/arch/arm64/boot/dts/st/stm32mp251.dtsi
> @@ -1667,6 +1667,36 @@ sdmmc1: mmc@48220000 {
> status = "disabled";
> };
>
> + sdmmc2: mmc@48230000 {
> + compatible = "st,stm32mp25-sdmmc2", "arm,pl18x", "arm,primecell";
> + arm,primecell-periphid = <0x00353180>;
> + reg = <0x48230000 0x400>, <0x44230800 0x8>;
> + interrupts = <GIC_SPI 197 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&rcc CK_KER_SDMMC2>;
> + clock-names = "apb_pclk";
> + resets = <&rcc SDMMC2_R>;
> + cap-sd-highspeed;
> + cap-mmc-highspeed;
> + max-frequency = <166000000>;
I merged some weeks ago a patch introducing SDMCC2. max-freq is 120000000. I'll keep this patch adding SDMMC3, and increasing SDMMC2 max freq.
> + access-controllers = <&rifsc 77>;
> + status = "disabled";
> + };
> +
> + sdmmc3: mmc@48240000 {
> + compatible = "st,stm32mp25-sdmmc2", "arm,pl18x", "arm,primecell";
> + arm,primecell-periphid = <0x00353180>;
> + reg = <0x48240000 0x400>, <0x44230c00 0x8>;
> + interrupts = <GIC_SPI 214 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&rcc CK_KER_SDMMC3>;
> + clock-names = "apb_pclk";
> + resets = <&rcc SDMMC3_R>;
> + cap-sd-highspeed;
> + cap-mmc-highspeed;
> + max-frequency = <166000000>;
> + access-controllers = <&rifsc 78>;
> + status = "disabled";
> + };
> +
> ethernet1: ethernet@482c0000 {
> compatible = "st,stm32mp25-dwmac", "snps,dwmac-5.20";
> reg = <0x482c0000 0x4000>;
next prev parent reply other threads:[~2026-09-28 9:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 20:59 [PATCH 00/10] arm64: dts: st: Add support for DH electronics STM32MP23xx/STM32MP25xx DHCOS SoM and Breakout Board and DHSBC Marek Vasut
2026-07-11 20:59 ` [PATCH 01/10] dt-bindings: arm: stm32: Document " Marek Vasut
2026-07-13 7:48 ` Krzysztof Kozlowski
2026-07-13 10:31 ` Marek Vasut
2026-07-11 20:59 ` [PATCH 02/10] dt-bindings: gpio: pca95xx: Document Kinetic KTS1622 Marek Vasut
2026-07-13 7:49 ` Krzysztof Kozlowski
2026-07-13 8:36 ` Bartosz Golaszewski
2026-07-13 10:33 ` Marek Vasut
2026-07-15 8:18 ` Bartosz Golaszewski
2026-07-11 20:59 ` [PATCH 03/10] arm64: dts: st: Fix SDMMC1 indent on stm32mp231 Marek Vasut
2026-07-11 20:59 ` [PATCH 04/10] arm64: dts: st: Fix SDMMC1 indent on stm32mp251 Marek Vasut
2026-07-11 20:59 ` [PATCH 05/10] arm64: dts: st: Add SDMMC2 and SDMMC3 nodes on stm32mp231 Marek Vasut
2026-07-11 20:59 ` [PATCH 06/10] arm64: dts: st: Add SDMMC2 and SDMMC3 nodes on stm32mp251 Marek Vasut
2026-09-28 9:04 ` Alexandre TORGUE [this message]
2026-07-11 20:59 ` [PATCH 07/10] arm64: dts: st: Add OMM node on stm32mp231 Marek Vasut
2026-07-11 20:59 ` [PATCH 08/10] arm64: dts: st: Add pinmux nodes for DH electronics STM32MP23xx/STM32MP25xx DHCOS SoM and Breakout Board Marek Vasut
2026-09-28 9:02 ` Alexandre TORGUE
2026-09-28 14:12 ` Marek Vasut
2026-07-11 20:59 ` [PATCH 09/10] arm64: dts: st: Add support for DH electronics STM32MP23xx/STM32MP25xx DHCOS SoM and Breakout Board and DHSBC Marek Vasut
2026-07-11 20:59 ` [PATCH 10/10] MAINTAINERS: Add DH electronics DHCOS SoM entry and fix email address Marek Vasut
2026-07-13 7:51 ` Krzysztof Kozlowski
2026-07-13 13:25 ` Marek Vasut
2026-07-13 13:45 ` Krzysztof Kozlowski
2026-08-25 17:56 ` [PATCH 00/10] arm64: dts: st: Add support for DH electronics STM32MP23xx/STM32MP25xx DHCOS SoM and Breakout Board and DHSBC Marek Vasut
2026-09-08 19:43 ` Marek Vasut
2026-09-28 12:30 ` Alexandre TORGUE
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=7d8ee07c-14a5-429d-8c97-6c4ded486f12@foss.st.com \
--to=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=marex@nabladev.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®