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 v4 0/3] EDAC/versal: Add XilSEM CRAM/NPI error monitoring support
Date: Wed, 21 Oct 2026 18:27:19 +0530 [thread overview]
Message-ID: <1792587442-2794880-1-git-send-email-rama.devi.veggalam@amd.com> (raw)
Add support for XilSEM (Xilinx Soft Error Mitigation) to
the existing versal_edac driver. XilSEM runs as part of the Platform
Loader and Manager (PLM) on the PMC and monitors Configuration RAM
(CRAM) and the NoC Programming Interface (NPI) for correctable and
uncorrectable errors. It is registered as a second, independent EDAC
device alongside the existing DDR memory-controller (DDRMC) device,
using a new "xlnx,versal-xilsem" compatible string on the same
driver module.
Changes in this series:
- Extend the devicetree binding with the new compatible string.
- Add the firmware (EEMI) interface and error-event node ID/
masks XilSEM uses to report status.
- Add the driver support: probe/remove, event callback, sysfs
attributes, and their ABI documentation, bundled together in one
patch so the sysfs interface and its documentation land in the same
commit.
Rama devi Veggalam (3):
dt-bindings: edac: xlnx,versal-ddrmc: Add xlnx,versal-xilsem
compatible
firmware: xilinx: Add XilSEM firmware interface
edac: xilinx: Add XilSEM CRAM/NPI error monitoring support
.../ABI/testing/sysfs-devices-versal-edac | 286 +++++
.../memory-controllers/xlnx,versal-ddrmc-edac.yaml | 64 +-
MAINTAINERS | 5 +
drivers/edac/Kconfig | 17 +-
drivers/edac/versal_edac.c | 1276 +++++++++++++++++++-
drivers/edac/xsem_edac.h | 219 ++++
drivers/firmware/xilinx/Makefile | 2 +-
drivers/firmware/xilinx/zynqmp-sem.c | 229 ++++
drivers/soc/xilinx/xlnx_event_manager.c | 16 +-
include/linux/firmware/xlnx-zynqmp-sem.h | 196 +++
include/linux/firmware/xlnx-zynqmp.h | 50 +
11 files changed, 2328 insertions(+), 32 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-devices-versal-edac
create mode 100644 drivers/edac/xsem_edac.h
create mode 100644 drivers/firmware/xilinx/zynqmp-sem.c
create mode 100644 include/linux/firmware/xlnx-zynqmp-sem.h
--
1.9.5
next reply other threads:[~2026-10-21 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 12:57 Rama devi Veggalam [this message]
2026-10-21 12:57 ` [PATCH v4 1/3] dt-bindings: edac: xlnx,versal-ddrmc: Add xlnx,versal-xilsem compatible Rama devi Veggalam
2026-10-21 12:57 ` [PATCH v4 2/3] firmware: xilinx: Add XilSEM firmware interface Rama devi Veggalam
2026-10-21 12:57 ` [PATCH v4 3/3] edac: xilinx: Add XilSEM CRAM/NPI error monitoring support 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=1792587442-2794880-1-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®