From: Alexander Sverdlin <alexander.sverdlin@gmail.com>
To: Inochi Amaoto <inochiama@gmail.com>,
sophgo@lists.linux.dev, soc@lists.linux.dev
Cc: Chen Wang <unicorn_wang@outlook.com>,
Jisheng Zhang <jszhang@kernel.org>,
Haylen Chu <heylenay@outlook.com>,
Chao Wei <chao.wei@sophgo.com>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 1/7] riscv: dts: sophgo: cv18xx: Move RiscV-specific part into SoCs' .dtsi files
Date: Tue, 29 Apr 2025 21:10:57 +0200 [thread overview]
Message-ID: <70bc994b1e79c8d0d4c0010611c2e65042cff74f.camel@gmail.com> (raw)
In-Reply-To: <6wlgfvc3rkhv4s3ou67fjl6j4a26vocqck5727cg6muxlz2erj@kivndcjcqc7m>
Hi Inochi,
On Tue, 2025-04-29 at 06:35 +0800, Inochi Amaoto wrote:
> > Make the peripheral device tree re-usable on ARM64 platform by moving CPU
> > core and interrupt controllers' parts into new cv18xx-cpu.dtsi and
> > cv18xx-intc.dtsi.
> >
> > Add SOC_PERIPHERAL_IRQ() macro which explicitly maps peripheral nubering
> > into "plic" interrupt-controller numbering.
> >
> > Signed-off-by: Alexander Sverdlin <alexander.sverdlin@gmail.com>
> > ---
> > Changelog:
> > v5:
> > v4:
> > - cleanups dropped
> > - cv18xx-cpu-intc.dtsi instead of cv18xx-cpu.dtsi+cv18xx-intc.dtsi
> > v3:
> > - &cpus node has been moved into cv18xx-cpu.dtsi, &plic and &clint nodes
> > were moved into cv18xx-intc.dtsi to reduce code duplication;
> > v2:
> > - instead of carving out peripherals' part, carve out ARCH-specifics (CPU
> > core, interrupt controllers) and spread them among 3 SoC .dtsi files which
> > included cv18xx.dtsi;
> > - define a label for the "soc" node and use it in the newly introduced DTs;
> >
> > arch/riscv/boot/dts/sophgo/cv1800b.dtsi | 5 +
> > arch/riscv/boot/dts/sophgo/cv1812h.dtsi | 5 +
> > arch/riscv/boot/dts/sophgo/cv181x.dtsi | 2 +-
> > .../boot/dts/sophgo/cv18xx-cpu-intc.dtsi | 54 +++++++++++
> > arch/riscv/boot/dts/sophgo/cv18xx.dtsi | 91 +++++--------------
> > arch/riscv/boot/dts/sophgo/sg2002.dtsi | 5 +
> > 6 files changed, 93 insertions(+), 69 deletions(-)
> > create mode 100644 arch/riscv/boot/dts/sophgo/cv18xx-cpu-intc.dtsi
> >
>
> It is a hard time for now to do some change across the cv18xx
> series, and it has become a mess. Due to the fact, I think it
> is time to do some work like split some device (clk, pinctrl,
> plic, intc) from cv18xx.dtsi to avoid override, and make room
> for arm64 device.
>
> Since this change contains some change similar to this patch.
> Would you mind me to take content of this patch, and add you
> as the a co-author?
thanks for looking into this!
Either way is good for me!
--
Alexander Sverdlin.
next prev parent reply other threads:[~2025-04-29 19:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-16 18:56 [PATCH v5 0/7] arm64 support for Milk-V Duo Module 01 EVB Alexander Sverdlin
2025-03-16 18:56 ` [PATCH v5 1/7] riscv: dts: sophgo: cv18xx: Move RiscV-specific part into SoCs' .dtsi files Alexander Sverdlin
2025-04-28 22:35 ` Inochi Amaoto
2025-04-29 19:10 ` Alexander Sverdlin [this message]
2025-03-16 18:56 ` [PATCH v5 2/7] dt-bindings: soc: sophgo: Move SoCs/boards from riscv into soc, add SG2000 Alexander Sverdlin
2025-03-16 18:56 ` [PATCH v5 3/7] arm64: dts: sophgo: Add initial SG2000 SoC device tree Alexander Sverdlin
2025-03-16 18:56 ` [PATCH v5 4/7] arm64: dts: sophgo: Add Duo Module 01 Alexander Sverdlin
2025-03-16 18:56 ` [PATCH v5 5/7] arm64: dts: sophgo: Add Duo Module 01 Evaluation Board Alexander Sverdlin
2025-03-16 18:56 ` [PATCH v5 6/7] arm64: Add SOPHGO SOC family Kconfig support Alexander Sverdlin
2025-03-16 18:56 ` [PATCH v5 7/7] arm64: defconfig: Enable rudimentary Sophgo SG2000 support Alexander Sverdlin
2025-03-17 14:18 ` [PATCH v5 0/7] arm64 support for Milk-V Duo Module 01 EVB Rob Herring (Arm)
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=70bc994b1e79c8d0d4c0010611c2e65042cff74f.camel@gmail.com \
--to=alexander.sverdlin@gmail.com \
--cc=chao.wei@sophgo.com \
--cc=devicetree@vger.kernel.org \
--cc=heylenay@outlook.com \
--cc=inochiama@gmail.com \
--cc=jszhang@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=soc@lists.linux.dev \
--cc=sophgo@lists.linux.dev \
--cc=unicorn_wang@outlook.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