From: Conor Dooley <conor@kernel.org>
To: linux-riscv@lists.infradead.org
Cc: conor@kernel.org, "Conor Dooley" <conor.dooley@microchip.com>,
"Eric Biggers" <ebiggers@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Clément Léger" <cleger@rivosinc.com>,
"Andy Chiu" <andybnac@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>
Subject: [PATCH v3 6/6] dt-bindings: riscv: document vector crypto requirements
Date: Wed, 5 Feb 2025 16:05:12 +0000 [thread overview]
Message-ID: <20250205-ludicrous-gratify-b2ae27b95ebd@spud> (raw)
In-Reply-To: <20250205-cobbler-unpadded-5580c1f5d946@spud>
From: Conor Dooley <conor.dooley@microchip.com>
Section 35.2. Extensions Overview of [1] says:
| The Zvknhb and Zvbc Vector Crypto Extensions --and accordingly the composite extensions Zvkn and
| Zvks-- (sic) require a Zve64x base, or application ("V") base Vector Extension.
| All of the other Vector Crypto Extensions can be built on any embedded (Zve*) or application ("V") base
| Vector Extension
Eric Biggars pointed out that the spec is actually incorrect, and that
the list of instructions requiring a Zve64x base is actually: Zvkn,
Zvknc, Zvkng and Zvksc. Implement the rules according to his PR [2].
Link: https://github.com/riscv/riscv-isa-manual/releases/tag/riscv-isa-release-698e64a-2024-09-09 [1]
Link: https://github.com/riscv/riscv-isa-manual/pull/1697 [2]
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
---
.../devicetree/bindings/riscv/extensions.yaml | 33 +++++++++++++++++++
1 file changed, 33 insertions(+)
diff --git a/Documentation/devicetree/bindings/riscv/extensions.yaml b/Documentation/devicetree/bindings/riscv/extensions.yaml
index 02065664f819..9aeb9d4731ca 100644
--- a/Documentation/devicetree/bindings/riscv/extensions.yaml
+++ b/Documentation/devicetree/bindings/riscv/extensions.yaml
@@ -726,6 +726,39 @@ properties:
- contains:
const: zve64f
+ - if:
+ contains:
+ anyOf:
+ - const: zvbc
+ - const: zvkn
+ - const: zvknc
+ - const: zvkng
+ - const: zvknhb
+ - const: zvksc
+ then:
+ contains:
+ anyOf:
+ - const: v
+ - const: zve64x
+
+ - if:
+ contains:
+ anyOf:
+ - const: zvbb
+ - const: zvkb
+ - const: zvkg
+ - const: zvkned
+ - const: zvknha
+ - const: zvksed
+ - const: zvksh
+ - const: zvks
+ - const: zvkt
+ then:
+ contains:
+ anyOf:
+ - const: v
+ - const: zve32x
+
allOf:
# Zcf extension does not exist on rv64
- if:
--
2.45.2
prev parent reply other threads:[~2025-02-05 16:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 16:05 [PATCH v3 0/6] Add some validation for vector, vector crypto and fp stuff Conor Dooley
2025-02-05 16:05 ` [PATCH v3 1/6] RISC-V: add vector extension validation checks Conor Dooley
2025-02-06 10:08 ` Clément Léger
2025-02-06 11:19 ` Conor Dooley
2025-02-11 10:16 ` Clément Léger
2025-02-11 14:43 ` Conor Dooley
2025-02-05 16:05 ` [PATCH v3 2/6] RISC-V: add vector crypto " Conor Dooley
2025-02-06 10:20 ` Clément Léger
2025-02-06 11:24 ` Conor Dooley
2025-02-06 12:56 ` Clément Léger
2025-02-06 20:32 ` Eric Biggers
2025-02-07 0:02 ` Conor Dooley
2025-02-11 8:45 ` Clément Léger
2025-02-11 12:34 ` Conor Dooley
2025-02-11 13:33 ` Clément Léger
2025-02-05 16:05 ` [PATCH v3 3/6] RISC-V: add f & d " Conor Dooley
2025-02-06 10:08 ` Clément Léger
2025-02-11 10:22 ` Clément Léger
2025-02-11 12:06 ` Conor Dooley
2025-02-05 16:05 ` [PATCH v3 4/6] dt-bindings: riscv: d requires f Conor Dooley
2025-02-05 16:05 ` [PATCH v3 5/6] dt-bindings: riscv: add vector sub-extension dependencies Conor Dooley
2025-02-05 16:05 ` Conor Dooley [this message]
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=20250205-ludicrous-gratify-b2ae27b95ebd@spud \
--to=conor@kernel.org \
--cc=andybnac@gmail.com \
--cc=cleger@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=ebiggers@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.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