From: Conor Dooley <conor@kernel.org>
To: Eric Biggers <ebiggers@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
Subject: Re: [PATCH v3 2/6] RISC-V: add vector crypto extension validation checks
Date: Fri, 7 Feb 2025 00:02:56 +0000 [thread overview]
Message-ID: <20250206-prong-sandfish-417a3bf9de29@spud> (raw)
In-Reply-To: <20250206203249.GC1237@sol.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
On Thu, Feb 06, 2025 at 12:32:49PM -0800, Eric Biggers wrote:
> On Wed, Feb 05, 2025 at 04:05:08PM +0000, Conor Dooley wrote:
> > The 1.0.0 Vector crypto spec states:
> > The Zvknhb and Zvbc Vector Crypto Extensions --and accordingly
> > the composite extensions Zvkn and Zvks-- 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.
>
> As previously discussed, the above paragraph incorrectly lists the set of crypto
> extensions that require support for 64-bit elements. I have fixed this in the
> latest RISC-V ISA manual. It looks like this patch would still do the same
> thing either way, since it actually just checks that vector is available in some
> form. But this is not the best version of the manual to quote from.
/sigh, I updated the binding commit message but not the code one. That
one should probably change too, given that's now merged.
That's a stupid oversight, thanks.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-02-07 0:03 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 [this message]
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 ` [PATCH v3 6/6] dt-bindings: riscv: document vector crypto requirements 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=20250206-prong-sandfish-417a3bf9de29@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=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