From: "Clément Léger" <cleger@rivosinc.com>
To: Conor Dooley <conor@kernel.org>, linux-riscv@lists.infradead.org
Cc: Conor Dooley <conor.dooley@microchip.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Andy Chiu <andybnac@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC v1 4/5] dt-bindings: riscv: add vector sub-extension dependencies
Date: Thu, 3 Oct 2024 09:52:12 +0200 [thread overview]
Message-ID: <e10bff0c-a243-4280-925a-ceba13d0f1b4@rivosinc.com> (raw)
In-Reply-To: <20241002-eagle-fresh-4b2e259e45ee@spud>
On 02/10/2024 18:10, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> Section 33.18.2. Zve*: Vector Extensions for Embedded Processors
> in [1] says:
> | The Zve32f and Zve64x extensions depend on the Zve32x extension. The Zve64f extension depends
> | on the Zve32f and Zve64x extensions. The Zve64d extension depends on the Zve64f extension
>
> | The Zve32x extension depends on the Zicsr extension. The Zve32f and Zve64f extensions depend
> | upon the F extension
>
> | The Zve64d extension depends upon the D extension
>
> Apply these rules to the bindings to help prevent invalid combinations.
>
> Link: https://github.com/riscv/riscv-isa-manual/releases/tag/riscv-isa-release-698e64a-2024-09-09 [1]
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> .../devicetree/bindings/riscv/extensions.yaml | 46 +++++++++++++++++++
> 1 file changed, 46 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/riscv/extensions.yaml b/Documentation/devicetree/bindings/riscv/extensions.yaml
> index 779f5cfab806e..abf2579171c5b 100644
> --- a/Documentation/devicetree/bindings/riscv/extensions.yaml
> +++ b/Documentation/devicetree/bindings/riscv/extensions.yaml
> @@ -605,6 +605,52 @@ properties:
> contains:
> const: zca
>
> + - if:
> + contains:
> + const: zve32x
> + then:
> + contains:
> + const: zicsr
> +
> + - if:
> + contains:
> + const: zve32f
> + then:
> + allOf:
> + - contains:
> + const: f
> + - contains:
> + const: zve32x
> +
> + - if:
> + contains:
> + const: zve64x
> + then:
> + contains:
> + const: zve32x
> +
> + - if:
> + contains:
> + const: zve64f
> + then:
> + allOf:
> + - contains:
> + const: f
> + - contains:
> + const: zve32f
> + - contains:
> + const: zve64x
> +
> + - if:
> + contains:
> + const: zve64d
> + then:
> + allOf:
> + - contains:
> + const: d
> + - contains:
> + const: zve64f
> +
> allOf:
> # Zcf extension does not exist on rv64
> - if:
Looks good to me.
Reviewed-by: Clément léger <cleger@rivosinc.com>
Thanks,
Clément
next prev parent reply other threads:[~2024-10-03 7:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 16:10 [RFC v1 0/5] Add some validation for vector, vector crypto and fp stuff Conor Dooley
2024-10-02 16:10 ` [RFC v1 1/5] RISC-V: add vector crypto extension validation checks Conor Dooley
2024-10-02 16:10 ` [RFC v1 2/5] RISC-V: add f & d " Conor Dooley
2024-10-03 7:49 ` Clément Léger
2024-10-03 10:57 ` Conor Dooley
2024-10-02 16:10 ` [RFC v1 3/5] dt-bindings: riscv: d requires f Conor Dooley
2024-10-03 7:46 ` Clément Léger
2024-10-03 9:50 ` Krzysztof Kozlowski
2024-10-02 16:10 ` [RFC v1 4/5] dt-bindings: riscv: add vector sub-extension dependencies Conor Dooley
2024-10-03 7:52 ` Clément Léger [this message]
2024-10-03 9:52 ` Krzysztof Kozlowski
2024-10-02 16:10 ` [RFC v1 5/5] dt-bindings: riscv: document vector crypto requirements Conor Dooley
2024-10-03 7:59 ` Clément Léger
2024-10-03 11:05 ` Conor Dooley
2024-10-03 11:36 ` Clément Léger
2024-10-03 9:52 ` Krzysztof Kozlowski
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=e10bff0c-a243-4280-925a-ceba13d0f1b4@rivosinc.com \
--to=cleger@rivosinc.com \
--cc=andybnac@gmail.com \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®