From: Chen Wang <chen.wang@linux.dev>
To: "sophgo@lists.linux.dev" <sophgo@lists.linux.dev>
Subject: Fwd: [GIT PULL] RISC-V Sophgo Devicetrees for v7.3
Date: Wed, 5 Aug 2026 09:03:28 +0800 [thread overview]
Message-ID: <9daba6e5-fa82-4ed9-b9f2-078dacec46f0@linux.dev> (raw)
In-Reply-To: <1333a916-da71-432d-99ae-69cdb6061add@linux.dev>
I'm forwarding this because I noticed the previous email was rejected by
the mailing list—I'm not sure why.
-------- Forwarded Message --------
Subject: [GIT PULL] RISC-V Sophgo Devicetrees for v7.3
Date: Wed, 5 Aug 2026 08:52:02 +0800
From: Chen Wang <chen.wang@linux.dev>
To: soc@kernel.org, Arnd Bergmann <arnd@arndb.de>
CC: Conor Dooley <conor+dt@kernel.org>, Inochi Amaoto
<inochiama@gmail.com>, sophgo@lists.linux.dev <sophgo@lists.linux.dev>,
linux-riscv <linux-riscv@lists.infradead.org>, Chen Wang
<chen.wang@linux.dev>, Joshua Milas <josh.milas@gmail.com>, Chen-Yu Yeh
<chenyou910331@gmail.com>
Hey Arnd,
Please pull this dt changes for RISC-V/Sophgo.
Thanks,
Chen
The following changes since commit dc59e4fea9d83f03bad6bddf3fa2e52491777482:
Linux 7.2-rc1 (2026-06-28 12:01:31 -0700)
are available in the Git repository at:
https://github.com/sophgo/linux.git tags/riscv-sophgo-dt-for-v7.3
for you to fetch changes up to 59c682ffc76ebda27ecbbbd1423e23ec482d61b9:
riscv: dts: sophgo: Add Milk-V Duo 256M board support (2026-08-04
18:04:32 +0800)
----------------------------------------------------------------
RISC-V Devicetrees for v7.3
Sophgo:
The changes of this PR are all for CV18xx serials.
There are three major changes. The first is to allow
DMA multiplexer setting channel number for DMA controller;
the second is to add initial RISC-V support for "Duo S"
board, which uses SG2000, a dual-arch SoC (RISC-V and
ARM64); the third is to add support for "Duo 256M"
board, another dev-board based on SG2002 SoC.
Signed-off-by: Chen Wang <chen.wang@linux.dev>
----------------------------------------------------------------
Chen-Yu Yeh (3):
dt-bindings: soc: sophgo: add Milk-V Duo 256M board
riscv: dts: sophgo: cv180x: Add PWR_GPIO controller
riscv: dts: sophgo: Add Milk-V Duo 256M board support
Inochi Amaoto (1):
riscv: dts: sophgo: cv180x: Allow the DMA multiplexer to set
channel number for DMA controller
Joshua Milas (2):
riscv64: dts: sophgo: add SG2000 dtsi
riscv64: dts: sophgo: add initial Milk-V Duo S board support
.../devicetree/bindings/soc/sophgo/sophgo.yaml | 4 +
arch/riscv/boot/dts/sophgo/Makefile | 2 +
arch/riscv/boot/dts/sophgo/cv180x.dtsi | 20 +-
arch/riscv/boot/dts/sophgo/sg2000-milkv-duo-s.dts | 244
+++++++++++++++++++++
arch/riscv/boot/dts/sophgo/sg2000.dtsi | 53 +++++
.../riscv/boot/dts/sophgo/sg2002-milkv-duo256m.dts | 121 ++++++++++
6 files changed, 443 insertions(+), 1 deletion(-)
create mode 100644 arch/riscv/boot/dts/sophgo/sg2000-milkv-duo-s.dts
create mode 100644 arch/riscv/boot/dts/sophgo/sg2000.dtsi
create mode 100644 arch/riscv/boot/dts/sophgo/sg2002-milkv-duo256m.dts
next parent reply other threads:[~2026-08-05 1:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1333a916-da71-432d-99ae-69cdb6061add@linux.dev>
2026-08-05 1:03 ` Chen Wang [this message]
[not found] <178638063763.3872609.9920540210952957691.git-patchwork-notify@kernel.org>
2026-08-11 0:16 ` Fwd: [GIT PULL] RISC-V Sophgo Devicetrees for v7.3 Chen Wang
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=9daba6e5-fa82-4ed9-b9f2-078dacec46f0@linux.dev \
--to=chen.wang@linux.dev \
--cc=sophgo@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