From: Conor Dooley <conor@kernel.org>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Guodong Xu <guodong@riscstar.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@sifive.com>,
Kevin Meng Zhang <zhangmeng.kevin@linux.spacemit.com>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, spacemit@lists.linux.dev,
linux-serial@vger.kernel.org, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, Yixun Lan <dlan@gentoo.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Samuel Holland <samuel.holland@sifive.com>,
Anup Patel <anup@brainfault.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Lubomir Rintel <lkundrak@v3.sk>, Yangyu Chen <cyy@cyyself.name>
Subject: Re: [PATCH 7/8] riscv: dts: spacemit: add initial device tree of SpacemiT K3 SoC
Date: Thu, 18 Dec 2025 00:56:40 +0000 [thread overview]
Message-ID: <20251218-basil-quantum-225ce16e4699@spud> (raw)
In-Reply-To: <f9b6b5e2-ec9e-4208-8267-77020e0a9411@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
On Wed, Dec 17, 2025 at 09:07:14AM +0100, Heinrich Schuchardt wrote:
> On 12/17/25 08:11, Guodong Xu wrote:
> > Specifically, I must adhere to
> > Documentation/devicetree/bindings/riscv/extensions.yaml (and cpus.yaml for
> > properties like 'riscv,sv39' which stands for the extension Sv39). If I
> > add extension strings that are not yet defined in these schemas, such as
> > supm, running 'make dtbs_check W=3' fails with: 'supm' is not one of
> > ['i', 'm', 'a', ...], followed by "Unevaluated properties are not allowed."
>
> If Documentation/devicetree/bindings/riscv/extensions.yaml is incomplete
> with respect to ratified extensions, I guess the right approach is to amend
> it and not to curtail the CPU description.
Absolutely. If the cpu supports something that is not documented, then
please document it rather than omit from the devicetree.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-12-18 0:56 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 13:32 [PATCH 0/8] riscv: spacemit: Add SpacemiT K3 SoC and K3 Pico-ITX board Guodong Xu
2025-12-16 13:32 ` [PATCH 1/8] dt-bindings: riscv: add SpacemiT X100 CPU compatible Guodong Xu
2025-12-16 14:08 ` Heinrich Schuchardt
2025-12-16 15:07 ` Yixun Lan
2025-12-17 2:06 ` Guodong Xu
2025-12-16 15:16 ` Yixun Lan
2025-12-17 3:38 ` Guodong Xu
2025-12-16 15:33 ` Krzysztof Kozlowski
2025-12-17 1:54 ` Guodong Xu
2025-12-16 13:32 ` [PATCH 2/8] dt-bindings: timer: add SpacemiT K3 CLINT Guodong Xu
2025-12-16 16:40 ` Conor Dooley
2025-12-16 13:32 ` [PATCH 3/8] dt-bindings: interrupt-controller: add SpacemiT K3 APLIC Guodong Xu
2025-12-16 16:40 ` Conor Dooley
2025-12-16 13:32 ` [PATCH 4/8] dt-bindings: interrupt-controller: add SpacemiT K3 IMSIC Guodong Xu
2025-12-16 15:33 ` Krzysztof Kozlowski
2025-12-17 3:48 ` Guodong Xu
2025-12-16 13:32 ` [PATCH 5/8] dt-bindings: serial: 8250: add SpacemiT K3 UART compatible Guodong Xu
2025-12-16 16:41 ` Conor Dooley
2025-12-16 13:32 ` [PATCH 6/8] dt-bindings: riscv: spacemit: add K3 and Pico-ITX board bindings Guodong Xu
2025-12-16 15:05 ` Yixun Lan
2025-12-16 16:33 ` Conor Dooley
2025-12-17 1:23 ` Guodong Xu
2025-12-16 13:32 ` [PATCH 7/8] riscv: dts: spacemit: add initial device tree of SpacemiT K3 SoC Guodong Xu
2025-12-16 14:24 ` Heinrich Schuchardt
2025-12-17 7:11 ` Guodong Xu
2025-12-17 8:07 ` Heinrich Schuchardt
2025-12-18 0:56 ` Conor Dooley [this message]
2025-12-19 2:03 ` Guodong Xu
2025-12-19 8:08 ` Heinrich Schuchardt
2025-12-20 2:48 ` Yao Zi
2025-12-22 9:27 ` Guodong Xu
2025-12-20 23:23 ` Conor Dooley
2025-12-21 0:10 ` Heinrich Schuchardt
2025-12-22 10:32 ` Guodong Xu
2025-12-22 20:36 ` Conor Dooley
2025-12-26 6:53 ` Guodong Xu
2026-01-01 0:24 ` Conor Dooley
2025-12-16 15:35 ` Krzysztof Kozlowski
2025-12-17 5:39 ` Guodong Xu
2025-12-16 13:32 ` [PATCH 8/8] riscv: dts: spacemit: add SpacemiT K3 Pico-ITX board device tree Guodong Xu
2025-12-16 14:33 ` Heinrich Schuchardt
2025-12-17 7:13 ` Guodong Xu
2025-12-17 9:04 ` Bo Gan
2025-12-18 22:43 ` Guodong Xu
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=20251218-basil-quantum-225ce16e4699@spud \
--to=conor@kernel.org \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=cyy@cyyself.name \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=gregkh@linuxfoundation.org \
--cc=guodong@riscstar.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=jirislaby@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=palmer@dabbelt.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=spacemit@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=zhangmeng.kevin@linux.spacemit.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).