From: Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Borislav Petkov <bp@alien8.de>, Tony Luck <tony.luck@intel.com>,
James Morse <james.morse@arm.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
Robert Richter <rric@kernel.org>,
"Shubhrajyoti Datta" <shubhrajyoti.datta@amd.com>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-edac@vger.kernel.org>
Cc: <git@amd.com>
Subject: [PATCH v4 0/5] EDAC: Versal NET: Add support for error notification
Date: Thu, 2 Jan 2025 23:14:29 +0530 [thread overview]
Message-ID: <20250102174434.17677-1-shubhrajyoti.datta@amd.com> (raw)
Adds support for the error notification.
Currently 20 errors has been tested.
This driver is receiving events over rpmsg.
It does not access the registers by itself instead the NMC
reads and sends the info by rpmsg
Also we register the edac once and it reports the errors for all the
events including the 8 DDRMC controllers. So while registering we give
the particulars of the 1st controller.
Changes in v4:
Update the compatible
align the example
Enhance the description for rproc
Update the compatible
Changes in v3:
make remove void
Changes in v2:
- Export the symbols for module compilation
- rename EDAC to memory controller
- update the compatible name
- Add remote proc handle
- Read the data width from the registers
- Remove the dwidth, rank and channel number the same is read from the RpMsg.
- remove reset
- Add the remote proc requests
- remove probe_once
- reorder the rpmsg registration
- the data width , rank and number of channel is read from message.
Shubhrajyoti Datta (5):
cdx: export the symbols
ras: export the log_non_standard_event
cdx: add DDRMC commands
dt-bindings: memory-controllers: Add support for Versal NET EDAC
EDAC: Versal NET: Add support for error notification
.../amd,versal-net-ddrmc5-1.0.yaml | 41 +
drivers/cdx/controller/mc_cdx_pcol.h | 16 +
drivers/cdx/controller/mcdi.c | 3 +
drivers/edac/Kconfig | 9 +
drivers/edac/Makefile | 1 +
drivers/edac/versalnet_rpmsg_edac.c | 1325 +++++++++++++++++
drivers/ras/ras.c | 1 +
7 files changed, 1396 insertions(+)
create mode 100644 Documentation/devicetree/bindings/memory-controllers/amd,versal-net-ddrmc5-1.0.yaml
create mode 100644 drivers/edac/versalnet_rpmsg_edac.c
--
2.17.1
next reply other threads:[~2025-01-02 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 17:44 Shubhrajyoti Datta [this message]
2025-01-02 17:44 ` [PATCH v4 1/5] cdx: export the symbols Shubhrajyoti Datta
2025-01-02 17:44 ` [PATCH v4 2/5] ras: export the log_non_standard_event Shubhrajyoti Datta
2025-01-02 17:44 ` [PATCH v4 3/5] cdx: add DDRMC commands Shubhrajyoti Datta
2025-01-02 17:44 ` [PATCH v4 4/5] dt-bindings: memory-controllers: Add support for Versal NET EDAC Shubhrajyoti Datta
2025-01-02 18:00 ` Krzysztof Kozlowski
2025-01-03 6:13 ` Shubhrajyoti Datta
2025-01-02 18:23 ` Rob Herring (Arm)
2025-01-02 17:44 ` [PATCH v4 5/5] EDAC: Versal NET: Add support for error notification Shubhrajyoti Datta
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=20250102174434.17677-1-shubhrajyoti.datta@amd.com \
--to=shubhrajyoti.datta@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@kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--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