I'd argue this changes the definition of the I binding, as there was
more than just the counters that got split out (CSRs and fence.i at
least). We haven't released these bindings yet, so IIUC it's OK to
change the definition still.
I think this matches the original intent, or at least what the
implementation does.
Fixes: aeb71e42caae ("dt-bindings: riscv: deprecate riscv,isa")
Signed-off-by: Palmer Dabbelt <palmer@xxxxxxxxxxxx>
---
.../devicetree/bindings/riscv/extensions.yaml | 12 +++++-------
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/Documentation/devicetree/bindings/riscv/extensions.yaml b/Documentation/devicetree/bindings/riscv/extensions.yaml
index cc1f546fdbdc..31ec244bd32f 100644
--- a/Documentation/devicetree/bindings/riscv/extensions.yaml
+++ b/Documentation/devicetree/bindings/riscv/extensions.yaml
@@ -67,13 +67,11 @@ properties:
anyOf:
# single letter extensions, in canonical order
- const: i
- description: |
- The base integer instruction set, as ratified in the 20191213
- version of the unprivileged ISA specification.
-
- This does not include Chapter 10, "Counters", which was moved into
- the Zicntr and Zihpm extensions after the ratification of the
- 20191213 version of the unprivileged specification.
+ description:
+ The base integer instruction set, as specified by the 2.2
+ version of the unprivileged ISA specification, formally known as
+ the user-level ISA. This definition of I includes various
+ extensions that were later split out.
- const: m
description:
--
2.40.1
