]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
Merge patch series "Add some validation for vector, vector crypto and fp stuff"
authorAlexandre Ghiti <alexghiti@rivosinc.com>
Tue, 1 Apr 2025 07:06:41 +0000 (07:06 +0000)
committerAlexandre Ghiti <alexghiti@rivosinc.com>
Tue, 1 Apr 2025 07:06:41 +0000 (07:06 +0000)
commit004961843389e4d9447303910790dc2e6415899d
treeef786e51d38b7d91e345764320ae1f6106917049
parent79ba5c1c7767a539f42c6f6db46961b0bec2bc03
parenta0d857205756af45abaf63ca15b2640f707d5e73
Merge patch series "Add some validation for vector, vector crypto and fp stuff"

Conor Dooley <conor@kernel.org> says:

From: Conor Dooley <conor.dooley@microchip.com>

Yo,

This series is partly leveraging Clement's work adding a validate
callback in the extension detection code so that things like checking
for whether a vector crypto extension is usable can be done like:
has_extension(<vector crypto>)
rather than
has_vector() && has_extension(<vector crypto>)
which Eric pointed out was a poor design some months ago.

The rest of this is adding some requirements to the bindings that
prevent combinations of extensions disallowed by the ISA.

There's a bunch of over-long lines in here, but I thought that the
over-long lines were clearer than breaking them up.

Cheers,
Conor.

* patches from https://lore.kernel.org/r/20250312-abide-pancreas-3576b8c44d2c@spud:
  dt-bindings: riscv: document vector crypto requirements
  dt-bindings: riscv: add vector sub-extension dependencies
  dt-bindings: riscv: d requires f
  RISC-V: add f & d extension validation checks
  RISC-V: add vector crypto extension validation checks
  RISC-V: add vector extension validation checks

Link: https://lore.kernel.org/r/20250312-abide-pancreas-3576b8c44d2c@spud
Signed-off-by: Alexandre Ghiti <alexghiti@rivosinc.com>
Documentation/devicetree/bindings/riscv/extensions.yaml
arch/riscv/include/asm/cpufeature.h
arch/riscv/kernel/cpufeature.c