* [PATCH v2 0/3] dt-bindings: riscv: Add RISC-V Worlds and SiFive WorldGuard DT bindings
@ 2026-07-29 16:39 ` Yu-Chien Peter Lin
0 siblings, 0 replies; 23+ messages in thread
From: Yu-Chien Peter Lin @ 2026-07-29 16:39 UTC (permalink / raw)
To: devicetree, linux-riscv, linux-kernel
Cc: robh, krzk+dt, conor+dt, pjw, palmer, aou, alex, samuel.holland,
dlan, guodong, dfustini, michal.simek, junhui.liu,
darshan.prajapati, akpm, zhangchunyan, luxu.kernel, pincheng.plct,
nick.hu, jim.shu, zong.li, greentime.hu, robin.randhawa, scott,
dave.patel, raymond.mao, anup, pawandeep.oza, Yu-Chien Peter Lin
Add device tree bindings for RISC-V Worlds, a standard extension that tags
every transaction with a World ID for fine-grained isolation. SiFive's
WorldGuard Checker is a hardware firewall in the system interconnect that
inspects transaction WIDs and enforces per-World access policies on memory
and MMIO devices.
wgChecker specification reference:
https://github.com/riscvarchive/security/blob/main/papers/worldguard%20proposal.pdf
Yu-Chien Peter Lin (3):
dt-bindings: riscv: Add Worlds ISA extensions
dt-bindings: riscv: Add Worlds per-hart properties
dt-bindings: sifive: Add WorldGuard Checker
.../devicetree/bindings/riscv/cpus.yaml | 61 +++
.../devicetree/bindings/riscv/extensions.yaml | 53 +++
.../devicetree/bindings/riscv/worlds.yaml | 86 +++++
.../bindings/sifive/sifive,wgchecker2.yaml | 356 ++++++++++++++++++
4 files changed, 556 insertions(+)
create mode 100644 Documentation/devicetree/bindings/riscv/worlds.yaml
create mode 100644 Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
--
2.43.7
^ permalink raw reply [flat|nested] 23+ messages in thread
* [PATCH v2 1/3] dt-bindings: riscv: Add Worlds ISA extensions
2026-07-29 16:39 ` Yu-Chien Peter Lin
@ 2026-07-29 16:39 ` Yu-Chien Peter Lin
-1 siblings, 0 replies; 23+ messages in thread
From: Yu-Chien Peter Lin @ 2026-07-29 16:39 UTC (permalink / raw)
To: devicetree, linux-riscv, linux-kernel
Cc: robh, krzk+dt, conor+dt, pjw, palmer, aou, alex, samuel.holland,
dlan, guodong, dfustini, michal.simek, junhui.liu,
darshan.prajapati, akpm, zhangchunyan, luxu.kernel, pincheng.plct,
nick.hu, jim.shu, zong.li, greentime.hu, robin.randhawa, scott,
dave.patel, raymond.mao, anup, pawandeep.oza, Yu-Chien Peter Lin
Add DT bindings for five RISC-V Worlds ISA extensions
that implement World ID tagging for hardware-enforced
context isolation. Also, add checks for extension
dependency requirements.
Signed-off-by: Yu-Chien Peter Lin <peter.lin@sifive.com>
---
.../devicetree/bindings/riscv/extensions.yaml | 53 +++++++++++++++++++
1 file changed, 53 insertions(+)
diff --git a/Documentation/devicetree/bindings/riscv/extensions.yaml b/Documentation/devicetree/bindings/riscv/extensions.yaml
index 2b0a8a93bb21..7a57191a0293 100644
--- a/Documentation/devicetree/bindings/riscv/extensions.yaml
+++ b/Documentation/devicetree/bindings/riscv/extensions.yaml
@@ -193,12 +193,35 @@ properties:
ratified at commit d70011dde6c2 ("Update to ratified state")
of riscv-j-extension.
+ - const: smlwid
+ description: |
+ The standard Smlwid extension for M-mode control of lower
+ privilege World ID via the mlwid CSR as ratified at commit
+ TBD ("TBD") of riscv-worlds.
+
+ - const: smlwidlist
+ description: |
+ The standard Smlwidlist extension for M-mode control of lower
+ privilege World IDs via the mlwidlist CSR as ratified at commit
+ TBD ("TBD") of riscv-worlds.
+
- const: smstateen
description: |
The standard Smstateen extension for controlling access to CSRs
added by other RISC-V extensions in H/S/VS/U/VU modes and as
ratified at commit a28bfae (Ratified (#7)) of riscv-state-enable.
+ - const: smwiddeleg
+ description: |
+ The standard Smwiddeleg extension for M-mode delegation of lower
+ privilege World ID control to S-mode via the mwiddeleg CSR, as
+ ratified at commit TBD ("TBD") of riscv-worlds.
+
+ - const: smwid
+ description: |
+ The standard Smwid extension for M-mode World ID control via the
+ mwid CSR as ratified at commit TBD ("TBD") of riscv-worlds.
+
- const: ssaia
description: |
The standard Ssaia supervisor-level extension for the advanced
@@ -262,6 +285,12 @@ properties:
ratified in RISC-V Profiles Version 1.0, with commit b1d806605f87
("Updated to ratified state.")
+ - const: sswid
+ description: |
+ The standard Sswid extension for S-mode control of lower
+ privilege World IDs via the slwid CSR as ratified at commit
+ TBD ("TBD") of riscv-worlds.
+
- const: supm
description: |
The standard Supm extension for pointer masking support in user
@@ -924,6 +953,30 @@ properties:
then:
contains:
const: b
+ # Smlwidlist depends on Smwid and Smlwid
+ - if:
+ contains:
+ const: smlwidlist
+ then:
+ allOf:
+ - contains:
+ const: smwid
+ - contains:
+ const: smlwid
+ # Smwiddeleg depends on Smlwid
+ - if:
+ contains:
+ const: smwiddeleg
+ then:
+ contains:
+ const: smlwid
+ # Sswid depends on Smwiddeleg
+ - if:
+ contains:
+ const: sswid
+ then:
+ contains:
+ const: smwiddeleg
# Supm depends on Smnpm or Ssnpm
- if:
contains:
--
2.43.7
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply related [flat|nested] 23+ messages in thread* [PATCH v2 1/3] dt-bindings: riscv: Add Worlds ISA extensions
@ 2026-07-29 16:39 ` Yu-Chien Peter Lin
0 siblings, 0 replies; 23+ messages in thread
From: Yu-Chien Peter Lin @ 2026-07-29 16:39 UTC (permalink / raw)
To: devicetree, linux-riscv, linux-kernel
Cc: robh, krzk+dt, conor+dt, pjw, palmer, aou, alex, samuel.holland,
dlan, guodong, dfustini, michal.simek, junhui.liu,
darshan.prajapati, akpm, zhangchunyan, luxu.kernel, pincheng.plct,
nick.hu, jim.shu, zong.li, greentime.hu, robin.randhawa, scott,
dave.patel, raymond.mao, anup, pawandeep.oza, Yu-Chien Peter Lin
Add DT bindings for five RISC-V Worlds ISA extensions
that implement World ID tagging for hardware-enforced
context isolation. Also, add checks for extension
dependency requirements.
Signed-off-by: Yu-Chien Peter Lin <peter.lin@sifive.com>
---
.../devicetree/bindings/riscv/extensions.yaml | 53 +++++++++++++++++++
1 file changed, 53 insertions(+)
diff --git a/Documentation/devicetree/bindings/riscv/extensions.yaml b/Documentation/devicetree/bindings/riscv/extensions.yaml
index 2b0a8a93bb21..7a57191a0293 100644
--- a/Documentation/devicetree/bindings/riscv/extensions.yaml
+++ b/Documentation/devicetree/bindings/riscv/extensions.yaml
@@ -193,12 +193,35 @@ properties:
ratified at commit d70011dde6c2 ("Update to ratified state")
of riscv-j-extension.
+ - const: smlwid
+ description: |
+ The standard Smlwid extension for M-mode control of lower
+ privilege World ID via the mlwid CSR as ratified at commit
+ TBD ("TBD") of riscv-worlds.
+
+ - const: smlwidlist
+ description: |
+ The standard Smlwidlist extension for M-mode control of lower
+ privilege World IDs via the mlwidlist CSR as ratified at commit
+ TBD ("TBD") of riscv-worlds.
+
- const: smstateen
description: |
The standard Smstateen extension for controlling access to CSRs
added by other RISC-V extensions in H/S/VS/U/VU modes and as
ratified at commit a28bfae (Ratified (#7)) of riscv-state-enable.
+ - const: smwiddeleg
+ description: |
+ The standard Smwiddeleg extension for M-mode delegation of lower
+ privilege World ID control to S-mode via the mwiddeleg CSR, as
+ ratified at commit TBD ("TBD") of riscv-worlds.
+
+ - const: smwid
+ description: |
+ The standard Smwid extension for M-mode World ID control via the
+ mwid CSR as ratified at commit TBD ("TBD") of riscv-worlds.
+
- const: ssaia
description: |
The standard Ssaia supervisor-level extension for the advanced
@@ -262,6 +285,12 @@ properties:
ratified in RISC-V Profiles Version 1.0, with commit b1d806605f87
("Updated to ratified state.")
+ - const: sswid
+ description: |
+ The standard Sswid extension for S-mode control of lower
+ privilege World IDs via the slwid CSR as ratified at commit
+ TBD ("TBD") of riscv-worlds.
+
- const: supm
description: |
The standard Supm extension for pointer masking support in user
@@ -924,6 +953,30 @@ properties:
then:
contains:
const: b
+ # Smlwidlist depends on Smwid and Smlwid
+ - if:
+ contains:
+ const: smlwidlist
+ then:
+ allOf:
+ - contains:
+ const: smwid
+ - contains:
+ const: smlwid
+ # Smwiddeleg depends on Smlwid
+ - if:
+ contains:
+ const: smwiddeleg
+ then:
+ contains:
+ const: smlwid
+ # Sswid depends on Smwiddeleg
+ - if:
+ contains:
+ const: sswid
+ then:
+ contains:
+ const: smwiddeleg
# Supm depends on Smnpm or Ssnpm
- if:
contains:
--
2.43.7
^ permalink raw reply related [flat|nested] 23+ messages in thread* Re: [PATCH v2 1/3] dt-bindings: riscv: Add Worlds ISA extensions
2026-07-29 16:39 ` Yu-Chien Peter Lin
(?)
@ 2026-07-29 16:45 ` sashiko-bot
-1 siblings, 0 replies; 23+ messages in thread
From: sashiko-bot @ 2026-07-29 16:45 UTC (permalink / raw)
To: Yu-Chien Peter Lin; +Cc: devicetree, robh, conor+dt
Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
- [Medium] S-mode extension 'sswid' imposes an invalid schema dependency on M-mode extension 'smwiddeleg', breaking guest VM device trees.
- [Medium] The patch contains 'TBD' placeholders for the ratification commit hashes of the newly added standard extensions.
- [Low] The newly added multi-letter extensions violate the strict alphanumeric sorting requirement.
--
--- Patch [1]: [PATCH v2 1/3] dt-bindings: riscv: Add Worlds ISA extensions ---
commit f77a112e3cec85c24b75fb71cd433146ac340c50
Author: Yu-Chien Peter Lin <peter.lin@sifive.com>
dt-bindings: riscv: Add Worlds ISA extensions
This commit adds device tree bindings for five RISC-V Worlds ISA extensions
that implement World ID tagging for hardware-enforced context isolation. It
also adds checks for extension dependency requirements.
> diff --git a/Documentation/devicetree/bindings/riscv/extensions.yaml b/Documentation/devicetree/bindings/riscv/extensions.yaml
> index 5ffc40d599c02..3fb13b860e701 100644
> --- a/Documentation/devicetree/bindings/riscv/extensions.yaml
> +++ b/Documentation/devicetree/bindings/riscv/extensions.yaml
> @@ -193,12 +193,35 @@ properties:
> ratified at commit d70011dde6c2 ("Update to ratified state")
> of riscv-j-extension.
>
> + - const: smlwid
> + description: |
> + The standard Smlwid extension for M-mode control of lower
> + privilege World ID via the mlwid CSR as ratified at commit
> + TBD ("TBD") of riscv-worlds.
[Severity: Medium]
Is this extension fully ratified?
The description still contains TBD for the ratification commit hashes here and
in the other extensions added by this patch.
Could you update the TBD placeholders with the actual commit hashes if the
extensions are complete?
> +
> + - const: smlwidlist
> + description: |
> + The standard Smlwidlist extension for M-mode control of lower
> + privilege World IDs via the mlwidlist CSR as ratified at commit
> + TBD ("TBD") of riscv-worlds.
> +
> - const: smstateen
> description: |
> The standard Smstateen extension for controlling access to CSRs
> added by other RISC-V extensions in H/S/VS/U/VU modes and as
> ratified at commit a28bfae (Ratified (#7)) of riscv-state-enable.
>
> + - const: smwiddeleg
> + description: |
> + The standard Smwiddeleg extension for M-mode delegation of lower
> + privilege World ID control to S-mode via the mwiddeleg CSR, as
> + ratified at commit TBD ("TBD") of riscv-worlds.
> +
> + - const: smwid
[Severity: Low]
Does this ordering violate the alphanumeric sorting requirement for
multi-letter extensions?
It appears smwiddeleg is placed before smwid, which is alphabetically
incorrect since smwid is a prefix and should come first.
Also, smlwid and smlwidlist appear to be inserted out of alphanumeric order
compared to the surrounding extensions.
[ ... ]
> @@ -924,6 +953,30 @@ properties:
[ ... ]
> + # Sswid depends on Smwiddeleg
> + - if:
> + contains:
> + const: sswid
> + then:
> + contains:
> + const: smwiddeleg
[Severity: Medium]
Could this strict dependency cause a regression for guest VM device trees?
This block requires the M-mode smwiddeleg extension to be present whenever
the S-mode sswid extension is declared. In RISC-V systems, hypervisors
typically only expose Supervisor and User mode extensions to guest VMs.
If a valid guest VM device tree contains sswid but omits M-mode capabilities
like smwiddeleg, wouldn't it falsely fail validation?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260729163908.249838-1-peter.lin@sifive.com?part=1
^ permalink raw reply [flat|nested] 23+ messages in thread
* [PATCH v2 2/3] dt-bindings: riscv: Add Worlds per-hart properties
2026-07-29 16:39 ` Yu-Chien Peter Lin
@ 2026-07-29 16:39 ` Yu-Chien Peter Lin
-1 siblings, 0 replies; 23+ messages in thread
From: Yu-Chien Peter Lin @ 2026-07-29 16:39 UTC (permalink / raw)
To: devicetree, linux-riscv, linux-kernel
Cc: robh, krzk+dt, conor+dt, pjw, palmer, aou, alex, samuel.holland,
dlan, guodong, dfustini, michal.simek, junhui.liu,
darshan.prajapati, akpm, zhangchunyan, luxu.kernel, pincheng.plct,
nick.hu, jim.shu, zong.li, greentime.hu, robin.randhawa, scott,
dave.patel, raymond.mao, anup, pawandeep.oza, Yu-Chien Peter Lin
Add per-hart DT properties for the RISC-V Worlds architecture:
riscv,pmwid, riscv,pmwidlist, and riscv,pmlwidlist. These
platform-defined values are primarily used by M-mode firmware
to configure World ID CSRs and restrict WID usage across
privilege levels.
Also add schema validation rules to enforce valid property
combinations based on the ISA extensions present.
Signed-off-by: Yu-Chien Peter Lin <peter.lin@sifive.com>
---
.../devicetree/bindings/riscv/cpus.yaml | 61 +++++++++++++++
.../devicetree/bindings/riscv/worlds.yaml | 77 +++++++++++++++++++
2 files changed, 138 insertions(+)
create mode 100644 Documentation/devicetree/bindings/riscv/worlds.yaml
diff --git a/Documentation/devicetree/bindings/riscv/cpus.yaml b/Documentation/devicetree/bindings/riscv/cpus.yaml
index 5feeb2203050..5922a0307cfe 100644
--- a/Documentation/devicetree/bindings/riscv/cpus.yaml
+++ b/Documentation/devicetree/bindings/riscv/cpus.yaml
@@ -26,6 +26,7 @@ description: |
allOf:
- $ref: /schemas/cpu.yaml#
- $ref: extensions.yaml
+ - $ref: worlds.yaml
- if:
not:
properties:
@@ -39,6 +40,44 @@ allOf:
properties:
thead,vlenb: false
+ - if:
+ properties:
+ riscv,isa-extensions:
+ not:
+ contains:
+ const: smwid
+ then:
+ properties:
+ riscv,pmwidlist: false
+
+ - if:
+ properties:
+ riscv,isa-extensions:
+ not:
+ contains:
+ const: smlwid
+ then:
+ properties:
+ riscv,pmlwidlist: false
+
+ - if:
+ allOf:
+ - properties:
+ riscv,isa-extensions:
+ not:
+ contains:
+ const: smwid
+ - properties:
+ riscv,isa-extensions:
+ contains:
+ enum:
+ - smlwid
+ - smwiddeleg
+ - sswid
+ then:
+ required:
+ - riscv,pmwid
+
properties:
compatible:
oneOf:
@@ -120,6 +159,28 @@ properties:
thead systems where the vector register length is not identical on all harts, or
the vlenb CSR is not available.
+ riscv,pmwid:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description:
+ M-mode World ID (WID) for this hart, M-mode firmware may read this property
+ to identify the WID for M-mode. For a Worlds-aware platform without any Worlds
+ ISA implemented, this is the WID for all privilege modes.
+ minimum: 0
+ maximum: 63
+
+ riscv,pmwidlist:
+ $ref: /schemas/types.yaml#/definitions/uint64
+ description:
+ Optional bitmask of WIDs available for M-mode use on this hart; each set bit N
+ indicates WID N is available. Firmware may read this to select a platform
+ authorized WID.
+
+ riscv,pmlwidlist:
+ $ref: /schemas/types.yaml#/definitions/uint64
+ description:
+ Optional bitmask of WIDs available for S-mode and U-mode use on this hart; each
+ set bit N indicates WID N is available. Firmware may read this to select platform
+ authorized WIDs for lower-privilege modes.
# RISC-V has multiple properties for cache op block sizes as the sizes
# differ between individual CBO extensions
cache-op-block-size: false
diff --git a/Documentation/devicetree/bindings/riscv/worlds.yaml b/Documentation/devicetree/bindings/riscv/worlds.yaml
new file mode 100644
index 000000000000..cc8b3747591e
--- /dev/null
+++ b/Documentation/devicetree/bindings/riscv/worlds.yaml
@@ -0,0 +1,77 @@
+# SPDX-License-Identifier: (GPL-2.0 OR MIT)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/riscv/worlds.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: RISC-V Worlds Extension
+
+maintainers:
+ - Yu-Chien Peter Lin <peter.lin@sifive.com>
+
+description: |
+ The RISC-V Worlds ISA extension, as described in the RISC-V Privileged
+ Specification, adds World ID tagging for context isolation.
+
+ This binding describes the system-wide Worlds configuration for the /cpus node
+ and is used alongside per-hart Worlds-related properties such as riscv,pmwid in
+ the RISC-V CPU binding and Worlds-related ISA extensions enumerated via
+ riscv,isa-extensions.
+
+select:
+ properties:
+ $nodename:
+ pattern: "^cpus$"
+
+properties:
+ riscv,nworlds:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description: |
+ Number of World IDs (WIDs) supported by the platform. This is a system-wide
+ property that describes the total number of isolation contexts available.
+ Hardware components such as the WorldGuard Checker use this to determine
+ the valid range of WID values.
+ minimum: 2
+ maximum: 64
+
+additionalProperties: true
+
+examples:
+ - |
+ // Example: System with 4 World IDs
+ cpus {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ timebase-frequency = <1000000>;
+ riscv,nworlds = <4>;
+
+ cpu@0 {
+ device_type = "cpu";
+ reg = <0>;
+ compatible = "sifive,bullet0", "riscv";
+ riscv,isa-base = "rv64i";
+ riscv,isa-extensions = "i", "m", "a", "f", "d", "c";
+ riscv,pmwid = <0>;
+
+ interrupt-controller {
+ #interrupt-cells = <1>;
+ compatible = "riscv,cpu-intc";
+ interrupt-controller;
+ };
+ };
+
+ cpu@1 {
+ device_type = "cpu";
+ reg = <1>;
+ compatible = "sifive,bullet0", "riscv";
+ riscv,isa-base = "rv64i";
+ riscv,isa-extensions = "i", "m", "a", "f", "d", "c";
+ riscv,pmwid = <1>;
+
+ interrupt-controller {
+ #interrupt-cells = <1>;
+ compatible = "riscv,cpu-intc";
+ interrupt-controller;
+ };
+ };
+ };
--
2.43.7
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply related [flat|nested] 23+ messages in thread* [PATCH v2 2/3] dt-bindings: riscv: Add Worlds per-hart properties
@ 2026-07-29 16:39 ` Yu-Chien Peter Lin
0 siblings, 0 replies; 23+ messages in thread
From: Yu-Chien Peter Lin @ 2026-07-29 16:39 UTC (permalink / raw)
To: devicetree, linux-riscv, linux-kernel
Cc: robh, krzk+dt, conor+dt, pjw, palmer, aou, alex, samuel.holland,
dlan, guodong, dfustini, michal.simek, junhui.liu,
darshan.prajapati, akpm, zhangchunyan, luxu.kernel, pincheng.plct,
nick.hu, jim.shu, zong.li, greentime.hu, robin.randhawa, scott,
dave.patel, raymond.mao, anup, pawandeep.oza, Yu-Chien Peter Lin
Add per-hart DT properties for the RISC-V Worlds architecture:
riscv,pmwid, riscv,pmwidlist, and riscv,pmlwidlist. These
platform-defined values are primarily used by M-mode firmware
to configure World ID CSRs and restrict WID usage across
privilege levels.
Also add schema validation rules to enforce valid property
combinations based on the ISA extensions present.
Signed-off-by: Yu-Chien Peter Lin <peter.lin@sifive.com>
---
.../devicetree/bindings/riscv/cpus.yaml | 61 +++++++++++++++
.../devicetree/bindings/riscv/worlds.yaml | 77 +++++++++++++++++++
2 files changed, 138 insertions(+)
create mode 100644 Documentation/devicetree/bindings/riscv/worlds.yaml
diff --git a/Documentation/devicetree/bindings/riscv/cpus.yaml b/Documentation/devicetree/bindings/riscv/cpus.yaml
index 5feeb2203050..5922a0307cfe 100644
--- a/Documentation/devicetree/bindings/riscv/cpus.yaml
+++ b/Documentation/devicetree/bindings/riscv/cpus.yaml
@@ -26,6 +26,7 @@ description: |
allOf:
- $ref: /schemas/cpu.yaml#
- $ref: extensions.yaml
+ - $ref: worlds.yaml
- if:
not:
properties:
@@ -39,6 +40,44 @@ allOf:
properties:
thead,vlenb: false
+ - if:
+ properties:
+ riscv,isa-extensions:
+ not:
+ contains:
+ const: smwid
+ then:
+ properties:
+ riscv,pmwidlist: false
+
+ - if:
+ properties:
+ riscv,isa-extensions:
+ not:
+ contains:
+ const: smlwid
+ then:
+ properties:
+ riscv,pmlwidlist: false
+
+ - if:
+ allOf:
+ - properties:
+ riscv,isa-extensions:
+ not:
+ contains:
+ const: smwid
+ - properties:
+ riscv,isa-extensions:
+ contains:
+ enum:
+ - smlwid
+ - smwiddeleg
+ - sswid
+ then:
+ required:
+ - riscv,pmwid
+
properties:
compatible:
oneOf:
@@ -120,6 +159,28 @@ properties:
thead systems where the vector register length is not identical on all harts, or
the vlenb CSR is not available.
+ riscv,pmwid:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description:
+ M-mode World ID (WID) for this hart, M-mode firmware may read this property
+ to identify the WID for M-mode. For a Worlds-aware platform without any Worlds
+ ISA implemented, this is the WID for all privilege modes.
+ minimum: 0
+ maximum: 63
+
+ riscv,pmwidlist:
+ $ref: /schemas/types.yaml#/definitions/uint64
+ description:
+ Optional bitmask of WIDs available for M-mode use on this hart; each set bit N
+ indicates WID N is available. Firmware may read this to select a platform
+ authorized WID.
+
+ riscv,pmlwidlist:
+ $ref: /schemas/types.yaml#/definitions/uint64
+ description:
+ Optional bitmask of WIDs available for S-mode and U-mode use on this hart; each
+ set bit N indicates WID N is available. Firmware may read this to select platform
+ authorized WIDs for lower-privilege modes.
# RISC-V has multiple properties for cache op block sizes as the sizes
# differ between individual CBO extensions
cache-op-block-size: false
diff --git a/Documentation/devicetree/bindings/riscv/worlds.yaml b/Documentation/devicetree/bindings/riscv/worlds.yaml
new file mode 100644
index 000000000000..cc8b3747591e
--- /dev/null
+++ b/Documentation/devicetree/bindings/riscv/worlds.yaml
@@ -0,0 +1,77 @@
+# SPDX-License-Identifier: (GPL-2.0 OR MIT)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/riscv/worlds.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: RISC-V Worlds Extension
+
+maintainers:
+ - Yu-Chien Peter Lin <peter.lin@sifive.com>
+
+description: |
+ The RISC-V Worlds ISA extension, as described in the RISC-V Privileged
+ Specification, adds World ID tagging for context isolation.
+
+ This binding describes the system-wide Worlds configuration for the /cpus node
+ and is used alongside per-hart Worlds-related properties such as riscv,pmwid in
+ the RISC-V CPU binding and Worlds-related ISA extensions enumerated via
+ riscv,isa-extensions.
+
+select:
+ properties:
+ $nodename:
+ pattern: "^cpus$"
+
+properties:
+ riscv,nworlds:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description: |
+ Number of World IDs (WIDs) supported by the platform. This is a system-wide
+ property that describes the total number of isolation contexts available.
+ Hardware components such as the WorldGuard Checker use this to determine
+ the valid range of WID values.
+ minimum: 2
+ maximum: 64
+
+additionalProperties: true
+
+examples:
+ - |
+ // Example: System with 4 World IDs
+ cpus {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ timebase-frequency = <1000000>;
+ riscv,nworlds = <4>;
+
+ cpu@0 {
+ device_type = "cpu";
+ reg = <0>;
+ compatible = "sifive,bullet0", "riscv";
+ riscv,isa-base = "rv64i";
+ riscv,isa-extensions = "i", "m", "a", "f", "d", "c";
+ riscv,pmwid = <0>;
+
+ interrupt-controller {
+ #interrupt-cells = <1>;
+ compatible = "riscv,cpu-intc";
+ interrupt-controller;
+ };
+ };
+
+ cpu@1 {
+ device_type = "cpu";
+ reg = <1>;
+ compatible = "sifive,bullet0", "riscv";
+ riscv,isa-base = "rv64i";
+ riscv,isa-extensions = "i", "m", "a", "f", "d", "c";
+ riscv,pmwid = <1>;
+
+ interrupt-controller {
+ #interrupt-cells = <1>;
+ compatible = "riscv,cpu-intc";
+ interrupt-controller;
+ };
+ };
+ };
--
2.43.7
^ permalink raw reply related [flat|nested] 23+ messages in thread* Re: [PATCH v2 2/3] dt-bindings: riscv: Add Worlds per-hart properties
2026-07-29 16:39 ` Yu-Chien Peter Lin
(?)
@ 2026-07-29 16:52 ` sashiko-bot
-1 siblings, 0 replies; 23+ messages in thread
From: sashiko-bot @ 2026-07-29 16:52 UTC (permalink / raw)
To: Yu-Chien Peter Lin; +Cc: devicetree, conor+dt, robh
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] The CPU node schema incorrectly references the system-wide Worlds schema, bypassing strict property validation for all CPU nodes.
- [High] The schema incorrectly requires the `riscv,pmwid` property on legacy devicetrees that lack the `riscv,isa-extensions` property.
--
--- Patch [2]: [PATCH v2 2/3] dt-bindings: riscv: Add Worlds per-hart properties ---
commit 8c65780e5330e56c6e5f7b6479ae772aa1d15f0c
Author: Yu-Chien Peter Lin <peter.lin@sifive.com>
dt-bindings: riscv: Add Worlds per-hart properties
This commit adds device tree properties to describe the RISC-V Worlds
architecture. It introduces system-wide and per-hart configuration
properties for World IDs, along with schema validation rules.
> diff --git a/Documentation/devicetree/bindings/riscv/cpus.yaml b/Documentation/devicetree/bindings/riscv/cpus.yaml
> index 5feeb2203050a..5922a0307cfe0 100644
> --- a/Documentation/devicetree/bindings/riscv/cpus.yaml
> +++ b/Documentation/devicetree/bindings/riscv/cpus.yaml
> @@ -26,6 +26,7 @@ description: |
> allOf:
> - $ref: /schemas/cpu.yaml#
> - $ref: extensions.yaml
> + - $ref: worlds.yaml
[Severity: High]
Does this inclusion break the strict property validation for all CPU nodes?
Because worlds.yaml includes additionalProperties: true, JSON schema
validation will treat all properties as successfully evaluated.
This neutralizes the unevaluatedProperties: false restriction in cpus.yaml,
allowing undocumented or typo'd properties to silently pass validation.
[ ... ]
> + - if:
> + allOf:
> + - properties:
> + riscv,isa-extensions:
> + not:
> + contains:
> + const: smwid
> + - properties:
> + riscv,isa-extensions:
> + contains:
> + enum:
> + - smlwid
> + - smwiddeleg
> + - sswid
> + then:
> + required:
> + - riscv,pmwid
[Severity: High]
Will this erroneously require riscv,pmwid on legacy devicetrees that lack
the riscv,isa-extensions property?
In JSON Schema, a properties check automatically succeeds if the specified
property is absent.
Without an explicit check requiring riscv,isa-extensions to be present, this
conditional evaluates to true when the property is missing. This breaks
backward compatibility with older valid devicetrees that use the deprecated
riscv,isa property.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260729163908.249838-1-peter.lin@sifive.com?part=2
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [PATCH v2 2/3] dt-bindings: riscv: Add Worlds per-hart properties
2026-07-29 16:39 ` Yu-Chien Peter Lin
@ 2026-07-29 18:06 ` Rob Herring (Arm)
-1 siblings, 0 replies; 23+ messages in thread
From: Rob Herring (Arm) @ 2026-07-29 18:06 UTC (permalink / raw)
To: Yu-Chien Peter Lin
Cc: anup, guodong, pincheng.plct, alex, aou, linux-kernel, devicetree,
michal.simek, dave.patel, pjw, linux-riscv, zhangchunyan,
raymond.mao, palmer, greentime.hu, dfustini, luxu.kernel,
conor+dt, akpm, scott, jim.shu, krzk+dt, robin.randhawa, zong.li,
pawandeep.oza, nick.hu, samuel.holland, darshan.prajapati,
junhui.liu, dlan
On Thu, 30 Jul 2026 00:39:07 +0800, Yu-Chien Peter Lin wrote:
> Add per-hart DT properties for the RISC-V Worlds architecture:
> riscv,pmwid, riscv,pmwidlist, and riscv,pmlwidlist. These
> platform-defined values are primarily used by M-mode firmware
> to configure World ID CSRs and restrict WID usage across
> privilege levels.
>
> Also add schema validation rules to enforce valid property
> combinations based on the ISA extensions present.
>
> Signed-off-by: Yu-Chien Peter Lin <peter.lin@sifive.com>
> ---
> .../devicetree/bindings/riscv/cpus.yaml | 61 +++++++++++++++
> .../devicetree/bindings/riscv/worlds.yaml | 77 +++++++++++++++++++
> 2 files changed, 138 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/riscv/worlds.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
Documentation/devicetree/bindings/cpu/idle-states.example.dtb: cpu@0 (riscv): 'riscv,pmwid' is a required property
from schema $id: http://devicetree.org/schemas/riscv/cpus.yaml
Documentation/devicetree/bindings/cpu/idle-states.example.dtb: cpu@1 (riscv): 'riscv,pmwid' is a required property
from schema $id: http://devicetree.org/schemas/riscv/cpus.yaml
Documentation/devicetree/bindings/cpu/idle-states.example.dtb: cpu@10 (riscv): 'riscv,pmwid' is a required property
from schema $id: http://devicetree.org/schemas/riscv/cpus.yaml
Documentation/devicetree/bindings/cpu/idle-states.example.dtb: cpu@11 (riscv): 'riscv,pmwid' is a required property
from schema $id: http://devicetree.org/schemas/riscv/cpus.yaml
doc reference errors (make refcheckdocs):
See https://patchwork.kernel.org/project/devicetree/patch/20260729163908.249838-3-peter.lin@sifive.com
The base for the series is generally the latest rc1. A different dependency
should be noted in *this* patch.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit after running the above command yourself. Note
that DT_SCHEMA_FILES can be set to your schema file to speed up checking
your schema. However, it must be unset to test all examples with your schema.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [PATCH v2 2/3] dt-bindings: riscv: Add Worlds per-hart properties
@ 2026-07-29 18:06 ` Rob Herring (Arm)
0 siblings, 0 replies; 23+ messages in thread
From: Rob Herring (Arm) @ 2026-07-29 18:06 UTC (permalink / raw)
To: Yu-Chien Peter Lin
Cc: anup, guodong, pincheng.plct, alex, aou, linux-kernel, devicetree,
michal.simek, dave.patel, pjw, linux-riscv, zhangchunyan,
raymond.mao, palmer, greentime.hu, dfustini, luxu.kernel,
conor+dt, akpm, scott, jim.shu, krzk+dt, robin.randhawa, zong.li,
pawandeep.oza, nick.hu, samuel.holland, darshan.prajapati,
junhui.liu, dlan
On Thu, 30 Jul 2026 00:39:07 +0800, Yu-Chien Peter Lin wrote:
> Add per-hart DT properties for the RISC-V Worlds architecture:
> riscv,pmwid, riscv,pmwidlist, and riscv,pmlwidlist. These
> platform-defined values are primarily used by M-mode firmware
> to configure World ID CSRs and restrict WID usage across
> privilege levels.
>
> Also add schema validation rules to enforce valid property
> combinations based on the ISA extensions present.
>
> Signed-off-by: Yu-Chien Peter Lin <peter.lin@sifive.com>
> ---
> .../devicetree/bindings/riscv/cpus.yaml | 61 +++++++++++++++
> .../devicetree/bindings/riscv/worlds.yaml | 77 +++++++++++++++++++
> 2 files changed, 138 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/riscv/worlds.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
Documentation/devicetree/bindings/cpu/idle-states.example.dtb: cpu@0 (riscv): 'riscv,pmwid' is a required property
from schema $id: http://devicetree.org/schemas/riscv/cpus.yaml
Documentation/devicetree/bindings/cpu/idle-states.example.dtb: cpu@1 (riscv): 'riscv,pmwid' is a required property
from schema $id: http://devicetree.org/schemas/riscv/cpus.yaml
Documentation/devicetree/bindings/cpu/idle-states.example.dtb: cpu@10 (riscv): 'riscv,pmwid' is a required property
from schema $id: http://devicetree.org/schemas/riscv/cpus.yaml
Documentation/devicetree/bindings/cpu/idle-states.example.dtb: cpu@11 (riscv): 'riscv,pmwid' is a required property
from schema $id: http://devicetree.org/schemas/riscv/cpus.yaml
doc reference errors (make refcheckdocs):
See https://patchwork.kernel.org/project/devicetree/patch/20260729163908.249838-3-peter.lin@sifive.com
The base for the series is generally the latest rc1. A different dependency
should be noted in *this* patch.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit after running the above command yourself. Note
that DT_SCHEMA_FILES can be set to your schema file to speed up checking
your schema. However, it must be unset to test all examples with your schema.
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [PATCH v2 2/3] dt-bindings: riscv: Add Worlds per-hart properties
2026-07-29 16:39 ` Yu-Chien Peter Lin
@ 2026-07-30 7:30 ` Krzysztof Kozlowski
-1 siblings, 0 replies; 23+ messages in thread
From: Krzysztof Kozlowski @ 2026-07-30 7:30 UTC (permalink / raw)
To: Yu-Chien Peter Lin
Cc: devicetree, linux-riscv, linux-kernel, robh, krzk+dt, conor+dt,
pjw, palmer, aou, alex, samuel.holland, dlan, guodong, dfustini,
michal.simek, junhui.liu, darshan.prajapati, akpm, zhangchunyan,
luxu.kernel, pincheng.plct, nick.hu, jim.shu, zong.li,
greentime.hu, robin.randhawa, scott, dave.patel, raymond.mao,
anup, pawandeep.oza
On Thu, Jul 30, 2026 at 12:39:07AM +0800, Yu-Chien Peter Lin wrote:
> + riscv,pmlwidlist:
> + $ref: /schemas/types.yaml#/definitions/uint64
> + description:
> + Optional bitmask of WIDs available for S-mode and U-mode use on this hart; each
> + set bit N indicates WID N is available. Firmware may read this to select platform
> + authorized WIDs for lower-privilege modes.
> # RISC-V has multiple properties for cache op block sizes as the sizes
> # differ between individual CBO extensions
> cache-op-block-size: false
> diff --git a/Documentation/devicetree/bindings/riscv/worlds.yaml b/Documentation/devicetree/bindings/riscv/worlds.yaml
> new file mode 100644
> index 000000000000..cc8b3747591e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/riscv/worlds.yaml
Please run scripts/checkpatch.pl on the patches and fix reported
warnings. After that, run also 'scripts/checkpatch.pl --strict' on the
patches and (probably) fix more warnings. Some warnings can be ignored,
especially from --strict run, but the code here looks like it needs a
fix. Feel free to get in touch if the warning is not clear.
> @@ -0,0 +1,77 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR MIT)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/riscv/worlds.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: RISC-V Worlds Extension
> +
> +maintainers:
> + - Yu-Chien Peter Lin <peter.lin@sifive.com>
> +
> +description: |
> + The RISC-V Worlds ISA extension, as described in the RISC-V Privileged
> + Specification, adds World ID tagging for context isolation.
> +
> + This binding describes the system-wide Worlds configuration for the /cpus node
> + and is used alongside per-hart Worlds-related properties such as riscv,pmwid in
> + the RISC-V CPU binding and Worlds-related ISA extensions enumerated via
> + riscv,isa-extensions.
> +
> +select:
> + properties:
> + $nodename:
> + pattern: "^cpus$"
> +
> +properties:
> + riscv,nworlds:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: |
> + Number of World IDs (WIDs) supported by the platform. This is a system-wide
> + property that describes the total number of isolation contexts available.
> + Hardware components such as the WorldGuard Checker use this to determine
> + the valid range of WID values.
Does not look like property of CPUs, but the "WorldGuard Checker" device
node.
Anyway, SoC compatible defines this. Don't add redundant properties.
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [PATCH v2 2/3] dt-bindings: riscv: Add Worlds per-hart properties
@ 2026-07-30 7:30 ` Krzysztof Kozlowski
0 siblings, 0 replies; 23+ messages in thread
From: Krzysztof Kozlowski @ 2026-07-30 7:30 UTC (permalink / raw)
To: Yu-Chien Peter Lin
Cc: devicetree, linux-riscv, linux-kernel, robh, krzk+dt, conor+dt,
pjw, palmer, aou, alex, samuel.holland, dlan, guodong, dfustini,
michal.simek, junhui.liu, darshan.prajapati, akpm, zhangchunyan,
luxu.kernel, pincheng.plct, nick.hu, jim.shu, zong.li,
greentime.hu, robin.randhawa, scott, dave.patel, raymond.mao,
anup, pawandeep.oza
On Thu, Jul 30, 2026 at 12:39:07AM +0800, Yu-Chien Peter Lin wrote:
> + riscv,pmlwidlist:
> + $ref: /schemas/types.yaml#/definitions/uint64
> + description:
> + Optional bitmask of WIDs available for S-mode and U-mode use on this hart; each
> + set bit N indicates WID N is available. Firmware may read this to select platform
> + authorized WIDs for lower-privilege modes.
> # RISC-V has multiple properties for cache op block sizes as the sizes
> # differ between individual CBO extensions
> cache-op-block-size: false
> diff --git a/Documentation/devicetree/bindings/riscv/worlds.yaml b/Documentation/devicetree/bindings/riscv/worlds.yaml
> new file mode 100644
> index 000000000000..cc8b3747591e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/riscv/worlds.yaml
Please run scripts/checkpatch.pl on the patches and fix reported
warnings. After that, run also 'scripts/checkpatch.pl --strict' on the
patches and (probably) fix more warnings. Some warnings can be ignored,
especially from --strict run, but the code here looks like it needs a
fix. Feel free to get in touch if the warning is not clear.
> @@ -0,0 +1,77 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR MIT)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/riscv/worlds.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: RISC-V Worlds Extension
> +
> +maintainers:
> + - Yu-Chien Peter Lin <peter.lin@sifive.com>
> +
> +description: |
> + The RISC-V Worlds ISA extension, as described in the RISC-V Privileged
> + Specification, adds World ID tagging for context isolation.
> +
> + This binding describes the system-wide Worlds configuration for the /cpus node
> + and is used alongside per-hart Worlds-related properties such as riscv,pmwid in
> + the RISC-V CPU binding and Worlds-related ISA extensions enumerated via
> + riscv,isa-extensions.
> +
> +select:
> + properties:
> + $nodename:
> + pattern: "^cpus$"
> +
> +properties:
> + riscv,nworlds:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: |
> + Number of World IDs (WIDs) supported by the platform. This is a system-wide
> + property that describes the total number of isolation contexts available.
> + Hardware components such as the WorldGuard Checker use this to determine
> + the valid range of WID values.
Does not look like property of CPUs, but the "WorldGuard Checker" device
node.
Anyway, SoC compatible defines this. Don't add redundant properties.
Best regards,
Krzysztof
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 23+ messages in thread
* [PATCH v2 3/3] dt-bindings: sifive: Add WorldGuard Checker
2026-07-29 16:39 ` Yu-Chien Peter Lin
@ 2026-07-29 16:39 ` Yu-Chien Peter Lin
-1 siblings, 0 replies; 23+ messages in thread
From: Yu-Chien Peter Lin @ 2026-07-29 16:39 UTC (permalink / raw)
To: devicetree, linux-riscv, linux-kernel
Cc: robh, krzk+dt, conor+dt, pjw, palmer, aou, alex, samuel.holland,
dlan, guodong, dfustini, michal.simek, junhui.liu,
darshan.prajapati, akpm, zhangchunyan, luxu.kernel, pincheng.plct,
nick.hu, jim.shu, zong.li, greentime.hu, robin.randhawa, scott,
dave.patel, raymond.mao, anup, pawandeep.oza, Yu-Chien Peter Lin
Add YAML binding schema for the SiFive wgChecker, a programmable
access controller integrated in the interconnect fabric of RISC-V
Worlds-capable SoCs.
wgChecker enforces World ID (WID) based access control on downstream
bus transactions. Each checker slot encodes a 2-bit permission field
per WID (read/write), enabling fine-grained memory partitioning and
device isolation between execution contexts. Violations are reported
via bus errors, interrupts, or both, selectable and lockable per slot.
The binding registers wgChecker as an access-controllers provider.
Consumers (i.e. its protected device) reference it via the standard
access-controllers phandle to declare their access requirements.
Also document the sifive,trustedwid property for the /cpus node,
identifying the privileged WID authorized to configure all checkers
on the platform.
Link: https://github.com/riscvarchive/security/blob/main/papers/worldguard%20proposal.pdf
Signed-off-by: Yu-Chien Peter Lin <peter.lin@sifive.com>
Reviewed-by: Zong Li <zong.li@sifive.com>
Reviewed-by: Jim Shu <jim.shu@sifive.com>
---
.../devicetree/bindings/riscv/worlds.yaml | 9 +
.../bindings/sifive/sifive,wgchecker2.yaml | 356 ++++++++++++++++++
2 files changed, 365 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
diff --git a/Documentation/devicetree/bindings/riscv/worlds.yaml b/Documentation/devicetree/bindings/riscv/worlds.yaml
index cc8b3747591e..c39a06c2dd8d 100644
--- a/Documentation/devicetree/bindings/riscv/worlds.yaml
+++ b/Documentation/devicetree/bindings/riscv/worlds.yaml
@@ -34,6 +34,14 @@ properties:
minimum: 2
maximum: 64
+ sifive,trustedwid:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ maximum: 31
+ description: |
+ The World ID (WID) designated as the trusted WID for this platform.
+ Transactions tagged with this WID are authorized to access and configure
+ WorldGuard blocks, including wgCheckers and wgMarkers.
+
additionalProperties: true
examples:
@@ -44,6 +52,7 @@ examples:
#size-cells = <0>;
timebase-frequency = <1000000>;
riscv,nworlds = <4>;
+ sifive,trustedwid = <3>;
cpu@0 {
device_type = "cpu";
diff --git a/Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml b/Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
new file mode 100644
index 000000000000..c025a4765cb3
--- /dev/null
+++ b/Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
@@ -0,0 +1,356 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+# Copyright (C) 2026 SiFive, Inc.
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/sifive/sifive,wgchecker2.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: SiFive WorldGuard Checker
+
+maintainers:
+ - Yu-Chien Peter Lin <peter.lin@sifive.com>
+
+description: |
+ The RISC-V Worlds ISA extension defines World IDs (WIDs) as architectural
+ identifiers that tag each system transaction with its originating context.
+ System integrators assign WIDs to execution contexts such as privilege modes,
+ trusted execution environments, or other isolation boundaries.
+
+ The SiFive WorldGuard Checker is a hardware firewall positioned in the
+ system interconnect fabric. It inspects every transaction, evaluating the
+ WID against access control policies encoded in checker slots for each
+ protected resource. Transactions from unauthorized WIDs are blocked and
+ reported as bus errors, interrupts, or both.
+
+ This enables spatial partitioning of memory regions and memory-mapped devices
+ across execution contexts. Different address ranges can enforce distinct
+ policies, allowing isolated workloads to coexist with hardware-enforced
+ protection.
+
+ The wgChecker acts as an access-controller provider as defined in the
+ access-controllers framework. Protected devices are consumers that declare
+ their access policy via the access-controllers property. The hardware
+ supports up to 32 World IDs.
+
+ The World ID authorized to configure WorldGuard blocks is specified by the
+ sifive,trustedwid property in the /cpus node.
+
+allOf:
+ - $ref: /schemas/access-controllers/access-controllers.yaml#
+
+properties:
+ compatible:
+ oneOf:
+ - items:
+ - const: qemu,wgchecker2
+ - const: sifive,wgchecker2
+ - const: sifive,wgchecker2
+
+ reg:
+ maxItems: 1
+ description:
+ Base address and size of the wgChecker memory-mapped I/O registers.
+
+ interrupts:
+ maxItems: 1
+ description:
+ Interrupt line asserted when a WID access violation is detected and
+ interrupt reporting is enabled in the slot configuration (IR or IW
+ bits set).
+
+ '#access-controller-cells':
+ const: 1
+ description: |
+ Specifies the partition identifier to reference a partition child
+ node that defines the access control region, WID permissions, and
+ access failure configuration. The special ID 0xFFFFFFFF indicates
+ unprotected mode, granting unrestricted access to the device.
+
+ '#address-cells':
+ const: 1
+
+ '#size-cells':
+ const: 0
+
+patternProperties:
+ "^partition@[0-9a-f]+$":
+ type: object
+ additionalProperties: false
+
+ properties:
+ reg:
+ maximum: 0xFFFFFFFE
+ description:
+ Partition identifier. Must be unique within the wgChecker node.
+ The value 0xFFFFFFFF is reserved for unprotected mode and must
+ not be used.
+
+ sifive,protected-region:
+ $ref: /schemas/types.yaml#/definitions/uint32-array
+ description:
+ Protected memory region encoded as a base address and size.
+ items:
+ - description: Upper 32 bits of the base address
+ - description: Lower 32 bits of the base address
+ - description: Upper 32 bits of the region size
+ - description: Lower 32 bits of the region size
+
+ sifive,slot-permissions:
+ $ref: /schemas/types.yaml#/definitions/uint64
+ description: |
+ 64-bit WID permission bitmap. Each WID N uses two consecutive bits:
+ - bit[2*N] : Read permission for WID N
+ - bit[2*N+1]: Write permission for WID N
+ Set bits grant access.
+
+ sifive,slot-config:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ maximum: 0x1F
+ description: |
+ Access failure configuration flags for this slot:
+ bit[0] (ER): report read violations as bus errors
+ bit[1] (EW): report write violations as bus errors
+ bit[2] (IR): report read violations via interrupt
+ bit[3] (IW): report write violations via interrupt
+ bit[4] (L) : lock this slot against further modification
+ Bits[5:31] are reserved and must be zero.
+
+ required:
+ - reg
+ - sifive,protected-region
+ - sifive,slot-permissions
+ - sifive,slot-config
+
+required:
+ - compatible
+ - reg
+ - '#address-cells'
+ - '#size-cells'
+ - '#access-controller-cells'
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/interrupt-controller/irq.h>
+
+ // Example 1: Peripheral device protection
+
+ cpus {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ timebase-frequency = <1000000>;
+ riscv,nworlds = <4>;
+ sifive,trustedwid = <3>;
+
+ cpu@0 {
+ device_type = "cpu";
+ reg = <0>;
+ compatible = "riscv";
+ riscv,isa-base = "rv64i";
+ riscv,isa-extensions = "i", "m", "a", "c", "smlwid";
+ riscv,pmwid = <3>;
+
+ cpu_intc0: interrupt-controller {
+ #interrupt-cells = <1>;
+ compatible = "riscv,cpu-intc";
+ interrupt-controller;
+ };
+ };
+ };
+
+ soc {
+ #address-cells = <2>;
+ #size-cells = <2>;
+
+ uart: uart@1c1000 {
+ compatible = "ns16550a";
+ reg = <0x0 0x001c1000 0x0 0x1000>;
+ reg-names = "control";
+ interrupts = <10 IRQ_TYPE_LEVEL_HIGH>;
+ access-controllers = <&wgchecker0 0>;
+ };
+
+ wgchecker0: access-controller@1c2000 {
+ compatible = "qemu,wgchecker2", "sifive,wgchecker2";
+ reg = <0x0 0x001c2000 0x0 0x1000>;
+ #access-controller-cells = <1>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ interrupts = <80 IRQ_TYPE_LEVEL_HIGH>;
+ interrupt-parent = <&aplic0_m>;
+
+ partition@0 {
+ reg = <0>;
+ sifive,protected-region = <0x0 0x001c1000 0x0 0x00001000>;
+ sifive,slot-permissions = <0x0 0x000000c3>;
+ sifive,slot-config = <0x0f>;
+ };
+ };
+
+ aplic0_m: interrupt-controller@c000000 {
+ compatible = "qemu,aplic", "riscv,aplic";
+ reg = <0x0 0xc000000 0x0 0x4000>;
+ interrupt-controller;
+ #interrupt-cells = <2>;
+ riscv,num-sources = <96>;
+ interrupts-extended = <&cpu_intc0 11>;
+ };
+ };
+
+ - |
+ #include <dt-bindings/interrupt-controller/irq.h>
+
+ // Example 2: Device with multiple address regions and per-region access rules
+
+ cpus {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ timebase-frequency = <1000000>;
+ riscv,nworlds = <16>;
+ sifive,trustedwid = <3>;
+
+ cpu@0 {
+ device_type = "cpu";
+ reg = <0>;
+ compatible = "riscv";
+ riscv,isa-base = "rv64i";
+ riscv,isa-extensions = "i", "m", "a", "c", "smlwid";
+ riscv,pmwid = <3>;
+
+ cpu_intc1: interrupt-controller {
+ #interrupt-cells = <1>;
+ compatible = "riscv,cpu-intc";
+ interrupt-controller;
+ };
+ };
+ };
+
+ soc {
+ #address-cells = <2>;
+ #size-cells = <2>;
+
+ device: device@10000 {
+ compatible = "vendor,soc1-ip";
+ reg = <0x0 0x00010000 0x0 0x8000>,
+ <0x0 0x00a00000 0x0 0x4000>;
+ reg-names = "m_mode", "s_mode";
+ // m_mode: WID 3 only; s_mode: WID 0,3 RW
+ access-controllers = <&wgchecker1 0>,
+ <&wgchecker1 1>;
+ };
+
+ wgchecker1: access-controller@35000 {
+ compatible = "qemu,wgchecker2", "sifive,wgchecker2";
+ reg = <0x0 0x00035000 0x0 0x1000>;
+ #access-controller-cells = <1>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ interrupts = <81 IRQ_TYPE_LEVEL_HIGH>;
+ interrupt-parent = <&aplic1_m>;
+
+ partition@0 {
+ reg = <0>;
+ sifive,protected-region = <0x0 0x00010000 0x0 0x00008000>;
+ sifive,slot-permissions = <0x0 0x000000c0>;
+ sifive,slot-config = <0x0f>;
+ };
+
+ partition@1 {
+ reg = <1>;
+ sifive,protected-region = <0x0 0x00a00000 0x0 0x00004000>;
+ sifive,slot-permissions = <0x0 0x000000c3>;
+ sifive,slot-config = <0x0f>;
+ };
+ };
+
+ aplic1_m: interrupt-controller@c000000 {
+ compatible = "qemu,aplic", "riscv,aplic";
+ reg = <0x0 0xc000000 0x0 0x4000>;
+ interrupt-controller;
+ #interrupt-cells = <2>;
+ riscv,num-sources = <96>;
+ interrupts-extended = <&cpu_intc1 11>;
+ };
+ };
+
+ - |
+ #include <dt-bindings/interrupt-controller/irq.h>
+
+ // Example 3: DRAM partitioning with a secure enclave
+
+ cpus {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ timebase-frequency = <1000000>;
+ riscv,nworlds = <4>;
+ sifive,trustedwid = <3>;
+
+ cpu@0 {
+ device_type = "cpu";
+ reg = <0>;
+ compatible = "riscv";
+ riscv,isa-base = "rv64i";
+ riscv,isa-extensions = "i", "m", "a", "c", "smlwid", "smwiddeleg", "sswid";
+ riscv,pmwid = <3>;
+
+ cpu_intc2: interrupt-controller {
+ #interrupt-cells = <1>;
+ compatible = "riscv,cpu-intc";
+ interrupt-controller;
+ };
+ };
+ };
+
+ soc {
+ #address-cells = <2>;
+ #size-cells = <2>;
+
+ memory@80000000 {
+ device_type = "memory";
+ reg = <0x0 0x80000000 0x0 0x80000000>;
+ access-controllers = <&wgchecker2 0>,
+ <&wgchecker2 1>,
+ <&wgchecker2 2>;
+ };
+
+ wgchecker2: access-controller@40000000 {
+ compatible = "qemu,wgchecker2", "sifive,wgchecker2";
+ reg = <0x0 0x40000000 0x0 0x1000>;
+ #access-controller-cells = <1>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ interrupts = <82 IRQ_TYPE_LEVEL_HIGH>;
+ interrupt-parent = <&aplic2_m>;
+
+ partition@0 {
+ reg = <0>;
+ sifive,protected-region = <0x0 0x80000000 0x0 0x40000000>;
+ sifive,slot-permissions = <0x0 0x000000cf>;
+ sifive,slot-config = <0x0f>;
+ };
+
+ partition@1 {
+ reg = <1>;
+ sifive,protected-region = <0x0 0xc0000000 0x0 0x01000000>;
+ sifive,slot-permissions = <0x0 0x000000cc>;
+ sifive,slot-config = <0x0f>;
+ };
+
+ partition@2 {
+ reg = <2>;
+ sifive,protected-region = <0x0 0xc1000000 0x0 0x3f000000>;
+ sifive,slot-permissions = <0x0 0x000000cf>;
+ sifive,slot-config = <0x0f>;
+ };
+ };
+
+ aplic2_m: interrupt-controller@c000000 {
+ compatible = "qemu,aplic", "riscv,aplic";
+ reg = <0x0 0xc000000 0x0 0x4000>;
+ interrupt-controller;
+ #interrupt-cells = <2>;
+ riscv,num-sources = <96>;
+ interrupts-extended = <&cpu_intc2 11>;
+ };
+ };
--
2.43.7
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply related [flat|nested] 23+ messages in thread* [PATCH v2 3/3] dt-bindings: sifive: Add WorldGuard Checker
@ 2026-07-29 16:39 ` Yu-Chien Peter Lin
0 siblings, 0 replies; 23+ messages in thread
From: Yu-Chien Peter Lin @ 2026-07-29 16:39 UTC (permalink / raw)
To: devicetree, linux-riscv, linux-kernel
Cc: robh, krzk+dt, conor+dt, pjw, palmer, aou, alex, samuel.holland,
dlan, guodong, dfustini, michal.simek, junhui.liu,
darshan.prajapati, akpm, zhangchunyan, luxu.kernel, pincheng.plct,
nick.hu, jim.shu, zong.li, greentime.hu, robin.randhawa, scott,
dave.patel, raymond.mao, anup, pawandeep.oza, Yu-Chien Peter Lin
Add YAML binding schema for the SiFive wgChecker, a programmable
access controller integrated in the interconnect fabric of RISC-V
Worlds-capable SoCs.
wgChecker enforces World ID (WID) based access control on downstream
bus transactions. Each checker slot encodes a 2-bit permission field
per WID (read/write), enabling fine-grained memory partitioning and
device isolation between execution contexts. Violations are reported
via bus errors, interrupts, or both, selectable and lockable per slot.
The binding registers wgChecker as an access-controllers provider.
Consumers (i.e. its protected device) reference it via the standard
access-controllers phandle to declare their access requirements.
Also document the sifive,trustedwid property for the /cpus node,
identifying the privileged WID authorized to configure all checkers
on the platform.
Link: https://github.com/riscvarchive/security/blob/main/papers/worldguard%20proposal.pdf
Signed-off-by: Yu-Chien Peter Lin <peter.lin@sifive.com>
Reviewed-by: Zong Li <zong.li@sifive.com>
Reviewed-by: Jim Shu <jim.shu@sifive.com>
---
.../devicetree/bindings/riscv/worlds.yaml | 9 +
.../bindings/sifive/sifive,wgchecker2.yaml | 356 ++++++++++++++++++
2 files changed, 365 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
diff --git a/Documentation/devicetree/bindings/riscv/worlds.yaml b/Documentation/devicetree/bindings/riscv/worlds.yaml
index cc8b3747591e..c39a06c2dd8d 100644
--- a/Documentation/devicetree/bindings/riscv/worlds.yaml
+++ b/Documentation/devicetree/bindings/riscv/worlds.yaml
@@ -34,6 +34,14 @@ properties:
minimum: 2
maximum: 64
+ sifive,trustedwid:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ maximum: 31
+ description: |
+ The World ID (WID) designated as the trusted WID for this platform.
+ Transactions tagged with this WID are authorized to access and configure
+ WorldGuard blocks, including wgCheckers and wgMarkers.
+
additionalProperties: true
examples:
@@ -44,6 +52,7 @@ examples:
#size-cells = <0>;
timebase-frequency = <1000000>;
riscv,nworlds = <4>;
+ sifive,trustedwid = <3>;
cpu@0 {
device_type = "cpu";
diff --git a/Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml b/Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
new file mode 100644
index 000000000000..c025a4765cb3
--- /dev/null
+++ b/Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
@@ -0,0 +1,356 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+# Copyright (C) 2026 SiFive, Inc.
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/sifive/sifive,wgchecker2.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: SiFive WorldGuard Checker
+
+maintainers:
+ - Yu-Chien Peter Lin <peter.lin@sifive.com>
+
+description: |
+ The RISC-V Worlds ISA extension defines World IDs (WIDs) as architectural
+ identifiers that tag each system transaction with its originating context.
+ System integrators assign WIDs to execution contexts such as privilege modes,
+ trusted execution environments, or other isolation boundaries.
+
+ The SiFive WorldGuard Checker is a hardware firewall positioned in the
+ system interconnect fabric. It inspects every transaction, evaluating the
+ WID against access control policies encoded in checker slots for each
+ protected resource. Transactions from unauthorized WIDs are blocked and
+ reported as bus errors, interrupts, or both.
+
+ This enables spatial partitioning of memory regions and memory-mapped devices
+ across execution contexts. Different address ranges can enforce distinct
+ policies, allowing isolated workloads to coexist with hardware-enforced
+ protection.
+
+ The wgChecker acts as an access-controller provider as defined in the
+ access-controllers framework. Protected devices are consumers that declare
+ their access policy via the access-controllers property. The hardware
+ supports up to 32 World IDs.
+
+ The World ID authorized to configure WorldGuard blocks is specified by the
+ sifive,trustedwid property in the /cpus node.
+
+allOf:
+ - $ref: /schemas/access-controllers/access-controllers.yaml#
+
+properties:
+ compatible:
+ oneOf:
+ - items:
+ - const: qemu,wgchecker2
+ - const: sifive,wgchecker2
+ - const: sifive,wgchecker2
+
+ reg:
+ maxItems: 1
+ description:
+ Base address and size of the wgChecker memory-mapped I/O registers.
+
+ interrupts:
+ maxItems: 1
+ description:
+ Interrupt line asserted when a WID access violation is detected and
+ interrupt reporting is enabled in the slot configuration (IR or IW
+ bits set).
+
+ '#access-controller-cells':
+ const: 1
+ description: |
+ Specifies the partition identifier to reference a partition child
+ node that defines the access control region, WID permissions, and
+ access failure configuration. The special ID 0xFFFFFFFF indicates
+ unprotected mode, granting unrestricted access to the device.
+
+ '#address-cells':
+ const: 1
+
+ '#size-cells':
+ const: 0
+
+patternProperties:
+ "^partition@[0-9a-f]+$":
+ type: object
+ additionalProperties: false
+
+ properties:
+ reg:
+ maximum: 0xFFFFFFFE
+ description:
+ Partition identifier. Must be unique within the wgChecker node.
+ The value 0xFFFFFFFF is reserved for unprotected mode and must
+ not be used.
+
+ sifive,protected-region:
+ $ref: /schemas/types.yaml#/definitions/uint32-array
+ description:
+ Protected memory region encoded as a base address and size.
+ items:
+ - description: Upper 32 bits of the base address
+ - description: Lower 32 bits of the base address
+ - description: Upper 32 bits of the region size
+ - description: Lower 32 bits of the region size
+
+ sifive,slot-permissions:
+ $ref: /schemas/types.yaml#/definitions/uint64
+ description: |
+ 64-bit WID permission bitmap. Each WID N uses two consecutive bits:
+ - bit[2*N] : Read permission for WID N
+ - bit[2*N+1]: Write permission for WID N
+ Set bits grant access.
+
+ sifive,slot-config:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ maximum: 0x1F
+ description: |
+ Access failure configuration flags for this slot:
+ bit[0] (ER): report read violations as bus errors
+ bit[1] (EW): report write violations as bus errors
+ bit[2] (IR): report read violations via interrupt
+ bit[3] (IW): report write violations via interrupt
+ bit[4] (L) : lock this slot against further modification
+ Bits[5:31] are reserved and must be zero.
+
+ required:
+ - reg
+ - sifive,protected-region
+ - sifive,slot-permissions
+ - sifive,slot-config
+
+required:
+ - compatible
+ - reg
+ - '#address-cells'
+ - '#size-cells'
+ - '#access-controller-cells'
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/interrupt-controller/irq.h>
+
+ // Example 1: Peripheral device protection
+
+ cpus {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ timebase-frequency = <1000000>;
+ riscv,nworlds = <4>;
+ sifive,trustedwid = <3>;
+
+ cpu@0 {
+ device_type = "cpu";
+ reg = <0>;
+ compatible = "riscv";
+ riscv,isa-base = "rv64i";
+ riscv,isa-extensions = "i", "m", "a", "c", "smlwid";
+ riscv,pmwid = <3>;
+
+ cpu_intc0: interrupt-controller {
+ #interrupt-cells = <1>;
+ compatible = "riscv,cpu-intc";
+ interrupt-controller;
+ };
+ };
+ };
+
+ soc {
+ #address-cells = <2>;
+ #size-cells = <2>;
+
+ uart: uart@1c1000 {
+ compatible = "ns16550a";
+ reg = <0x0 0x001c1000 0x0 0x1000>;
+ reg-names = "control";
+ interrupts = <10 IRQ_TYPE_LEVEL_HIGH>;
+ access-controllers = <&wgchecker0 0>;
+ };
+
+ wgchecker0: access-controller@1c2000 {
+ compatible = "qemu,wgchecker2", "sifive,wgchecker2";
+ reg = <0x0 0x001c2000 0x0 0x1000>;
+ #access-controller-cells = <1>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ interrupts = <80 IRQ_TYPE_LEVEL_HIGH>;
+ interrupt-parent = <&aplic0_m>;
+
+ partition@0 {
+ reg = <0>;
+ sifive,protected-region = <0x0 0x001c1000 0x0 0x00001000>;
+ sifive,slot-permissions = <0x0 0x000000c3>;
+ sifive,slot-config = <0x0f>;
+ };
+ };
+
+ aplic0_m: interrupt-controller@c000000 {
+ compatible = "qemu,aplic", "riscv,aplic";
+ reg = <0x0 0xc000000 0x0 0x4000>;
+ interrupt-controller;
+ #interrupt-cells = <2>;
+ riscv,num-sources = <96>;
+ interrupts-extended = <&cpu_intc0 11>;
+ };
+ };
+
+ - |
+ #include <dt-bindings/interrupt-controller/irq.h>
+
+ // Example 2: Device with multiple address regions and per-region access rules
+
+ cpus {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ timebase-frequency = <1000000>;
+ riscv,nworlds = <16>;
+ sifive,trustedwid = <3>;
+
+ cpu@0 {
+ device_type = "cpu";
+ reg = <0>;
+ compatible = "riscv";
+ riscv,isa-base = "rv64i";
+ riscv,isa-extensions = "i", "m", "a", "c", "smlwid";
+ riscv,pmwid = <3>;
+
+ cpu_intc1: interrupt-controller {
+ #interrupt-cells = <1>;
+ compatible = "riscv,cpu-intc";
+ interrupt-controller;
+ };
+ };
+ };
+
+ soc {
+ #address-cells = <2>;
+ #size-cells = <2>;
+
+ device: device@10000 {
+ compatible = "vendor,soc1-ip";
+ reg = <0x0 0x00010000 0x0 0x8000>,
+ <0x0 0x00a00000 0x0 0x4000>;
+ reg-names = "m_mode", "s_mode";
+ // m_mode: WID 3 only; s_mode: WID 0,3 RW
+ access-controllers = <&wgchecker1 0>,
+ <&wgchecker1 1>;
+ };
+
+ wgchecker1: access-controller@35000 {
+ compatible = "qemu,wgchecker2", "sifive,wgchecker2";
+ reg = <0x0 0x00035000 0x0 0x1000>;
+ #access-controller-cells = <1>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ interrupts = <81 IRQ_TYPE_LEVEL_HIGH>;
+ interrupt-parent = <&aplic1_m>;
+
+ partition@0 {
+ reg = <0>;
+ sifive,protected-region = <0x0 0x00010000 0x0 0x00008000>;
+ sifive,slot-permissions = <0x0 0x000000c0>;
+ sifive,slot-config = <0x0f>;
+ };
+
+ partition@1 {
+ reg = <1>;
+ sifive,protected-region = <0x0 0x00a00000 0x0 0x00004000>;
+ sifive,slot-permissions = <0x0 0x000000c3>;
+ sifive,slot-config = <0x0f>;
+ };
+ };
+
+ aplic1_m: interrupt-controller@c000000 {
+ compatible = "qemu,aplic", "riscv,aplic";
+ reg = <0x0 0xc000000 0x0 0x4000>;
+ interrupt-controller;
+ #interrupt-cells = <2>;
+ riscv,num-sources = <96>;
+ interrupts-extended = <&cpu_intc1 11>;
+ };
+ };
+
+ - |
+ #include <dt-bindings/interrupt-controller/irq.h>
+
+ // Example 3: DRAM partitioning with a secure enclave
+
+ cpus {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ timebase-frequency = <1000000>;
+ riscv,nworlds = <4>;
+ sifive,trustedwid = <3>;
+
+ cpu@0 {
+ device_type = "cpu";
+ reg = <0>;
+ compatible = "riscv";
+ riscv,isa-base = "rv64i";
+ riscv,isa-extensions = "i", "m", "a", "c", "smlwid", "smwiddeleg", "sswid";
+ riscv,pmwid = <3>;
+
+ cpu_intc2: interrupt-controller {
+ #interrupt-cells = <1>;
+ compatible = "riscv,cpu-intc";
+ interrupt-controller;
+ };
+ };
+ };
+
+ soc {
+ #address-cells = <2>;
+ #size-cells = <2>;
+
+ memory@80000000 {
+ device_type = "memory";
+ reg = <0x0 0x80000000 0x0 0x80000000>;
+ access-controllers = <&wgchecker2 0>,
+ <&wgchecker2 1>,
+ <&wgchecker2 2>;
+ };
+
+ wgchecker2: access-controller@40000000 {
+ compatible = "qemu,wgchecker2", "sifive,wgchecker2";
+ reg = <0x0 0x40000000 0x0 0x1000>;
+ #access-controller-cells = <1>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ interrupts = <82 IRQ_TYPE_LEVEL_HIGH>;
+ interrupt-parent = <&aplic2_m>;
+
+ partition@0 {
+ reg = <0>;
+ sifive,protected-region = <0x0 0x80000000 0x0 0x40000000>;
+ sifive,slot-permissions = <0x0 0x000000cf>;
+ sifive,slot-config = <0x0f>;
+ };
+
+ partition@1 {
+ reg = <1>;
+ sifive,protected-region = <0x0 0xc0000000 0x0 0x01000000>;
+ sifive,slot-permissions = <0x0 0x000000cc>;
+ sifive,slot-config = <0x0f>;
+ };
+
+ partition@2 {
+ reg = <2>;
+ sifive,protected-region = <0x0 0xc1000000 0x0 0x3f000000>;
+ sifive,slot-permissions = <0x0 0x000000cf>;
+ sifive,slot-config = <0x0f>;
+ };
+ };
+
+ aplic2_m: interrupt-controller@c000000 {
+ compatible = "qemu,aplic", "riscv,aplic";
+ reg = <0x0 0xc000000 0x0 0x4000>;
+ interrupt-controller;
+ #interrupt-cells = <2>;
+ riscv,num-sources = <96>;
+ interrupts-extended = <&cpu_intc2 11>;
+ };
+ };
--
2.43.7
^ permalink raw reply related [flat|nested] 23+ messages in thread* Re: [PATCH v2 3/3] dt-bindings: sifive: Add WorldGuard Checker
2026-07-29 16:39 ` Yu-Chien Peter Lin
@ 2026-07-29 18:07 ` Rob Herring (Arm)
-1 siblings, 0 replies; 23+ messages in thread
From: Rob Herring (Arm) @ 2026-07-29 18:07 UTC (permalink / raw)
To: Yu-Chien Peter Lin
Cc: guodong, pjw, zhangchunyan, conor+dt, greentime.hu,
robin.randhawa, dfustini, raymond.mao, dave.patel, pincheng.plct,
linux-kernel, darshan.prajapati, linux-riscv, junhui.liu, akpm,
dlan, jim.shu, devicetree, luxu.kernel, krzk+dt, zong.li, anup,
michal.simek, scott, alex, samuel.holland, aou, pawandeep.oza,
palmer, nick.hu
On Thu, 30 Jul 2026 00:39:08 +0800, Yu-Chien Peter Lin wrote:
> Add YAML binding schema for the SiFive wgChecker, a programmable
> access controller integrated in the interconnect fabric of RISC-V
> Worlds-capable SoCs.
>
> wgChecker enforces World ID (WID) based access control on downstream
> bus transactions. Each checker slot encodes a 2-bit permission field
> per WID (read/write), enabling fine-grained memory partitioning and
> device isolation between execution contexts. Violations are reported
> via bus errors, interrupts, or both, selectable and lockable per slot.
>
> The binding registers wgChecker as an access-controllers provider.
> Consumers (i.e. its protected device) reference it via the standard
> access-controllers phandle to declare their access requirements.
>
> Also document the sifive,trustedwid property for the /cpus node,
> identifying the privileged WID authorized to configure all checkers
> on the platform.
>
> Link: https://github.com/riscvarchive/security/blob/main/papers/worldguard%20proposal.pdf
> Signed-off-by: Yu-Chien Peter Lin <peter.lin@sifive.com>
> Reviewed-by: Zong Li <zong.li@sifive.com>
> Reviewed-by: Jim Shu <jim.shu@sifive.com>
> ---
> .../devicetree/bindings/riscv/worlds.yaml | 9 +
> .../bindings/sifive/sifive,wgchecker2.yaml | 356 ++++++++++++++++++
> 2 files changed, 365 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
Documentation/devicetree/bindings/sifive/sifive,wgchecker2.example.dtb: uart@1c1000 (ns16550a): $nodename:0: 'uart@1c1000' does not match '^serial(@.*)?$'
from schema $id: http://devicetree.org/schemas/serial/8250.yaml
Documentation/devicetree/bindings/sifive/sifive,wgchecker2.example.dtb: uart@1c1000 (ns16550a): Unevaluated properties are not allowed ('access-controllers', 'reg-names' were unexpected)
from schema $id: http://devicetree.org/schemas/serial/8250.yaml
doc reference errors (make refcheckdocs):
See https://patchwork.kernel.org/project/devicetree/patch/20260729163908.249838-4-peter.lin@sifive.com
The base for the series is generally the latest rc1. A different dependency
should be noted in *this* patch.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit after running the above command yourself. Note
that DT_SCHEMA_FILES can be set to your schema file to speed up checking
your schema. However, it must be unset to test all examples with your schema.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [PATCH v2 3/3] dt-bindings: sifive: Add WorldGuard Checker
@ 2026-07-29 18:07 ` Rob Herring (Arm)
0 siblings, 0 replies; 23+ messages in thread
From: Rob Herring (Arm) @ 2026-07-29 18:07 UTC (permalink / raw)
To: Yu-Chien Peter Lin
Cc: guodong, pjw, zhangchunyan, conor+dt, greentime.hu,
robin.randhawa, dfustini, raymond.mao, dave.patel, pincheng.plct,
linux-kernel, darshan.prajapati, linux-riscv, junhui.liu, akpm,
dlan, jim.shu, devicetree, luxu.kernel, krzk+dt, zong.li, anup,
michal.simek, scott, alex, samuel.holland, aou, pawandeep.oza,
palmer, nick.hu
On Thu, 30 Jul 2026 00:39:08 +0800, Yu-Chien Peter Lin wrote:
> Add YAML binding schema for the SiFive wgChecker, a programmable
> access controller integrated in the interconnect fabric of RISC-V
> Worlds-capable SoCs.
>
> wgChecker enforces World ID (WID) based access control on downstream
> bus transactions. Each checker slot encodes a 2-bit permission field
> per WID (read/write), enabling fine-grained memory partitioning and
> device isolation between execution contexts. Violations are reported
> via bus errors, interrupts, or both, selectable and lockable per slot.
>
> The binding registers wgChecker as an access-controllers provider.
> Consumers (i.e. its protected device) reference it via the standard
> access-controllers phandle to declare their access requirements.
>
> Also document the sifive,trustedwid property for the /cpus node,
> identifying the privileged WID authorized to configure all checkers
> on the platform.
>
> Link: https://github.com/riscvarchive/security/blob/main/papers/worldguard%20proposal.pdf
> Signed-off-by: Yu-Chien Peter Lin <peter.lin@sifive.com>
> Reviewed-by: Zong Li <zong.li@sifive.com>
> Reviewed-by: Jim Shu <jim.shu@sifive.com>
> ---
> .../devicetree/bindings/riscv/worlds.yaml | 9 +
> .../bindings/sifive/sifive,wgchecker2.yaml | 356 ++++++++++++++++++
> 2 files changed, 365 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
Documentation/devicetree/bindings/sifive/sifive,wgchecker2.example.dtb: uart@1c1000 (ns16550a): $nodename:0: 'uart@1c1000' does not match '^serial(@.*)?$'
from schema $id: http://devicetree.org/schemas/serial/8250.yaml
Documentation/devicetree/bindings/sifive/sifive,wgchecker2.example.dtb: uart@1c1000 (ns16550a): Unevaluated properties are not allowed ('access-controllers', 'reg-names' were unexpected)
from schema $id: http://devicetree.org/schemas/serial/8250.yaml
doc reference errors (make refcheckdocs):
See https://patchwork.kernel.org/project/devicetree/patch/20260729163908.249838-4-peter.lin@sifive.com
The base for the series is generally the latest rc1. A different dependency
should be noted in *this* patch.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit after running the above command yourself. Note
that DT_SCHEMA_FILES can be set to your schema file to speed up checking
your schema. However, it must be unset to test all examples with your schema.
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [PATCH v2 3/3] dt-bindings: sifive: Add WorldGuard Checker
2026-07-29 16:39 ` Yu-Chien Peter Lin
@ 2026-07-30 7:35 ` Krzysztof Kozlowski
-1 siblings, 0 replies; 23+ messages in thread
From: Krzysztof Kozlowski @ 2026-07-30 7:35 UTC (permalink / raw)
To: Yu-Chien Peter Lin
Cc: devicetree, linux-riscv, linux-kernel, robh, krzk+dt, conor+dt,
pjw, palmer, aou, alex, samuel.holland, dlan, guodong, dfustini,
michal.simek, junhui.liu, darshan.prajapati, akpm, zhangchunyan,
luxu.kernel, pincheng.plct, nick.hu, jim.shu, zong.li,
greentime.hu, robin.randhawa, scott, dave.patel, raymond.mao,
anup, pawandeep.oza
On Thu, Jul 30, 2026 at 12:39:08AM +0800, Yu-Chien Peter Lin wrote:
> Add YAML binding schema for the SiFive wgChecker, a programmable
There is no "YAML" binding schema.
> access controller integrated in the interconnect fabric of RISC-V
> Worlds-capable SoCs.
>
> wgChecker enforces World ID (WID) based access control on downstream
> bus transactions. Each checker slot encodes a 2-bit permission field
> per WID (read/write), enabling fine-grained memory partitioning and
> device isolation between execution contexts. Violations are reported
> via bus errors, interrupts, or both, selectable and lockable per slot.
>
> The binding registers wgChecker as an access-controllers provider.
> Consumers (i.e. its protected device) reference it via the standard
> access-controllers phandle to declare their access requirements.
>
> Also document the sifive,trustedwid property for the /cpus node,
> identifying the privileged WID authorized to configure all checkers
> on the platform.
>
> Link: https://github.com/riscvarchive/security/blob/main/papers/worldguard%20proposal.pdf
> Signed-off-by: Yu-Chien Peter Lin <peter.lin@sifive.com>
> Reviewed-by: Zong Li <zong.li@sifive.com>
> Reviewed-by: Jim Shu <jim.shu@sifive.com>
What exactly these reviews pointed out?
> ---
> .../devicetree/bindings/riscv/worlds.yaml | 9 +
> .../bindings/sifive/sifive,wgchecker2.yaml | 356 ++++++++++++++++++
> 2 files changed, 365 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
>
> diff --git a/Documentation/devicetree/bindings/riscv/worlds.yaml b/Documentation/devicetree/bindings/riscv/worlds.yaml
> index cc8b3747591e..c39a06c2dd8d 100644
> --- a/Documentation/devicetree/bindings/riscv/worlds.yaml
> +++ b/Documentation/devicetree/bindings/riscv/worlds.yaml
> @@ -34,6 +34,14 @@ properties:
> minimum: 2
> maximum: 64
>
> + sifive,trustedwid:
No, for the same reasons.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maximum: 31
> + description: |
> + The World ID (WID) designated as the trusted WID for this platform.
> + Transactions tagged with this WID are authorized to access and configure
> + WorldGuard blocks, including wgCheckers and wgMarkers.
> +
> additionalProperties: true
>
> examples:
> @@ -44,6 +52,7 @@ examples:
> #size-cells = <0>;
> timebase-frequency = <1000000>;
> riscv,nworlds = <4>;
> + sifive,trustedwid = <3>;
>
> cpu@0 {
> device_type = "cpu";
> diff --git a/Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml b/Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
> new file mode 100644
> index 000000000000..c025a4765cb3
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
No, you do not get per vendor directory. NAK.
Do you see Qcom? Or TI? Or NXP?
Place it in appropriate directory matching the hardware.
> @@ -0,0 +1,356 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +# Copyright (C) 2026 SiFive, Inc.
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/sifive/sifive,wgchecker2.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: SiFive WorldGuard Checker
> +
> +maintainers:
> + - Yu-Chien Peter Lin <peter.lin@sifive.com>
> +
> +description: |
> + The RISC-V Worlds ISA extension defines World IDs (WIDs) as architectural
> + identifiers that tag each system transaction with its originating context.
> + System integrators assign WIDs to execution contexts such as privilege modes,
> + trusted execution environments, or other isolation boundaries.
> +
> + The SiFive WorldGuard Checker is a hardware firewall positioned in the
> + system interconnect fabric. It inspects every transaction, evaluating the
> + WID against access control policies encoded in checker slots for each
> + protected resource. Transactions from unauthorized WIDs are blocked and
> + reported as bus errors, interrupts, or both.
> +
> + This enables spatial partitioning of memory regions and memory-mapped devices
> + across execution contexts. Different address ranges can enforce distinct
> + policies, allowing isolated workloads to coexist with hardware-enforced
> + protection.
> +
> + The wgChecker acts as an access-controller provider as defined in the
> + access-controllers framework. Protected devices are consumers that declare
> + their access policy via the access-controllers property. The hardware
> + supports up to 32 World IDs.
> +
> + The World ID authorized to configure WorldGuard blocks is specified by the
> + sifive,trustedwid property in the /cpus node.
> +
> +allOf:
> + - $ref: /schemas/access-controllers/access-controllers.yaml#
> +
> +properties:
> + compatible:
> + oneOf:
> + - items:
> + - const: qemu,wgchecker2
> + - const: sifive,wgchecker2
> + - const: sifive,wgchecker2
You need soc specific compatibles.
I do not believe the two review tags did any actual real review. They
would tell you to read writing bindings document, wouldn't they?
> +
> + reg:
> + maxItems: 1
> + description:
> + Base address and size of the wgChecker memory-mapped I/O registers.
Again, standard comment. Why do you need description?
> +
> + interrupts:
> + maxItems: 1
> + description:
> + Interrupt line asserted when a WID access violation is detected and
> + interrupt reporting is enabled in the slot configuration (IR or IW
> + bits set).
> +
> + '#access-controller-cells':
> + const: 1
> + description: |
> + Specifies the partition identifier to reference a partition child
> + node that defines the access control region, WID permissions, and
> + access failure configuration. The special ID 0xFFFFFFFF indicates
> + unprotected mode, granting unrestricted access to the device.
> +
> + '#address-cells':
Use consistent quotes.
> + const: 1
> +
> + '#size-cells':
> + const: 0
> +
> +patternProperties:
> + "^partition@[0-9a-f]+$":
> + type: object
> + additionalProperties: false
> +
> + properties:
> + reg:
> + maximum: 0xFFFFFFFE
> + description:
> + Partition identifier. Must be unique within the wgChecker node.
> + The value 0xFFFFFFFF is reserved for unprotected mode and must
> + not be used.
> +
> + sifive,protected-region:
> + $ref: /schemas/types.yaml#/definitions/uint32-array
> + description:
> + Protected memory region encoded as a base address and size.
> + items:
> + - description: Upper 32 bits of the base address
> + - description: Lower 32 bits of the base address
> + - description: Upper 32 bits of the region size
> + - description: Lower 32 bits of the region size
> +
> + sifive,slot-permissions:
> + $ref: /schemas/types.yaml#/definitions/uint64
> + description: |
> + 64-bit WID permission bitmap. Each WID N uses two consecutive bits:
> + - bit[2*N] : Read permission for WID N
> + - bit[2*N+1]: Write permission for WID N
> + Set bits grant access.
> +
> + sifive,slot-config:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maximum: 0x1F
> + description: |
> + Access failure configuration flags for this slot:
> + bit[0] (ER): report read violations as bus errors
> + bit[1] (EW): report write violations as bus errors
> + bit[2] (IR): report read violations via interrupt
> + bit[3] (IW): report write violations via interrupt
> + bit[4] (L) : lock this slot against further modification
> + Bits[5:31] are reserved and must be zero.
> +
> + required:
> + - reg
> + - sifive,protected-region
> + - sifive,slot-permissions
> + - sifive,slot-config
> +
> +required:
> + - compatible
> + - reg
> + - '#address-cells'
> + - '#size-cells'
> + - '#access-controller-cells'
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> +
> + // Example 1: Peripheral device protection
> +
> + cpus {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + timebase-frequency = <1000000>;
> + riscv,nworlds = <4>;
> + sifive,trustedwid = <3>;
> +
> + cpu@0 {
> + device_type = "cpu";
> + reg = <0>;
> + compatible = "riscv";
> + riscv,isa-base = "rv64i";
> + riscv,isa-extensions = "i", "m", "a", "c", "smlwid";
> + riscv,pmwid = <3>;
> +
> + cpu_intc0: interrupt-controller {
> + #interrupt-cells = <1>;
> + compatible = "riscv,cpu-intc";
> + interrupt-controller;
> + };
> + };
> + };
> +
> + soc {
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + uart: uart@1c1000 {
> + compatible = "ns16550a";
> + reg = <0x0 0x001c1000 0x0 0x1000>;
> + reg-names = "control";
> + interrupts = <10 IRQ_TYPE_LEVEL_HIGH>;
> + access-controllers = <&wgchecker0 0>;
> + };
None of these are relevant. Drop all of the nodes.
Please read carefully writing bindings and DTS101 slides before posting
next version.
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [PATCH v2 3/3] dt-bindings: sifive: Add WorldGuard Checker
@ 2026-07-30 7:35 ` Krzysztof Kozlowski
0 siblings, 0 replies; 23+ messages in thread
From: Krzysztof Kozlowski @ 2026-07-30 7:35 UTC (permalink / raw)
To: Yu-Chien Peter Lin
Cc: devicetree, linux-riscv, linux-kernel, robh, krzk+dt, conor+dt,
pjw, palmer, aou, alex, samuel.holland, dlan, guodong, dfustini,
michal.simek, junhui.liu, darshan.prajapati, akpm, zhangchunyan,
luxu.kernel, pincheng.plct, nick.hu, jim.shu, zong.li,
greentime.hu, robin.randhawa, scott, dave.patel, raymond.mao,
anup, pawandeep.oza
On Thu, Jul 30, 2026 at 12:39:08AM +0800, Yu-Chien Peter Lin wrote:
> Add YAML binding schema for the SiFive wgChecker, a programmable
There is no "YAML" binding schema.
> access controller integrated in the interconnect fabric of RISC-V
> Worlds-capable SoCs.
>
> wgChecker enforces World ID (WID) based access control on downstream
> bus transactions. Each checker slot encodes a 2-bit permission field
> per WID (read/write), enabling fine-grained memory partitioning and
> device isolation between execution contexts. Violations are reported
> via bus errors, interrupts, or both, selectable and lockable per slot.
>
> The binding registers wgChecker as an access-controllers provider.
> Consumers (i.e. its protected device) reference it via the standard
> access-controllers phandle to declare their access requirements.
>
> Also document the sifive,trustedwid property for the /cpus node,
> identifying the privileged WID authorized to configure all checkers
> on the platform.
>
> Link: https://github.com/riscvarchive/security/blob/main/papers/worldguard%20proposal.pdf
> Signed-off-by: Yu-Chien Peter Lin <peter.lin@sifive.com>
> Reviewed-by: Zong Li <zong.li@sifive.com>
> Reviewed-by: Jim Shu <jim.shu@sifive.com>
What exactly these reviews pointed out?
> ---
> .../devicetree/bindings/riscv/worlds.yaml | 9 +
> .../bindings/sifive/sifive,wgchecker2.yaml | 356 ++++++++++++++++++
> 2 files changed, 365 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
>
> diff --git a/Documentation/devicetree/bindings/riscv/worlds.yaml b/Documentation/devicetree/bindings/riscv/worlds.yaml
> index cc8b3747591e..c39a06c2dd8d 100644
> --- a/Documentation/devicetree/bindings/riscv/worlds.yaml
> +++ b/Documentation/devicetree/bindings/riscv/worlds.yaml
> @@ -34,6 +34,14 @@ properties:
> minimum: 2
> maximum: 64
>
> + sifive,trustedwid:
No, for the same reasons.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maximum: 31
> + description: |
> + The World ID (WID) designated as the trusted WID for this platform.
> + Transactions tagged with this WID are authorized to access and configure
> + WorldGuard blocks, including wgCheckers and wgMarkers.
> +
> additionalProperties: true
>
> examples:
> @@ -44,6 +52,7 @@ examples:
> #size-cells = <0>;
> timebase-frequency = <1000000>;
> riscv,nworlds = <4>;
> + sifive,trustedwid = <3>;
>
> cpu@0 {
> device_type = "cpu";
> diff --git a/Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml b/Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
> new file mode 100644
> index 000000000000..c025a4765cb3
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
No, you do not get per vendor directory. NAK.
Do you see Qcom? Or TI? Or NXP?
Place it in appropriate directory matching the hardware.
> @@ -0,0 +1,356 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +# Copyright (C) 2026 SiFive, Inc.
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/sifive/sifive,wgchecker2.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: SiFive WorldGuard Checker
> +
> +maintainers:
> + - Yu-Chien Peter Lin <peter.lin@sifive.com>
> +
> +description: |
> + The RISC-V Worlds ISA extension defines World IDs (WIDs) as architectural
> + identifiers that tag each system transaction with its originating context.
> + System integrators assign WIDs to execution contexts such as privilege modes,
> + trusted execution environments, or other isolation boundaries.
> +
> + The SiFive WorldGuard Checker is a hardware firewall positioned in the
> + system interconnect fabric. It inspects every transaction, evaluating the
> + WID against access control policies encoded in checker slots for each
> + protected resource. Transactions from unauthorized WIDs are blocked and
> + reported as bus errors, interrupts, or both.
> +
> + This enables spatial partitioning of memory regions and memory-mapped devices
> + across execution contexts. Different address ranges can enforce distinct
> + policies, allowing isolated workloads to coexist with hardware-enforced
> + protection.
> +
> + The wgChecker acts as an access-controller provider as defined in the
> + access-controllers framework. Protected devices are consumers that declare
> + their access policy via the access-controllers property. The hardware
> + supports up to 32 World IDs.
> +
> + The World ID authorized to configure WorldGuard blocks is specified by the
> + sifive,trustedwid property in the /cpus node.
> +
> +allOf:
> + - $ref: /schemas/access-controllers/access-controllers.yaml#
> +
> +properties:
> + compatible:
> + oneOf:
> + - items:
> + - const: qemu,wgchecker2
> + - const: sifive,wgchecker2
> + - const: sifive,wgchecker2
You need soc specific compatibles.
I do not believe the two review tags did any actual real review. They
would tell you to read writing bindings document, wouldn't they?
> +
> + reg:
> + maxItems: 1
> + description:
> + Base address and size of the wgChecker memory-mapped I/O registers.
Again, standard comment. Why do you need description?
> +
> + interrupts:
> + maxItems: 1
> + description:
> + Interrupt line asserted when a WID access violation is detected and
> + interrupt reporting is enabled in the slot configuration (IR or IW
> + bits set).
> +
> + '#access-controller-cells':
> + const: 1
> + description: |
> + Specifies the partition identifier to reference a partition child
> + node that defines the access control region, WID permissions, and
> + access failure configuration. The special ID 0xFFFFFFFF indicates
> + unprotected mode, granting unrestricted access to the device.
> +
> + '#address-cells':
Use consistent quotes.
> + const: 1
> +
> + '#size-cells':
> + const: 0
> +
> +patternProperties:
> + "^partition@[0-9a-f]+$":
> + type: object
> + additionalProperties: false
> +
> + properties:
> + reg:
> + maximum: 0xFFFFFFFE
> + description:
> + Partition identifier. Must be unique within the wgChecker node.
> + The value 0xFFFFFFFF is reserved for unprotected mode and must
> + not be used.
> +
> + sifive,protected-region:
> + $ref: /schemas/types.yaml#/definitions/uint32-array
> + description:
> + Protected memory region encoded as a base address and size.
> + items:
> + - description: Upper 32 bits of the base address
> + - description: Lower 32 bits of the base address
> + - description: Upper 32 bits of the region size
> + - description: Lower 32 bits of the region size
> +
> + sifive,slot-permissions:
> + $ref: /schemas/types.yaml#/definitions/uint64
> + description: |
> + 64-bit WID permission bitmap. Each WID N uses two consecutive bits:
> + - bit[2*N] : Read permission for WID N
> + - bit[2*N+1]: Write permission for WID N
> + Set bits grant access.
> +
> + sifive,slot-config:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maximum: 0x1F
> + description: |
> + Access failure configuration flags for this slot:
> + bit[0] (ER): report read violations as bus errors
> + bit[1] (EW): report write violations as bus errors
> + bit[2] (IR): report read violations via interrupt
> + bit[3] (IW): report write violations via interrupt
> + bit[4] (L) : lock this slot against further modification
> + Bits[5:31] are reserved and must be zero.
> +
> + required:
> + - reg
> + - sifive,protected-region
> + - sifive,slot-permissions
> + - sifive,slot-config
> +
> +required:
> + - compatible
> + - reg
> + - '#address-cells'
> + - '#size-cells'
> + - '#access-controller-cells'
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> +
> + // Example 1: Peripheral device protection
> +
> + cpus {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + timebase-frequency = <1000000>;
> + riscv,nworlds = <4>;
> + sifive,trustedwid = <3>;
> +
> + cpu@0 {
> + device_type = "cpu";
> + reg = <0>;
> + compatible = "riscv";
> + riscv,isa-base = "rv64i";
> + riscv,isa-extensions = "i", "m", "a", "c", "smlwid";
> + riscv,pmwid = <3>;
> +
> + cpu_intc0: interrupt-controller {
> + #interrupt-cells = <1>;
> + compatible = "riscv,cpu-intc";
> + interrupt-controller;
> + };
> + };
> + };
> +
> + soc {
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + uart: uart@1c1000 {
> + compatible = "ns16550a";
> + reg = <0x0 0x001c1000 0x0 0x1000>;
> + reg-names = "control";
> + interrupts = <10 IRQ_TYPE_LEVEL_HIGH>;
> + access-controllers = <&wgchecker0 0>;
> + };
None of these are relevant. Drop all of the nodes.
Please read carefully writing bindings and DTS101 slides before posting
next version.
Best regards,
Krzysztof
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [PATCH v2 3/3] dt-bindings: sifive: Add WorldGuard Checker
2026-07-30 7:35 ` Krzysztof Kozlowski
@ 2026-07-30 7:37 ` Krzysztof Kozlowski
-1 siblings, 0 replies; 23+ messages in thread
From: Krzysztof Kozlowski @ 2026-07-30 7:37 UTC (permalink / raw)
To: Yu-Chien Peter Lin
Cc: devicetree, linux-riscv, linux-kernel, robh, krzk+dt, conor+dt,
pjw, palmer, aou, alex, samuel.holland, dlan, guodong, dfustini,
michal.simek, junhui.liu, darshan.prajapati, akpm, zhangchunyan,
luxu.kernel, pincheng.plct, nick.hu, jim.shu, zong.li,
greentime.hu, robin.randhawa, scott, dave.patel, raymond.mao,
anup, pawandeep.oza
On 30/07/2026 09:35, Krzysztof Kozlowski wrote:
>> +allOf:
>> + - $ref: /schemas/access-controllers/access-controllers.yaml#
>> +
>> +properties:
>> + compatible:
>> + oneOf:
>> + - items:
>> + - const: qemu,wgchecker2
>> + - const: sifive,wgchecker2
>> + - const: sifive,wgchecker2
>
> You need soc specific compatibles.
>
> I do not believe the two review tags did any actual real review. They
> would tell you to read writing bindings document, wouldn't they?
And you WERE TOLD this already at v1 - missing device specific compatibles.
Drop all review tags here, they did not happen.
Best regards,
Krzysztof
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [PATCH v2 3/3] dt-bindings: sifive: Add WorldGuard Checker
@ 2026-07-30 7:37 ` Krzysztof Kozlowski
0 siblings, 0 replies; 23+ messages in thread
From: Krzysztof Kozlowski @ 2026-07-30 7:37 UTC (permalink / raw)
To: Yu-Chien Peter Lin
Cc: devicetree, linux-riscv, linux-kernel, robh, krzk+dt, conor+dt,
pjw, palmer, aou, alex, samuel.holland, dlan, guodong, dfustini,
michal.simek, junhui.liu, darshan.prajapati, akpm, zhangchunyan,
luxu.kernel, pincheng.plct, nick.hu, jim.shu, zong.li,
greentime.hu, robin.randhawa, scott, dave.patel, raymond.mao,
anup, pawandeep.oza
On 30/07/2026 09:35, Krzysztof Kozlowski wrote:
>> +allOf:
>> + - $ref: /schemas/access-controllers/access-controllers.yaml#
>> +
>> +properties:
>> + compatible:
>> + oneOf:
>> + - items:
>> + - const: qemu,wgchecker2
>> + - const: sifive,wgchecker2
>> + - const: sifive,wgchecker2
>
> You need soc specific compatibles.
>
> I do not believe the two review tags did any actual real review. They
> would tell you to read writing bindings document, wouldn't they?
And you WERE TOLD this already at v1 - missing device specific compatibles.
Drop all review tags here, they did not happen.
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [PATCH v2 3/3] dt-bindings: sifive: Add WorldGuard Checker
2026-07-30 7:35 ` Krzysztof Kozlowski
@ 2026-07-30 17:36 ` Conor Dooley
-1 siblings, 0 replies; 23+ messages in thread
From: Conor Dooley @ 2026-07-30 17:36 UTC (permalink / raw)
To: Krzysztof Kozlowski
Cc: Yu-Chien Peter Lin, devicetree, linux-riscv, linux-kernel, robh,
krzk+dt, conor+dt, pjw, palmer, aou, alex, samuel.holland, dlan,
guodong, dfustini, michal.simek, junhui.liu, darshan.prajapati,
akpm, zhangchunyan, luxu.kernel, pincheng.plct, nick.hu, jim.shu,
zong.li, greentime.hu, robin.randhawa, scott, dave.patel,
raymond.mao, anup, pawandeep.oza
[-- Attachment #1: Type: text/plain, Size: 6180 bytes --]
On Thu, Jul 30, 2026 at 09:35:02AM +0200, Krzysztof Kozlowski wrote:
> On Thu, Jul 30, 2026 at 12:39:08AM +0800, Yu-Chien Peter Lin wrote:
> > Add YAML binding schema for the SiFive wgChecker, a programmable
>
> There is no "YAML" binding schema.
>
> > access controller integrated in the interconnect fabric of RISC-V
> > Worlds-capable SoCs.
> >
> > wgChecker enforces World ID (WID) based access control on downstream
> > bus transactions. Each checker slot encodes a 2-bit permission field
> > per WID (read/write), enabling fine-grained memory partitioning and
> > device isolation between execution contexts. Violations are reported
> > via bus errors, interrupts, or both, selectable and lockable per slot.
> >
> > The binding registers wgChecker as an access-controllers provider.
> > Consumers (i.e. its protected device) reference it via the standard
> > access-controllers phandle to declare their access requirements.
> >
> > Also document the sifive,trustedwid property for the /cpus node,
> > identifying the privileged WID authorized to configure all checkers
> > on the platform.
> >
> > Link: https://github.com/riscvarchive/security/blob/main/papers/worldguard%20proposal.pdf
> > Signed-off-by: Yu-Chien Peter Lin <peter.lin@sifive.com>
> > Reviewed-by: Zong Li <zong.li@sifive.com>
> > Reviewed-by: Jim Shu <jim.shu@sifive.com>
>
> What exactly these reviews pointed out?
>
> > ---
> > .../devicetree/bindings/riscv/worlds.yaml | 9 +
> > .../bindings/sifive/sifive,wgchecker2.yaml | 356 ++++++++++++++++++
> > 2 files changed, 365 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/riscv/worlds.yaml b/Documentation/devicetree/bindings/riscv/worlds.yaml
> > index cc8b3747591e..c39a06c2dd8d 100644
> > --- a/Documentation/devicetree/bindings/riscv/worlds.yaml
> > +++ b/Documentation/devicetree/bindings/riscv/worlds.yaml
> > @@ -34,6 +34,14 @@ properties:
> > minimum: 2
> > maximum: 64
> >
> > + sifive,trustedwid:
>
> No, for the same reasons.
I am not entirely sure that this is defined by the platform compatible,
if you've got something like a FPGA with lots of configurability then it
may be needed. Then again, yeah maybe it can just come from the platform
compatible unlike a device shows up that actually needs it.
This is especially true if the consumer of the property is the SBI
firmware.
(that's assuming "same reason" follows on from your comment on the
prior binding)
>
> > + $ref: /schemas/types.yaml#/definitions/uint32
> > + maximum: 31
> > + description: |
> > + The World ID (WID) designated as the trusted WID for this platform.
> > + Transactions tagged with this WID are authorized to access and configure
> > + WorldGuard blocks, including wgCheckers and wgMarkers.
> > +
> > additionalProperties: true
> >
> > examples:
> > @@ -44,6 +52,7 @@ examples:
> > #size-cells = <0>;
> > timebase-frequency = <1000000>;
> > riscv,nworlds = <4>;
> > + sifive,trustedwid = <3>;
> >
> > cpu@0 {
> > device_type = "cpu";
> > diff --git a/Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml b/Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
> > new file mode 100644
> > index 000000000000..c025a4765cb3
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
>
> No, you do not get per vendor directory. NAK.
>
> Do you see Qcom? Or TI? Or NXP?
>
> Place it in appropriate directory matching the hardware.
Which would be access-controllers.
>
>
> > @@ -0,0 +1,356 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +# Copyright (C) 2026 SiFive, Inc.
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/sifive/sifive,wgchecker2.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: SiFive WorldGuard Checker
> > +
> > +maintainers:
> > + - Yu-Chien Peter Lin <peter.lin@sifive.com>
> > +
> > +description: |
> > + The RISC-V Worlds ISA extension defines World IDs (WIDs) as architectural
> > + identifiers that tag each system transaction with its originating context.
> > + System integrators assign WIDs to execution contexts such as privilege modes,
> > + trusted execution environments, or other isolation boundaries.
> > +
> > + The SiFive WorldGuard Checker is a hardware firewall positioned in the
> > + system interconnect fabric. It inspects every transaction, evaluating the
> > + WID against access control policies encoded in checker slots for each
> > + protected resource. Transactions from unauthorized WIDs are blocked and
> > + reported as bus errors, interrupts, or both.
> > +
> > + This enables spatial partitioning of memory regions and memory-mapped devices
> > + across execution contexts. Different address ranges can enforce distinct
> > + policies, allowing isolated workloads to coexist with hardware-enforced
> > + protection.
> > +
> > + The wgChecker acts as an access-controller provider as defined in the
> > + access-controllers framework. Protected devices are consumers that declare
> > + their access policy via the access-controllers property. The hardware
> > + supports up to 32 World IDs.
> > +
> > + The World ID authorized to configure WorldGuard blocks is specified by the
> > + sifive,trustedwid property in the /cpus node.
> > +
> > +allOf:
> > + - $ref: /schemas/access-controllers/access-controllers.yaml#
> > +
> > +properties:
> > + compatible:
> > + oneOf:
> > + - items:
> > + - const: qemu,wgchecker2
> > + - const: sifive,wgchecker2
> > + - const: sifive,wgchecker2
>
> You need soc specific compatibles.
>
> I do not believe the two review tags did any actual real review. They
> would tell you to read writing bindings document, wouldn't they?
I did okay the qemu compatible FWIW, the standalone sifive one though I
did not.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 23+ messages in thread* Re: [PATCH v2 3/3] dt-bindings: sifive: Add WorldGuard Checker
@ 2026-07-30 17:36 ` Conor Dooley
0 siblings, 0 replies; 23+ messages in thread
From: Conor Dooley @ 2026-07-30 17:36 UTC (permalink / raw)
To: Krzysztof Kozlowski
Cc: Yu-Chien Peter Lin, devicetree, linux-riscv, linux-kernel, robh,
krzk+dt, conor+dt, pjw, palmer, aou, alex, samuel.holland, dlan,
guodong, dfustini, michal.simek, junhui.liu, darshan.prajapati,
akpm, zhangchunyan, luxu.kernel, pincheng.plct, nick.hu, jim.shu,
zong.li, greentime.hu, robin.randhawa, scott, dave.patel,
raymond.mao, anup, pawandeep.oza
[-- Attachment #1.1: Type: text/plain, Size: 6180 bytes --]
On Thu, Jul 30, 2026 at 09:35:02AM +0200, Krzysztof Kozlowski wrote:
> On Thu, Jul 30, 2026 at 12:39:08AM +0800, Yu-Chien Peter Lin wrote:
> > Add YAML binding schema for the SiFive wgChecker, a programmable
>
> There is no "YAML" binding schema.
>
> > access controller integrated in the interconnect fabric of RISC-V
> > Worlds-capable SoCs.
> >
> > wgChecker enforces World ID (WID) based access control on downstream
> > bus transactions. Each checker slot encodes a 2-bit permission field
> > per WID (read/write), enabling fine-grained memory partitioning and
> > device isolation between execution contexts. Violations are reported
> > via bus errors, interrupts, or both, selectable and lockable per slot.
> >
> > The binding registers wgChecker as an access-controllers provider.
> > Consumers (i.e. its protected device) reference it via the standard
> > access-controllers phandle to declare their access requirements.
> >
> > Also document the sifive,trustedwid property for the /cpus node,
> > identifying the privileged WID authorized to configure all checkers
> > on the platform.
> >
> > Link: https://github.com/riscvarchive/security/blob/main/papers/worldguard%20proposal.pdf
> > Signed-off-by: Yu-Chien Peter Lin <peter.lin@sifive.com>
> > Reviewed-by: Zong Li <zong.li@sifive.com>
> > Reviewed-by: Jim Shu <jim.shu@sifive.com>
>
> What exactly these reviews pointed out?
>
> > ---
> > .../devicetree/bindings/riscv/worlds.yaml | 9 +
> > .../bindings/sifive/sifive,wgchecker2.yaml | 356 ++++++++++++++++++
> > 2 files changed, 365 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/riscv/worlds.yaml b/Documentation/devicetree/bindings/riscv/worlds.yaml
> > index cc8b3747591e..c39a06c2dd8d 100644
> > --- a/Documentation/devicetree/bindings/riscv/worlds.yaml
> > +++ b/Documentation/devicetree/bindings/riscv/worlds.yaml
> > @@ -34,6 +34,14 @@ properties:
> > minimum: 2
> > maximum: 64
> >
> > + sifive,trustedwid:
>
> No, for the same reasons.
I am not entirely sure that this is defined by the platform compatible,
if you've got something like a FPGA with lots of configurability then it
may be needed. Then again, yeah maybe it can just come from the platform
compatible unlike a device shows up that actually needs it.
This is especially true if the consumer of the property is the SBI
firmware.
(that's assuming "same reason" follows on from your comment on the
prior binding)
>
> > + $ref: /schemas/types.yaml#/definitions/uint32
> > + maximum: 31
> > + description: |
> > + The World ID (WID) designated as the trusted WID for this platform.
> > + Transactions tagged with this WID are authorized to access and configure
> > + WorldGuard blocks, including wgCheckers and wgMarkers.
> > +
> > additionalProperties: true
> >
> > examples:
> > @@ -44,6 +52,7 @@ examples:
> > #size-cells = <0>;
> > timebase-frequency = <1000000>;
> > riscv,nworlds = <4>;
> > + sifive,trustedwid = <3>;
> >
> > cpu@0 {
> > device_type = "cpu";
> > diff --git a/Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml b/Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
> > new file mode 100644
> > index 000000000000..c025a4765cb3
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
>
> No, you do not get per vendor directory. NAK.
>
> Do you see Qcom? Or TI? Or NXP?
>
> Place it in appropriate directory matching the hardware.
Which would be access-controllers.
>
>
> > @@ -0,0 +1,356 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +# Copyright (C) 2026 SiFive, Inc.
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/sifive/sifive,wgchecker2.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: SiFive WorldGuard Checker
> > +
> > +maintainers:
> > + - Yu-Chien Peter Lin <peter.lin@sifive.com>
> > +
> > +description: |
> > + The RISC-V Worlds ISA extension defines World IDs (WIDs) as architectural
> > + identifiers that tag each system transaction with its originating context.
> > + System integrators assign WIDs to execution contexts such as privilege modes,
> > + trusted execution environments, or other isolation boundaries.
> > +
> > + The SiFive WorldGuard Checker is a hardware firewall positioned in the
> > + system interconnect fabric. It inspects every transaction, evaluating the
> > + WID against access control policies encoded in checker slots for each
> > + protected resource. Transactions from unauthorized WIDs are blocked and
> > + reported as bus errors, interrupts, or both.
> > +
> > + This enables spatial partitioning of memory regions and memory-mapped devices
> > + across execution contexts. Different address ranges can enforce distinct
> > + policies, allowing isolated workloads to coexist with hardware-enforced
> > + protection.
> > +
> > + The wgChecker acts as an access-controller provider as defined in the
> > + access-controllers framework. Protected devices are consumers that declare
> > + their access policy via the access-controllers property. The hardware
> > + supports up to 32 World IDs.
> > +
> > + The World ID authorized to configure WorldGuard blocks is specified by the
> > + sifive,trustedwid property in the /cpus node.
> > +
> > +allOf:
> > + - $ref: /schemas/access-controllers/access-controllers.yaml#
> > +
> > +properties:
> > + compatible:
> > + oneOf:
> > + - items:
> > + - const: qemu,wgchecker2
> > + - const: sifive,wgchecker2
> > + - const: sifive,wgchecker2
>
> You need soc specific compatibles.
>
> I do not believe the two review tags did any actual real review. They
> would tell you to read writing bindings document, wouldn't they?
I did okay the qemu compatible FWIW, the standalone sifive one though I
did not.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [PATCH v2 0/3] dt-bindings: riscv: Add RISC-V Worlds and SiFive WorldGuard DT bindings
2026-07-29 16:39 ` Yu-Chien Peter Lin
` (3 preceding siblings ...)
(?)
@ 2026-07-31 1:43 ` Nick Kossifidis
-1 siblings, 0 replies; 23+ messages in thread
From: Nick Kossifidis @ 2026-07-31 1:43 UTC (permalink / raw)
To: Yu-Chien Peter Lin, devicetree, linux-riscv, linux-kernel
Cc: robh, krzk+dt, conor+dt, pjw, palmer, aou, alex
Hello Peter,
On 7/29/26 19:39, Yu-Chien Peter Lin wrote:
> Add device tree bindings for RISC-V Worlds, a standard extension that tags
> every transaction with a World ID for fine-grained isolation. SiFive's
> WorldGuard Checker is a hardware firewall in the system interconnect that
> inspects transaction WIDs and enforces per-World access policies on memory
> and MMIO devices.
>
> wgChecker specification reference:
> https://github.com/riscvarchive/security/blob/main/papers/worldguard%20proposal.pdf
>
> Yu-Chien Peter Lin (3):
> dt-bindings: riscv: Add Worlds ISA extensions
> dt-bindings: riscv: Add Worlds per-hart properties
> dt-bindings: sifive: Add WorldGuard Checker
>
> .../devicetree/bindings/riscv/cpus.yaml | 61 +++
> .../devicetree/bindings/riscv/extensions.yaml | 53 +++
> .../devicetree/bindings/riscv/worlds.yaml | 86 +++++
> .../bindings/sifive/sifive,wgchecker2.yaml | 356 ++++++++++++++++++
> 4 files changed, 556 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/riscv/worlds.yaml
> create mode 100644 Documentation/devicetree/bindings/sifive/sifive,wgchecker2.yaml
>
What's the plan for this and why do we need Linux-specific dt bindings ?
This looks more like a set of firmware specific bindings, like OpenSBI
domains for example
(https://github.com/riscv-software-src/opensbi/blob/master/docs/domain_support.md).
I understand adding the ISA extensions in the list (although the fast
track is still underway, it's not ratified yet), but the rest don't make
sense, not yet at least. How do you plan to use pmlwidlist on Linux to
associate processes to wids ? Do you plan on adding a driver for the wg
checker (and the markers that you mention) on Linux ? Do you ever expect
Linux to run under trustedwid ?
Regards,
Nick
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 23+ messages in thread