From: Eric Biggers <ebiggers@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org,
"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>,
"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: Re: [PATCH v2 5/5] dt-bindings: riscv: document vector crypto requirements
Date: Thu, 24 Oct 2024 19:24:11 -0700 [thread overview]
Message-ID: <20241025022411.GB1781@sol.localdomain> (raw)
In-Reply-To: <20241024-pungent-lasso-42dd3512a3c8@spud>
On Thu, Oct 24, 2024 at 01:34:33PM +0100, Conor Dooley wrote:
> 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
>
> Apply these rules in the binding, so that invalid combinations can be
> avoided.
It looks like that part of the spec is wrong, though. The Zvknhb and Zvbc are
correct, but the list of the composite extensions that at least one of them is
included in is: Zvkn, Zvknc, Zvkng, Zvksc.
- Eric
next prev parent reply other threads:[~2024-10-25 2:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 12:34 [PATCH v2 0/5] Add some validation for vector, vector crypto and fp stuff Conor Dooley
2024-10-24 12:34 ` [PATCH v2 1/5] RISC-V: add vector crypto extension validation checks Conor Dooley
2024-10-25 2:08 ` Eric Biggers
2024-10-25 16:52 ` Conor Dooley
2024-10-24 12:34 ` [PATCH v2 2/5] RISC-V: add f & d " Conor Dooley
2024-10-24 12:34 ` [PATCH v2 3/5] dt-bindings: riscv: d requires f Conor Dooley
2024-10-24 12:34 ` [PATCH v2 4/5] dt-bindings: riscv: add vector sub-extension dependencies Conor Dooley
2024-10-24 12:34 ` [PATCH v2 5/5] dt-bindings: riscv: document vector crypto requirements Conor Dooley
2024-10-25 2:24 ` Eric Biggers [this message]
2024-10-25 2:42 ` Eric Biggers
2024-10-25 16:53 ` Conor Dooley
2025-01-18 0:54 ` Charlie Jenkins
2025-01-20 17:17 ` 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=20241025022411.GB1781@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=andybnac@gmail.com \
--cc=cleger@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.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