mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rama devi Veggalam <rama.devi.veggalam@amd.com>
To: <bp@alien8.de>, <tony.luck@intel.com>, <michal.simek@amd.com>,
	<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-edac@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <james.morse@arm.com>,
	<mchehab@kernel.org>, <rric@kernel.org>, <git@amd.com>,
	Rama devi Veggalam <rama.devi.veggalam@amd.com>
Subject: [PATCH v5 1/3] dt-bindings: edac: Add Xilinx XilSEM
Date: Sun, 22 Nov 2026 07:35:22 +0530	[thread overview]
Message-ID: <1795313124-2138932-2-git-send-email-rama.devi.veggalam@amd.com> (raw)
In-Reply-To: <1795313124-2138932-1-git-send-email-rama.devi.veggalam@amd.com>

Add a devicetree binding for the Xilinx Soft Error Mitigation (XilSEM)
block on Versal and Versal NET devices.

XilSEM is part of the Platform Loader and Manager (PLM) that runs on
the Platform Management Controller (PMC). It detects, and optionally
corrects, soft errors in the Configuration RAM (CRAM) and the NoC
programming interface (NPI) registers. Errors are reported to Linux
through the firmware's event notification interface, so the node needs
no interrupt property. The only resource is the register region used to
read the CRAM and NPI scan status.

Only monolithic (single-SLR) devices are supported; multi-SLR devices
are not covered by this binding.

Use a single compatible, xlnx,xilsem, because XilSEM is common to Versal
and Versal NET devices.

Signed-off-by: Rama devi Veggalam <rama.devi.veggalam@amd.com>
---
Changes in v5:
- Moved the XilSEM binding out of the Versal DDRMC EDAC yaml into a
  separate xilsem yaml.
- Renamed the compatible to xlnx,xilsem, shared by Versal and Versal
  NET.
- Described the CRAM and NPI coverage, and why there is no interrupt
  property.
- Described reg as the PLM RTCA region used to read the CRAM and NPI
  scan status.
- Stated that only monolithic devices are supported.

Changes in v4:
- Added a new "xlnx,versal-xilsem" compatible string to the existing
  xlnx,versal-ddrmc-edac.yaml binding, gated via allOf/if-then so
  DDRMC and XilSEM requirements (reg, reg-names, interrupts) are
  validated independently per compatible string.

Changes in v3:
- Merged XilSEM edac with Versal Edac

Changes in v2:
- Changed "xlnx,versal-xilsem-edac" to constant
- Removed "compatible: in required section
- Removed "|" in description
- Removed "items" in compatible
- Fixed indentation in examples
- Updated title and description
---
 .../devicetree/bindings/edac/xlnx,xilsem.yaml      | 53 ++++++++++++++++++++++
 1 file changed, 53 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/edac/xlnx,xilsem.yaml

diff --git a/Documentation/devicetree/bindings/edac/xlnx,xilsem.yaml b/Documentation/devicetree/bindings/edac/xlnx,xilsem.yaml
new file mode 100644
index 0000000..3ae5b6e
--- /dev/null
+++ b/Documentation/devicetree/bindings/edac/xlnx,xilsem.yaml
@@ -0,0 +1,53 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/edac/xlnx,xilsem.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Xilinx XilSEM EDAC
+
+maintainers:
+  - Rama devi Veggalam <rama.devi.veggalam@amd.com>
+
+description:
+  Xilinx Soft Error Mitigation (XilSEM) is part of the Platform Loader and
+  Manager (PLM) which is loaded into and runs on the Platform Management
+  Controller (PMC) of Versal and Versal NET devices. XilSEM is responsible for
+  detecting and optionally correcting soft errors in Configuration RAM (CRAM)
+  and the NoC Programming Interface (NPI) registers. Whenever an error is
+  detected, be it correctable or uncorrectable, XilSEM notifies the errors to
+  user applications via the firmware's event notification interface, so no
+  interrupt property is needed.
+
+  Only monolithic (single Super Logic Region, SLR) devices are supported.
+  Multi-SLR devices, built with Stacked Silicon Interconnect Technology
+  (SSIT), are not supported, and this node must not be used on them.
+
+properties:
+  compatible:
+    const: xlnx,xilsem
+
+  reg:
+    items:
+      - description:
+          XilSEM region in the PLM Run-Time Configuration Area (RTCA), which
+          the PLM firmware updates and Linux only reads, used to read the CRAM
+          and NPI scan status
+
+required:
+  - compatible
+  - reg
+
+additionalProperties: false
+
+examples:
+  - |
+    bus {
+        #address-cells = <2>;
+        #size-cells = <2>;
+
+        edac@f2014050 {
+            compatible = "xlnx,xilsem";
+            reg = <0x0 0xf2014050 0x0 0xc4>;
+        };
+    };
-- 
1.9.5


  reply	other threads:[~2026-11-22  2:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-22  2:05 [PATCH v5 0/3] EDAC: Add Xilinx XilSEM error monitoring driver Rama devi Veggalam
2026-11-22  2:05 ` Rama devi Veggalam [this message]
2026-11-22  2:05 ` [PATCH v5 2/3] firmware: xilinx: Add XilSEM firmware interface Rama devi Veggalam
2026-11-22  2:05 ` [PATCH v5 3/3] edac: Add Xilinx XilSEM error monitoring driver Rama devi Veggalam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1795313124-2138932-2-git-send-email-rama.devi.veggalam@amd.com \
    --to=rama.devi.veggalam@amd.com \
    --cc=bp@alien8.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=git@amd.com \
    --cc=james.morse@arm.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=michal.simek@amd.com \
    --cc=robh@kernel.org \
    --cc=rric@kernel.org \
    --cc=tony.luck@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®