From: Joshua Milas <josh.milas@gmail.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
unicorn_wang@outlook.com, inochiama@gmail.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr,
alexander.sverdlin@gmail.com, rabenda.cn@gmail.com,
thomas.bonnefille@bootlin.com, chao.wei@sophgo.com,
liujingqi@lanxincomputing.com
Cc: josh.milas@gmail.com, devicetree@vger.kernel.org,
sophgo@lists.linux.dev, linux-riscv@lists.infradead.org
Subject: [PATCH 0/3] Add initial Milk-V Duo S board support
Date: Fri, 10 Oct 2025 21:48:08 -0400 [thread overview]
Message-ID: <20251011014811.28521-1-josh.milas@gmail.com> (raw)
This adds an initial device tree for the Milk-V Duo S board
with support for reading from the SD card and network over
ethernet. This is continued work from Michael Opdenacker's
v6 series [1] on the ARM64 and RISCV side. It has been tested
with both ARM64 and RISCV64.
---
v2
- Made new entry in docs to avoid DTC check error
- "Milk-V DuoS" -> "Milk-V Duo S"
- Sorting of aliases
- Added uart*, emmc, mdio, gmac0, i2c*, spi*, dmac, saradc
to device tree matching what is available on the pinout [2]
and available in the device tree includes
- Removal of 'no-mmc' and 'no-sdio' for sdhci0 as it works
without
- Added riscv device tree
Link: https://lore.kernel.org/linux-riscv/20240421055710.143617-1-michael.opdenacker@bootlin.com/ [1]
Link: https://milkv.io/duo-s/duos-pinout.webp [2]
Joshua Milas (3):
dt-bindings: soc: sophgo: add Milk-V Duo S board compatibles
arm64: dts: sophgo: add initial Milk-V Duo S board support
riscv64: dts: sophgo: add initial Milk-V Duo S board support
.../bindings/soc/sophgo/sophgo.yaml | 5 +
arch/arm64/boot/dts/sophgo/Makefile | 1 +
.../boot/dts/sophgo/sg2000-milkv-duo-s.dts | 110 ++++++++++++++++++
arch/riscv/boot/dts/sophgo/Makefile | 1 +
.../boot/dts/sophgo/cv1812h-milkv-duo-s.dts | 110 ++++++++++++++++++
5 files changed, 227 insertions(+)
create mode 100644 arch/arm64/boot/dts/sophgo/sg2000-milkv-duo-s.dts
create mode 100644 arch/riscv/boot/dts/sophgo/cv1812h-milkv-duo-s.dts
base-commit: 0251a1deaec78252cb311fc8305d3670bc5eee0e
--
2.51.0
next reply other threads:[~2025-10-11 1:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-11 1:48 Joshua Milas [this message]
2025-10-11 1:48 ` [PATCH 1/3] dt-bindings: soc: sophgo: add Milk-V Duo S board compatibles Joshua Milas
2025-10-11 1:50 ` Inochi Amaoto
2025-10-11 1:48 ` [PATCH 2/3] arm64: dts: sophgo: add initial Milk-V Duo S board support Joshua Milas
2025-10-11 1:56 ` Inochi Amaoto
2025-10-11 19:19 ` Joshua Milas
2025-10-13 0:43 ` Inochi Amaoto
2025-10-26 21:35 ` Joshua Milas
2025-10-26 22:48 ` Michael Opdenacker
2025-10-28 23:23 ` Joshua Milas
2025-10-29 0:53 ` Inochi Amaoto
2025-10-30 12:50 ` Michael Opdenacker
2025-10-11 1:48 ` [PATCH 3/3] riscv64: " Joshua Milas
2025-10-11 1:57 ` Inochi Amaoto
2025-10-11 2:16 ` [PATCH 0/3] Add " Chen Wang
2025-10-14 3:27 ` 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=20251011014811.28521-1-josh.milas@gmail.com \
--to=josh.milas@gmail.com \
--cc=alex@ghiti.fr \
--cc=alexander.sverdlin@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=chao.wei@sophgo.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=liujingqi@lanxincomputing.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rabenda.cn@gmail.com \
--cc=robh@kernel.org \
--cc=sophgo@lists.linux.dev \
--cc=thomas.bonnefille@bootlin.com \
--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;
as well as URLs for NNTP newsgroup(s).