From: michael.opdenacker@bootlin.com
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Chen Wang <unicorn_wang@outlook.com>,
Inochi Amaoto <inochiama@outlook.com>
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>,
linux-riscv@lists.infradead.org
Subject: [PATCH v3 0/2] add initial Milk-V Duo S board support
Date: Wed, 10 Apr 2024 08:22:52 +0200 [thread overview]
Message-ID: <20240410062254.2955647-1-michael.opdenacker@bootlin.com> (raw)
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
This adds an initial device tree for the Milk-V Duo S board.
Last tested on linux-next as a May 9, 2024.
- Changes in V3
- Fix enum in devicetree/bindings/riscv/sophgo.yaml
- Changes in V2:
- Add a first patch to register the new compatible string
for this board.
- Use a correct SoC compatible string
- Add "disable-wp" (disable write protect) property
to enable write access to the external SD card.
Many thanks to reviewers!
Michael Opdenacker (2):
dt-bindings: riscv: add Milk-V Duo S board compatibles
riscv: dts: sophgo: add initial Milk-V Duo S board support
.../devicetree/bindings/riscv/sophgo.yaml | 1 +
arch/riscv/boot/dts/sophgo/Makefile | 1 +
.../boot/dts/sophgo/sg2000-milkv-duos.dts | 39 +++++++++++++++++++
3 files changed, 41 insertions(+)
create mode 100644 arch/riscv/boot/dts/sophgo/sg2000-milkv-duos.dts
--
2.34.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2024-04-10 6:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 6:22 michael.opdenacker [this message]
2024-04-10 6:22 ` [PATCH v3 1/2] dt-bindings: riscv: add Milk-V Duo S board compatibles michael.opdenacker
2024-04-10 7:19 ` Inochi Amaoto
2024-04-10 7:55 ` Michael Opdenacker
2024-04-10 10:17 ` Inochi Amaoto
2024-04-10 6:22 ` [PATCH v3 2/2] riscv: dts: sophgo: add initial Milk-V Duo S board support michael.opdenacker
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=20240410062254.2955647-1-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=aou@eecs.berkeley.edu \
--cc=inochiama@outlook.com \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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).