From: Rob Herring <robh@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: palmer@dabbelt.com, Conor Dooley <conor.dooley@microchip.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/6] dt-bindings: riscv: cpus: switch to unevaluatedProperties: false
Date: Thu, 15 Jun 2023 11:47:34 -0600 [thread overview]
Message-ID: <20230615174734.GA1240678-robh@kernel.org> (raw)
In-Reply-To: <20230610-snaking-version-81ae5abb7573@spud>
On Sat, Jun 10, 2023 at 06:24:47PM +0100, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> Do the various bits needed to drop the additionalProperties: true that
> we currently have in riscv/cpu.yaml, to permit actually enforcing what
> people put in cpus nodes.
Arm needs pretty much all the same properties. I started on adding them
to cpu.yaml a while back. Let me finish that up.
>
> CC: Rob Herring <robh+dt@kernel.org>
> CC: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
> CC: Paul Walmsley <paul.walmsley@sifive.com>
> CC: Palmer Dabbelt <palmer@dabbelt.com>
> CC: linux-riscv@lists.infradead.org
> CC: devicetree@vger.kernel.org
> CC: linux-kernel@vger.kernel.org
>
> Conor Dooley (6):
> dt-bindings: riscv: cpus: add a ref the common cpu schema
> dt-bindings: riscv: cpus: allow clocks property
I just have 'clocks: true', so if you want to keep this setting it to 1
clock that's fine. But I imagine that it's just a matter of time until
someone wants more clocks.
> dt-bindings: riscv: cpus: add a ref to thermal-cooling-cells
> dt-bindings: riscv: cpus: permit operating-points-v2
> dt-bindings: riscv: cpus: document cpu-supply
> dt-bindings: riscv: cpus: switch to unevaluatedProperties: false
>
> .../devicetree/bindings/riscv/cpus.yaml | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
> --
> 2.39.2
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-06-15 17:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-10 17:24 [PATCH v1 0/6] dt-bindings: riscv: cpus: switch to unevaluatedProperties: false Conor Dooley
2023-06-10 17:24 ` [PATCH v1 1/6] dt-bindings: riscv: cpus: add a ref the common cpu schema Conor Dooley
2023-06-10 17:24 ` [PATCH v1 2/6] dt-bindings: riscv: cpus: allow clocks property Conor Dooley
2023-06-10 17:24 ` [PATCH v1 3/6] dt-bindings: riscv: cpus: add a ref to thermal-cooling-cells Conor Dooley
2023-06-10 17:24 ` [PATCH v1 4/6] dt-bindings: riscv: cpus: permit operating-points-v2 Conor Dooley
2023-06-10 17:24 ` [PATCH v1 5/6] dt-bindings: riscv: cpus: document cpu-supply Conor Dooley
2023-06-10 17:24 ` [PATCH v1 6/6] dt-bindings: riscv: cpus: switch to unevaluatedProperties: false Conor Dooley
2023-06-15 17:47 ` Rob Herring [this message]
2023-06-15 21:46 ` [PATCH v1 0/6] " 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=20230615174734.GA1240678-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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).