From: Gatien Chevallier <gatien.chevallier@foss.st.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Gatien Chevallier <gatien.chevallier@foss.st.com>
Subject: [PATCH 2/4] arm64: dts: st: enable ethernet1 controller on stm32mp257f-dk
Date: Wed, 3 Sep 2025 11:53:03 +0200 [thread overview]
Message-ID: <20250903-mp2_ethernet-v1-2-4105b0ad2344@foss.st.com> (raw)
In-Reply-To: <20250903-mp2_ethernet-v1-0-4105b0ad2344@foss.st.com>
ethernet1 controller is connected to the RTL8211F-CG Realtek PHY in
RGMII mode. Enable this peripheral on the stm32mp257f-dk board.
Signed-off-by: Gatien Chevallier <gatien.chevallier@foss.st.com>
---
arch/arm64/boot/dts/st/stm32mp257f-dk.dts | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/arch/arm64/boot/dts/st/stm32mp257f-dk.dts b/arch/arm64/boot/dts/st/stm32mp257f-dk.dts
index a278a1e3ce03aa379d40ef807d268bbf31a04546..1f81f717426afa323a2c1359413c1f439b5f4dd0 100644
--- a/arch/arm64/boot/dts/st/stm32mp257f-dk.dts
+++ b/arch/arm64/boot/dts/st/stm32mp257f-dk.dts
@@ -19,6 +19,7 @@ / {
compatible = "st,stm32mp257f-dk", "st,stm32mp257";
aliases {
+ ethernet0 = ðernet1;
serial0 = &usart2;
};
@@ -77,6 +78,29 @@ &arm_wdt {
status = "okay";
};
+ðernet1 {
+ pinctrl-0 = <ð1_rgmii_pins_b>;
+ pinctrl-1 = <ð1_rgmii_sleep_pins_b>;
+ pinctrl-names = "default", "sleep";
+ max-speed = <1000>;
+ phy-handle = <&phy1_eth1>;
+ phy-mode = "rgmii-id";
+ status = "okay";
+
+ mdio {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ compatible = "snps,dwmac-mdio";
+ phy1_eth1: ethernet-phy@1 {
+ compatible = "ethernet-phy-id001c.c916";
+ reg = <1>;
+ reset-gpios = <&gpioa 2 GPIO_ACTIVE_LOW>;
+ reset-assert-us = <10000>;
+ reset-deassert-us = <80000>;
+ };
+ };
+};
+
&scmi_regu {
scmi_vddio1: regulator@0 {
regulator-min-microvolt = <1800000>;
--
2.25.1
next prev parent reply other threads:[~2025-09-03 9:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 9:53 [PATCH 0/4] arm64: dts: st: add ethernet1 controller support on stm32mp23/25 boards Gatien Chevallier
2025-09-03 9:53 ` [PATCH 1/4] arm64: dts: st: add eth1 pins for stm32mp2x platforms Gatien Chevallier
2025-09-03 9:53 ` Gatien Chevallier [this message]
2025-09-03 12:21 ` [PATCH 2/4] arm64: dts: st: enable ethernet1 controller on stm32mp257f-dk Andrew Lunn
2025-09-03 13:35 ` Gatien CHEVALLIER
2025-09-03 9:53 ` [PATCH 3/4] arm64: dts: st: enable ethernet1 controller on stm32mp257f-ev1 Gatien Chevallier
2025-09-03 12:24 ` Andrew Lunn
2025-09-03 12:46 ` Gatien CHEVALLIER
2025-09-03 9:53 ` [PATCH 4/4] arm64: dts: st: enable ethernet1 controller on stm32mp235f-dk Gatien Chevallier
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=20250903-mp2_ethernet-v1-2-4105b0ad2344@foss.st.com \
--to=gatien.chevallier@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.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;
as well as URLs for NNTP newsgroup(s).