From: Troy Mitchell <troy.mitchell@linux.spacemit.com>
To: Yixun Lan <dlan@gentoo.org>,
Troy Mitchell <troy.mitchell@linux.spacemit.com>
Cc: 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 v3 2/2] riscv: dts: spacemit: add MusePi Pro board device tree
Date: Mon, 20 Oct 2025 10:02:04 +0800 [thread overview]
Message-ID: <52A7E982E5B11F53+aPWYHMbImTxJy7pJ@kernel.org> (raw)
In-Reply-To: <20251020015204-GYF1506524@gentoo.org>
Hi Yixun, thanks for your review.
On Mon, Oct 20, 2025 at 09:52:04AM +0800, Yixun Lan wrote:
> Hi Troy,
>
> On 13:52 Fri 17 Oct , Troy Mitchell wrote:
> > 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].
> >
> > Here's a refined list of its core features for consideration:
> > - SoC: SpacemiT M1/K1, 8-core 64-bit RISC-V with 2.0 TOPS AI power.
> > This suggests potential for light AI/ML workloads on-device.
> > - Memory: LPDDR4X @ 2400MT/s, available in 8GB & 16GB options.
> > Sufficient for various workloads.
> > - Storage: Onboard eMMC 5.1 (64GB/128GB options). M.2 M-Key for NVMe
> > SSD (2230 size), and a microSD slot (UHS-II) for expansion.
> > Good variety for boot and data.
> > - Display: HDMI 1.4 (1080P@60Hz) and 2-lane MIPI DSI FPC (1080P@60Hz).
> > Standard display options.
> > - Connectivity: Onboard Wi-Fi 6 & Bluetooth 5.2. A single Gigabit
> > Ethernet port (RJ45). Given the stated markets,
> > this should cover basic networking.
> > - USB: 4x USB 3.0 Type-A (host) and 1x USB 2.0 Type-C (device/OTG).
> > Decent host capabilities.
> > - Expansion: Full-size miniPCIe slot for assorted modules
> > (4G/5G, wireless etc.). A second M.2 M-Key (2230) for more
> > general PCIe devices (SSD, PCIe-to-SATA, comm boards).
> > - GPIO: Standard 40-pin GPIO interface, as expected for an SBC.
> > - MIPI: Includes 1x 4-lane MIPI CSI FPC and 2x MIPI DSI FPC interfaces
> > for cameras and displays.
> > - Clock: Onboard RTC with battery support.
> I think you've already gave an overall description for MusePi board in
> patch [1/2] which is sufficient, in this patch you could better focus on
> what it actually done here? enabling mmc, ethernet, led, pdma, uart..
Yes, I'll remove these.
>
> >
> > 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]
> > Link: 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]
> >
> ditto
> > Signed-off-by: Troy Mitchell <troy.mitchell@linux.spacemit.com>
[...]
> > +++ b/arch/riscv/boot/dts/spacemit/k1-musepi-pro.dts
> > @@ -0,0 +1,78 @@
> > +// SPDX-License-Identifier: (GPL-2.0 OR MIT)
> > +/*
> > + * Copyright (C) 2024 Yangyu Chen <cyy@cyyself.name>
> ..
> > + * Copyright (C) 2025 Troy Mitchell <troy.mitchell@linux.spacemit.com>
> this isn't a big problem, but I think it would be better to use SpacemiT
> Corp's Copyright, to reflect you're not doing as individual contributor..
I understand. Since I originally wrote and now maintain this DTS,
would it still be acceptable to include my own copyright line along with SpacemiT’s?
Or company-only?
- Troy
next prev parent reply other threads:[~2025-10-20 2:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 5:52 [PATCH v3 0/2] riscv: dts: spacemit: add initial support for MusePi Pro Troy Mitchell
2025-10-17 5:52 ` [PATCH v3 1/2] dt-bindings: riscv: spacemit: add MusePi Pro board Troy Mitchell
2025-10-20 1:41 ` Yixun Lan
2025-10-20 1:54 ` Troy Mitchell
2025-10-17 5:52 ` [PATCH v3 2/2] riscv: dts: spacemit: add MusePi Pro board device tree Troy Mitchell
2025-10-20 1:52 ` Yixun Lan
2025-10-20 2:02 ` Troy Mitchell [this message]
2025-10-20 2:18 ` Yixun Lan
2025-10-20 2:20 ` 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=52A7E982E5B11F53+aPWYHMbImTxJy7pJ@kernel.org \
--to=troy.mitchell@linux.spacemit.com \
--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 \
/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
all inboxes | Powered by JetHome®