From: Jisheng Zhang <jszhang@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <maz@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org,
Inochi Amaoto <inochiama@outlook.com>
Subject: [PATCH v2 0/5] Add Milk-V Duo board support
Date: Fri, 6 Oct 2023 20:14:44 +0800 [thread overview]
Message-ID: <20231006121449.721-1-jszhang@kernel.org> (raw)
Milk-V Duo[1] board is an embedded development platform based on the
CV1800B[2] chip. Add minimal device tree files for the development board.
Currently, now it's supported to boot to a basic shell.
NOTE: this series is based on the SG2042 upstream series[3] for the vendor
prefix and ARCH_SOPHGO option.
Link: https://milkv.io/duo [1]
Link: https://en.sophgo.com/product/introduce/cv180xB.html [2]
Link: https://lore.kernel.org/linux-riscv/cover.1696433229.git.unicorn_wang@outlook.com/ [3]
since v1:
- fix dtbs_check warning
- add clint node
- sort dts in Makefile
Jisheng Zhang (5):
dt-bindings: interrupt-controller: Add SOPHGO CV1800B plic
dt-bindings: timer: Add SOPHGO CV1800B clint
dt-bindings: riscv: Add Milk-V Duo board compatibles
riscv: dts: sophgo: add initial CV1800B SoC device tree
riscv: dts: sophgo: add Milk-V Duo board device tree
.../sifive,plic-1.0.0.yaml | 1 +
.../devicetree/bindings/riscv/sophgo.yaml | 4 +
.../bindings/timer/sifive,clint.yaml | 1 +
arch/riscv/boot/dts/sophgo/Makefile | 2 +-
.../boot/dts/sophgo/cv1800b-milkv-duo.dts | 38 ++++++
arch/riscv/boot/dts/sophgo/cv1800b.dtsi | 123 ++++++++++++++++++
6 files changed, 168 insertions(+), 1 deletion(-)
create mode 100644 arch/riscv/boot/dts/sophgo/cv1800b-milkv-duo.dts
create mode 100644 arch/riscv/boot/dts/sophgo/cv1800b.dtsi
--
2.40.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2023-10-06 12:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 12:14 Jisheng Zhang [this message]
2023-10-06 12:14 ` [PATCH v2 1/5] dt-bindings: interrupt-controller: Add SOPHGO CV1800B plic Jisheng Zhang
2023-10-06 12:14 ` [PATCH v2 2/5] dt-bindings: timer: Add SOPHGO CV1800B clint Jisheng Zhang
2023-10-06 12:14 ` [PATCH v2 3/5] dt-bindings: riscv: Add Milk-V Duo board compatibles Jisheng Zhang
2023-10-06 12:14 ` [PATCH v2 4/5] riscv: dts: sophgo: add initial CV1800B SoC device tree Jisheng Zhang
2023-10-07 12:42 ` Chen Wang
2023-10-06 12:14 ` [PATCH v2 5/5] riscv: dts: sophgo: add Milk-V Duo board " Jisheng Zhang
2023-10-07 12:44 ` Chen Wang
2023-10-06 14:21 ` [PATCH v2 0/5] Add Milk-V Duo board support Conor Dooley
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=20231006121449.721-1-jszhang@kernel.org \
--to=jszhang@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@outlook.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).