From: Conor Dooley <conor@kernel.org>
To: linux-riscv@lists.infradead.org
Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Heiko Stuebner <heiko@sntech.de>,
Andrew Jones <ajones@ventanamicro.com>,
Sunil V L <sunilvl@ventanamicro.com>,
Yangyu Chen <cyy@cyyself.name>,
devicetree@vger.kernel.org
Subject: [RFC 2/6] dt-bindings: riscv: add riscv,isa-extension-* property and incompatible example
Date: Mon, 8 May 2023 19:16:22 +0100 [thread overview]
Message-ID: <20230508-sneeze-cesarean-d1aff8be9cc8@spud> (raw)
In-Reply-To: <20230508-hypnotic-phobia-99598439d828@spud>
From: Conor Dooley <conor.dooley@microchip.com>
This dt-binding is illustrative *only*, it doesn't yet do what I want it
to do in terms of enforcement etc. I am yet to figure out exactly how to
wrangle the binding such that the individual properties have more
generous versions than the generic pattern property.
This binding *will* generate errors, and needs rework before it can
seriously be considered.
Nevertheless, it should demonstrate how I intend such a property be
used.
Not-signed-off-by: Conor Dooley <conor.dooley@microchip.com>
---
.../devicetree/bindings/riscv/cpus.yaml | 61 ++++++++++++++++++-
1 file changed, 60 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/riscv/cpus.yaml b/Documentation/devicetree/bindings/riscv/cpus.yaml
index 405915b04d69..cccb3b2ae23d 100644
--- a/Documentation/devicetree/bindings/riscv/cpus.yaml
+++ b/Documentation/devicetree/bindings/riscv/cpus.yaml
@@ -100,6 +100,15 @@ properties:
lowercase.
$ref: "/schemas/types.yaml#/definitions/string"
pattern: ^rv(?:64|32)imaf?d?q?c?b?k?j?p?v?h?(?:[hsxz](?:[a-z])+)?(?:_[hsxz](?:[a-z])+)*$
+ deprecated: true
+
+ riscv,isa-base:
+ description:
+ Identifies the base ISA supported by a hart.
+ $ref: "/schemas/types.yaml#/definitions/string"
+ enum:
+ - rv32i
+ - rv64i
# RISC-V requires 'timebase-frequency' in /cpus, so disallow it here
timebase-frequency: false
@@ -136,8 +145,32 @@ properties:
DMIPS/MHz, relative to highest capacity-dmips-mhz
in the system.
+ riscv,isa-extension-v:
+ description: RISC-V Vector extension
+ $ref: "/schemas/types.yaml#/definitions/string"
+ oneOf:
+ - const: v1.0.0
+ description: the original incarnation
+ - const: v1.0.1
+ description: backwards compat was broken here
+
+patternProperties:
+ "^riscv,isa-extension-*":
+ description:
+ Catch-all property for ISA extensions that do not need any special
+ handling, and of which all known versions are compatible with their
+ original revision.
+ $ref: "/schemas/types.yaml#/definitions/string"
+ enum:
+ - v1.0.0
+
+oneOf:
+ - required:
+ - riscv,isa-base
+ - required:
+ - riscv,isa
+
required:
- - riscv,isa
- interrupt-controller
additionalProperties: true
@@ -208,4 +241,30 @@ examples:
};
};
};
+
+ - |
+ // Example 3: Extension specification
+ cpus {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ cpu@0 {
+ device_type = "cpu";
+ reg = <0>;
+ compatible = "riscv";
+ riscv,isa-base = "rv64i";
+ riscv,isa-extension-i = "v1.0.0";
+ riscv,isa-extension-m = "v1.0.0";
+ riscv,isa-extension-a = "v1.0.0";
+ riscv,isa-extension-f = "v1.0.0";
+ riscv,isa-extension-d = "v1.0.0";
+ riscv,isa-extension-c = "v2.0.0";
+ riscv,isa-extension-v = "v1.0.1";
+ mmu-type = "riscv,sv48";
+ interrupt-controller {
+ #interrupt-cells = <1>;
+ interrupt-controller;
+ compatible = "riscv,cpu-intc";
+ };
+ };
+ };
...
--
2.39.2
next prev parent reply other threads:[~2023-05-08 18:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 18:16 [RFC 0/6] Deprecate riscv,isa DT property? Conor Dooley
2023-05-08 18:16 ` [RFC 1/6] dt-bindings: riscv: clarify what an unversioned extension means Conor Dooley
2023-05-13 17:46 ` Krzysztof Kozlowski
2023-05-08 18:16 ` Conor Dooley [this message]
2023-05-13 17:50 ` [RFC 2/6] dt-bindings: riscv: add riscv,isa-extension-* property and incompatible example Krzysztof Kozlowski
2023-05-13 18:00 ` Conor Dooley
2023-05-08 18:16 ` [RFC 3/6] RISC-V: deprecate riscv,isa & replace it with per-extension properties Conor Dooley
2023-05-08 18:16 ` [RFC 4/6] RISC-V: add support for riscv,isa-base property Conor Dooley
2023-05-08 18:16 ` [RFC 5/6] RISC-V: drop a needless check in print_isa_ext() Conor Dooley
2023-05-08 18:16 ` [RFC 6/6] riscv: dts: microchip: use new riscv,isa-extension-* properties for mpfs Conor Dooley
2023-05-11 21:27 ` [RFC 0/6] Deprecate riscv,isa DT property? Atish Patra
2023-05-11 21:47 ` Conor Dooley
2023-05-11 22:34 ` Atish Patra
2023-05-11 22:38 ` Conor Dooley
2023-05-12 18:01 ` Palmer Dabbelt
2023-05-12 19:40 ` Conor Dooley
2023-05-12 22:05 ` Conor Dooley
2023-05-12 23:20 ` Atish Patra
2023-05-12 23:52 ` Conor Dooley
2023-05-12 23:55 ` Palmer Dabbelt
2023-05-13 0:09 ` Conor Dooley
2023-05-13 0:38 ` Palmer Dabbelt
2023-05-13 7:47 ` Anup Patel
2023-05-13 21:34 ` Jessica Clarke
2023-05-13 21:54 ` Conor Dooley
2023-05-15 4:38 ` Sunil V L
2023-05-15 7:52 ` Conor Dooley
2023-05-12 18:08 ` Palmer Dabbelt
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=20230508-sneeze-cesarean-d1aff8be9cc8@spud \
--to=conor@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=cyy@cyyself.name \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=sunilvl@ventanamicro.com \
/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