From: Vivian Wang <wangruikang@iscas.ac.cn>
To: Troy Mitchell <troy.mitchell@linux.spacemit.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Yixun Lan <dlan@gentoo.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, Yangyu Chen <cyy@cyyself.name>
Cc: devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/5] riscv: dts: spacemit: add Ethernet support for MusePi Pro
Date: Fri, 10 Oct 2025 14:20:50 +0800 [thread overview]
Message-ID: <f968ca77-6fc0-4485-a13a-2ed83a7e6617@iscas.ac.cn> (raw)
In-Reply-To: <a02aec9a-976a-4b63-86cb-126b8ae71185@iscas.ac.cn>
On 10/10/25 14:13, Vivian Wang wrote:
> On 10/10/25 09:56, Troy Mitchell wrote:
>> MusePi Pro features a single RGMII Ethernet port with
>> PHY reset controlled by GPIO.
>>
>> Signed-off-by: Troy Mitchell <troy.mitchell@linux.spacemit.com>
>> ---
>> arch/riscv/boot/dts/spacemit/k1-musepi-pro.dts | 23 +++++++++++++++++++++++
>> 1 file changed, 23 insertions(+)
>>
>> diff --git a/arch/riscv/boot/dts/spacemit/k1-musepi-pro.dts b/arch/riscv/boot/dts/spacemit/k1-musepi-pro.dts
>> index 89a35914710bfd15c6ad27cd8d0de7ccf62e2309..e9a53dc7a417117c82f3e467677290bdaeffc845 100644
>> --- a/arch/riscv/boot/dts/spacemit/k1-musepi-pro.dts
>> +++ b/arch/riscv/boot/dts/spacemit/k1-musepi-pro.dts
>> @@ -47,6 +47,29 @@ &pdma {
>> status = "okay";
>> };
>>
>> +ð0 {
> For node orders in board DTS for SpacemiT devices, usually we follow
> node name order because there's no unit address to go off of here, so
> for what we have here it should be emmc, eth0, pdma, uart.
>
> See e.g. arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts and previous
> discussion [1].
>
> Also, personally I think it would be fine to just add the whole
> k1-musepi-pro.dts in the same patch instead of splitting it up like
> this. I feel it would be easier to manage this way. For previous devices
> these nodes have been added piecemeal mostly because the drivers were
> being developed in parallel, but if you're going to base this on
> v6.18-rc1 there shouldn't be dependency problems.
... and also almost missed: this should have an ethernet0 alias. In the
most common boot flow it's read by U-Boot to set mac-address so that
both U-Boot and Linux use the same MAC address. This allows U-Boot to a
persistent MAC address rather than having to use a random one.
> Maybe Yixun can chime in about this as well.
>
> Thanks,
> Vivian "dramforever" Wang
>
> [1]: https://lore.kernel.org/linux-riscv/CAH1PCMa35n4dnJ94-EHGrJyU3kztQYO8_v2CkD=rid466zv3+A@mail.gmail.com
>
next prev parent reply other threads:[~2025-10-10 6:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 1:56 [PATCH v2 0/5] riscv: dts: spacemit: add initial support for MusePi Pro Troy Mitchell
2025-10-10 1:56 ` [PATCH v2 1/5] dt-bindings: riscv: spacemit: add MusePi Pro board Troy Mitchell
2025-10-10 14:34 ` Conor Dooley
2025-10-10 1:56 ` [PATCH v2 2/5] riscv: dts: spacemit: add MusePi Pro board device tree Troy Mitchell
2025-10-10 1:56 ` [PATCH v2 3/5] riscv: dts: spacemit: enable PDMA on MusePi Pro Troy Mitchell
2025-10-10 1:56 ` [PATCH v2 4/5] riscv: dts: spacemit: enable eMMC " Troy Mitchell
2025-10-10 1:56 ` [PATCH v2 5/5] riscv: dts: spacemit: add Ethernet support for " Troy Mitchell
2025-10-10 6:13 ` Vivian Wang
2025-10-10 6:20 ` Troy Mitchell
2025-10-10 6:43 ` Yixun Lan
2025-10-10 7:59 ` Troy Mitchell
2025-10-10 22:38 ` Yixun Lan
2025-10-10 14:37 ` Conor Dooley
2025-10-10 6:20 ` Vivian Wang [this message]
2025-10-10 6:23 ` Troy Mitchell
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=f968ca77-6fc0-4485-a13a-2ed83a7e6617@iscas.ac.cn \
--to=wangruikang@iscas.ac.cn \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=cyy@cyyself.name \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=troy.mitchell@linux.spacemit.com \
/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