From: Chen-Yu Yeh <chenyou910331@gmail.com>
To: chen.wang@linux.dev, inochiama@gmail.com
Cc: Chen-Yu Yeh <chenyou910331@gmail.com>,
Conor Dooley <conor.dooley@microchip.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Han Gao <rabenda.cn@gmail.com>,
Joshua Milas <josh.milas@gmail.com>,
Alexander Sverdlin <alex@sverdlin.org>,
Chao Wei <chao.wei@sophgo.com>,
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
sophgo@lists.linux.dev (open list:SOPHGO DEVICETREES and DRIVERS),
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH v4 1/3] dt-bindings: soc: sophgo: add Milk-V Duo 256M board
Date: Wed, 22 Jul 2026 07:34:42 +0800 [thread overview]
Message-ID: <20260721233452.112204-2-chenyou910331@gmail.com> (raw)
In-Reply-To: <20260721233452.112204-1-chenyou910331@gmail.com>
Add compatible string for the Milk-V Duo 256M board.
Signed-off-by: Chen-Yu Yeh <chenyou910331@gmail.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
---
Documentation/devicetree/bindings/soc/sophgo/sophgo.yaml | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/soc/sophgo/sophgo.yaml b/Documentation/devicetree/bindings/soc/sophgo/sophgo.yaml
index 0b6fbab48b74..99194d8721ef 100644
--- a/Documentation/devicetree/bindings/soc/sophgo/sophgo.yaml
+++ b/Documentation/devicetree/bindings/soc/sophgo/sophgo.yaml
@@ -35,6 +35,10 @@ properties:
- enum:
- milkv,duo-s
- const: sophgo,sg2000
+ - items:
+ - enum:
+ - milkv,duo256m
+ - const: sophgo,sg2002
- items:
- enum:
- sipeed,licheerv-nano-b
--
2.43.0
next parent reply other threads:[~2026-07-21 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260721233452.112204-1-chenyou910331@gmail.com>
2026-07-21 23:34 ` Chen-Yu Yeh [this message]
2026-07-21 23:34 ` [PATCH v4 2/3] riscv: dts: sophgo: cv180x: Add PWR_GPIO controller Chen-Yu Yeh
2026-07-21 23:34 ` [PATCH v4 3/3] riscv: dts: sophgo: Add Milk-V Duo 256M board support Chen-Yu Yeh
2026-07-21 23:45 ` sashiko-bot
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=20260721233452.112204-2-chenyou910331@gmail.com \
--to=chenyou910331@gmail.com \
--cc=alex@sverdlin.org \
--cc=chao.wei@sophgo.com \
--cc=chen.wang@linux.dev \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@gmail.com \
--cc=josh.milas@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rabenda.cn@gmail.com \
--cc=robh@kernel.org \
--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