From: Chen-Yu Yeh <chenyou910331@gmail.com>
To: chen.wang@linux.dev, inochiama@gmail.com
Cc: Chen-Yu Yeh <chenyou910331@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Longbin Li <looong.bin@gmail.com>,
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-riscv@lists.infradead.org (open list:RISC-V ARCHITECTURE),
sophgo@lists.linux.dev (open list:SOPHGO DEVICETREES and DRIVERS),
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH 1/2] riscv: dts: sophgo: Enable ethernet for Milk-V Duo 256M
Date: Tue, 4 Aug 2026 00:33:18 +0800 [thread overview]
Message-ID: <20260803163323.74414-1-chenyou910331@gmail.com> (raw)
The SG2002 has an internal ethernet PHY, but on the Milk-V Duo 256M the
ethernet signals are only routed to the RJ45 connector of the optional
IO board.
Enable the GMAC and the MDIO multiplexer so that the interface is usable
when such a board is attached.
Tested on actual Milk-V Duo 256M hardware: the GMAC probes, the MDIO
multiplexer selects the internal bus and the internal EPHY is detected
at address 1:
eth0: PHY [mdio_mux-0.0:01] driver [Generic PHY]
Link-up was not verified for lack of the IO board.
Signed-off-by: Chen-Yu Yeh <chenyou910331@gmail.com>
---
arch/riscv/boot/dts/sophgo/sg2002-milkv-duo256m.dts | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/riscv/boot/dts/sophgo/sg2002-milkv-duo256m.dts b/arch/riscv/boot/dts/sophgo/sg2002-milkv-duo256m.dts
index a2797c0bd767..1462a96a1c12 100644
--- a/arch/riscv/boot/dts/sophgo/sg2002-milkv-duo256m.dts
+++ b/arch/riscv/boot/dts/sophgo/sg2002-milkv-duo256m.dts
@@ -49,6 +49,14 @@ coprocessor_rtos: region@8fe00000 {
};
};
+&gmac0 {
+ status = "okay";
+};
+
+&mdio {
+ status = "okay";
+};
+
&osc {
clock-frequency = <25000000>;
};
base-commit: 11881041b745b444e4f6c87a2748f1951cf02742
--
2.43.0
reply other threads:[~2026-08-03 16:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260803163323.74414-1-chenyou910331@gmail.com \
--to=chenyou910331@gmail.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=chen.wang@linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=looong.bin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=sophgo@lists.linux.dev \
/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