[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2e3f213b-d507-4290-91af-fba7492155d2@lunn.ch>
Date: Tue, 20 Jan 2026 23:10:55 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Joey Lu <a0987203069@...il.com>
Cc: andrew+netdev@...n.ch, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, robh@...nel.org,
krzk+dt@...nel.org, conor+dt@...nel.org, mcoquelin.stm32@...il.com,
richardcochran@...il.com, alexandre.torgue@...s.st.com,
joabreu@...opsys.com, ychuang3@...oton.com, schung@...oton.com,
yclu4@...oton.com, peppe.cavallaro@...com,
linux-arm-kernel@...ts.infradead.org, netdev@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
openbmc@...ts.ozlabs.org, linux-stm32@...md-mailman.stormreply.com
Subject: Re: [PATCH net-next v8 2/3] arm64: dts: nuvoton: Add Ethernet nodes
On Tue, Jan 20, 2026 at 09:34:39AM +0800, Joey Lu wrote:
> Dear Andrew,
Please don't top post.
>
> Thanks for the clarification.
>
> In our design, the Ethernet PHYs are located on the base boards, not on the
> MA35D1 SOM.
>
> The SOM base board routes two RGMII interfaces from the SOM to two external
> PHYs on the carrier board.
>
> On the MA35D1 IoT board, there is no separate SOM and carrier board - it is
> a single integrated board.
>
> I will update the DTS accordingly so that no PHY nodes appear in .dtsi.
>
> Thanks!
>
> Best regards,
>
> Joey
>
> Andrew Lunn 於 1/19/2026 11:22 PM 寫道:
> > On Mon, Jan 19, 2026 at 03:33:40PM +0800, Joey Lu wrote:
> > > Add GMAC nodes for our MA35D1 development boards:
> > > two RGMII interfaces for SOM board, and one RGMII
> > > and one RMII interface for IoT board.
> > >
> > > Signed-off-by: Joey Lu <a0987203069@...il.com>
> > > ---
> > > .../boot/dts/nuvoton/ma35d1-iot-512m.dts | 12 +++++
> > > .../boot/dts/nuvoton/ma35d1-som-256m.dts | 10 ++++
> > > arch/arm64/boot/dts/nuvoton/ma35d1.dtsi | 54 +++++++++++++++++++
Does ma35d1.dtsi represent the SOM?
If so, what is ma35d1-som-256m.dts ? It looks like some odd sort of
carrier board with a few serial ports and some memory? But systems
like this put the memory on the SOM, not the carrier.
As i said, i'm confused with your naming here.
Andrew
Powered by blists - more mailing lists