From: Yixun Lan <dlan@gentoo.org>
To: Troy Mitchell <troy.mitchell@linux.spacemit.com>
Cc: Troy Mitchell <troy.mitchell@linux.dev>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.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>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] riscv: dts: spacemit: Add MusePi Pro board device tree
Date: Sun, 28 Sep 2025 16:50:10 +0800 [thread overview]
Message-ID: <20250928085010-GYC1344940@gentoo.org> (raw)
In-Reply-To: <3074FC8521909735+aNjsSWwkd1aH-moh@kernel.org>
Hi Troy,
On 16:05 Sun 28 Sep , Troy Mitchell wrote:
> On Sun, Sep 28, 2025 at 04:00:03PM +0800, Yixun Lan wrote:
> > Hi Troy,
> >
> > On 12:16 Sun 28 Sep , Troy Mitchell wrote:
> > > From: Troy Mitchell <troy.mitchell@linux.spacemit.com>
> > >
> > > Add initial device tree support for the MusePi Pro board [1].
> > > The board is using the SpacemiT K1/M1 SoC.
> > >
> > > The device tree is adapted from the SpacemiT vendor tree [2].
> > >
> > > This minimal device tree enables booting into a serial console with UART
> > > output and a blinking LED.
> > >
> > > Link:
> > > https://developer.spacemit.com/documentation?token=YJtdwnvvViPVcmkoPDpcvwfVnrh&type=pdf [1]
> > > https://gitee.com/bianbu-linux/linux-6.6/blob/k1-bl-v2.2.y/arch/riscv/boot/dts/spacemit/k1-x_MUSE-Pi-Pro.dts [2]
> > >
> > same as patch 1
> > > Signed-off-by: Troy Mitchell <troy.mitchell@linux.spacemit.com>
> > > ---
..[snip]
> >
> > while you are here, I'd suggest to push as many features as possible
> > instead of this minimal DT, which say - PMU, emmc, ethernet should be ready..
> > (ethernet is in next, should show up at v6.18-rc1)
> Good idea.
> I think I should split these into multiple commits, right?
> Like, PDMA and EMAC should definitely be two separate commits.
>
IMO, not really necessary, but I wouldn't mind either..
--
Yixun Lan (dlan)
next prev parent reply other threads:[~2025-09-28 8:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 3:46 [PATCH 0/2] riscv: dts: spacemit: Add initial support for MusePi Pro Troy Mitchell
2025-09-28 4:16 ` [PATCH 1/2] dt-bindings: riscv: spacemit: Add MusePi Pro board Troy Mitchell
2025-09-28 4:26 ` Troy Mitchell
2025-09-28 4:56 ` E Shattow
2025-09-28 5:10 ` Troy Mitchell
2025-09-28 7:49 ` Yixun Lan
2025-09-28 7:52 ` Troy Mitchell
2025-09-29 17:48 ` Conor Dooley
2025-10-09 8:07 ` Troy Mitchell
2025-10-09 15:27 ` Conor Dooley
2025-10-10 0:56 ` Troy Mitchell
2025-09-28 4:16 ` [PATCH 2/2] riscv: dts: spacemit: Add MusePi Pro board device tree Troy Mitchell
2025-09-28 5:05 ` E Shattow
2025-09-28 5:10 ` Troy Mitchell
2025-09-28 8:00 ` Yixun Lan
2025-09-28 8:05 ` Troy Mitchell
2025-09-28 8:50 ` Yixun Lan [this message]
2025-09-28 9:04 ` 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=20250928085010-GYC1344940@gentoo.org \
--to=dlan@gentoo.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=cyy@cyyself.name \
--cc=devicetree@vger.kernel.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.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