From: Conor Dooley <conor@kernel.org>
To: Alexander Sverdlin <alexander.sverdlin@gmail.com>
Cc: soc@lists.linux.dev, Chen Wang <unicorn_wang@outlook.com>,
Inochi Amaoto <inochiama@outlook.com>, Lee Jones <lee@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Sebastian Reichel <sre@kernel.org>,
devicetree@vger.kernel.org, Haylen Chu <heylenay@outlook.com>,
linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org, linux-pm@vger.kernel.org,
Jisheng Zhang <jszhang@kernel.org>,
Chao Wei <chao.wei@sophgo.com>
Subject: Re: [PATCH v2 0/7] arm64 support for Milk-V Duo Module 01 EVB
Date: Tue, 11 Feb 2025 13:48:26 +0000 [thread overview]
Message-ID: <20250211-stubble-senate-0bbb0b04a989@spud> (raw)
In-Reply-To: <b1f05bff1d6c3f0cb1b381c15dcf222ec4c7f1b1.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2349 bytes --]
On Tue, Feb 11, 2025 at 01:43:31PM +0100, Alexander Sverdlin wrote:
> Hi Conor!
>
> On Tue, 2025-02-11 at 10:50 +0000, Conor Dooley wrote:
> > On Mon, Feb 10, 2025 at 11:09:40PM +0100, Alexander Sverdlin wrote:
> > > This series adds very basic support for Milk-V Duo Module 01 EVB [1] in
> > > arm64 mode. The SoC (SG2000) is dual-arch, RiscV and ARM64, the latter has
> > > been chosen because the upstream toolchain can be utilized.
> >
> > > .../{riscv => soc/sophgo}/sophgo.yaml | 7 +-
> > > arch/arm64/Kconfig.platforms | 6 ++
> > > arch/arm64/boot/dts/Makefile | 1 +
> > > arch/arm64/boot/dts/sophgo/Makefile | 2 +
> >
> > I'd expect this to be maintained alongside the riscv support, how come
> > there's no maintainers entry change here?
>
> MAINTAINERS file has "K: sophgo" entry already, I suppose new files will
> fall into this category? That's why I've ignored this specific checkpatch warning
> in all patches. Am I wrong?
Ah, I didn't realise.
>
> > > .../sophgo/sg2000-milkv-duo-module-01-evb.dts | 31 +++++++
> > > .../sophgo/sg2000-milkv-duo-module-01.dtsi | 85 +++++++++++++++++
> > > arch/arm64/boot/dts/sophgo/sg2000.dtsi | 75 +++++++++++++++
> > > arch/arm64/configs/defconfig | 5 +
> > > arch/riscv/boot/dts/sophgo/cv1800b.dtsi | 64 ++++++++++---
> > > arch/riscv/boot/dts/sophgo/cv1812h.dtsi | 64 ++++++++++---
> > > arch/riscv/boot/dts/sophgo/cv181x.dtsi | 2 +-
> > > arch/riscv/boot/dts/sophgo/cv18xx-cpu.dtsi | 57 ++++++++++++
> > > arch/riscv/boot/dts/sophgo/cv18xx.dtsi | 91 +++++--------------
> > > arch/riscv/boot/dts/sophgo/sg2002.dtsi | 64 ++++++++++---
> > > 14 files changed, 451 insertions(+), 103 deletions(-)
> > > rename Documentation/devicetree/bindings/{riscv => soc/sophgo}/sophgo.yaml (80%)
> > > create mode 100644 arch/arm64/boot/dts/sophgo/Makefile
> > > create mode 100644 arch/arm64/boot/dts/sophgo/sg2000-milkv-duo-module-01-evb.dts
> > > create mode 100644 arch/arm64/boot/dts/sophgo/sg2000-milkv-duo-module-01.dtsi
> > > create mode 100644 arch/arm64/boot/dts/sophgo/sg2000.dtsi
> > > create mode 100644 arch/riscv/boot/dts/sophgo/cv18xx-cpu.dtsi
>
> --
> Alexander Sverdlin.
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-02-11 13:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 22:09 [PATCH v2 0/7] arm64 support for Milk-V Duo Module 01 EVB Alexander Sverdlin
2025-02-10 22:09 ` [PATCH v2 1/7] riscv: dts: sophgo: cv18xx: Move RiscV-specific part into SoCs' .dtsi files Alexander Sverdlin
2025-02-12 0:31 ` Inochi Amaoto
2025-02-12 9:26 ` Alexander Sverdlin
2025-02-12 16:46 ` Krzysztof Kozlowski
2025-02-12 17:44 ` Alexander Sverdlin
2025-02-12 19:24 ` Krzysztof Kozlowski
2025-02-12 22:32 ` Inochi Amaoto
2025-02-12 22:31 ` Inochi Amaoto
2025-02-10 22:09 ` [PATCH v2 2/7] dt-bindings: soc: sophgo: Move SoCs/boards from riscv into soc, add SG2000 Alexander Sverdlin
2025-02-11 1:29 ` Chen Wang
2025-02-11 18:18 ` Conor Dooley
2025-02-10 22:09 ` [PATCH v2 3/7] arm64: dts: sophgo: Add initial SG2000 SoC device tree Alexander Sverdlin
2025-02-10 22:09 ` [PATCH v2 4/7] arm64: dts: sophgo: Add Duo Module 01 Alexander Sverdlin
2025-02-10 22:09 ` [PATCH v2 5/7] arm64: dts: sophgo: Add Duo Module 01 Evaluation Board Alexander Sverdlin
2025-02-10 22:09 ` [PATCH v2 6/7] arm64: Add SOPHGO SOC family Kconfig support Alexander Sverdlin
2025-02-11 1:25 ` Chen Wang
2025-02-10 22:09 ` [PATCH v2 7/7] arm64: defconfig: Enable rudimentary Sophgo SG2000 support Alexander Sverdlin
2025-02-11 10:50 ` [PATCH v2 0/7] arm64 support for Milk-V Duo Module 01 EVB Conor Dooley
2025-02-11 12:43 ` Alexander Sverdlin
2025-02-11 13:48 ` Conor Dooley [this message]
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=20250211-stubble-senate-0bbb0b04a989@spud \
--to=conor@kernel.org \
--cc=alexander.sverdlin@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=chao.wei@sophgo.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heylenay@outlook.com \
--cc=inochiama@outlook.com \
--cc=jszhang@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=soc@lists.linux.dev \
--cc=sre@kernel.org \
--cc=unicorn_wang@outlook.com \
--cc=will@kernel.org \
/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