From: Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>
To: <linux-edac@vger.kernel.org>
Cc: <git@amd.com>, <devicetree@vger.kernel.org>,
<sai.krishna.potthuri@amd.com>, <krzysztof.kozlowski@linaro.org>,
<robh+dt@kernel.org>, <conor+dt@kernel.org>, <bp@alien8.de>,
<tony.luck@intel.com>, <james.morse@arm.com>,
<mchehab@kernel.org>, <rric@kernel.org>, <michal.simek@amd.com>
Subject: [PATCH v8 0/2] edac: xilinx: Added EDAC support for Xilinx DDR controller
Date: Fri, 4 Aug 2023 17:49:22 +0530 [thread overview]
Message-ID: <20230804121924.18615-1-shubhrajyoti.datta@amd.com> (raw)
The integrated DDR Memory Controllers (DDRMCs) support both DDR4 and
LPDDR4/4X memory interfaces. It has four programmable NoC interface
ports and is designed to handle multiple streams of traffic.
Optional external interface reliability include ECC error
detection/correction and command address parity.
Adding edac support for DDR Memory controller.
Changes in v8:
remove disabling all interrupts
Changes in v7:
Update the subject to add memory-controllers instead of edac
Update the message
Clear status after handling the error
At probe disable all the unrequested interrupts.
Alphabetically sorted diff
Rename unCorrectable to uncorrectable
Use mask0 for GENMASK(0,5)
Add a processbit function
Changes in v6:
Fix the warn.
Changes in v5:
Update subject
Changes in v4:
Update the reviewed by tag
Update the subject
rename the driver file.
fix the debugfs file.
fix unneeded capitalisation.
refactor code
Changes in v3:
Rebased and resent.
Changes in v2:
remove edac from compatible
Update the description
update the ddrmc_base and ddrmc_noc_base names
Update a missed out file
remove edac from compatible name
rename ddrmc_noc_base and ddrmc_base
Shubhrajyoti Datta (2):
dt-bindings: memory-controllers: Add support for Xilinx Versal EDAC
for DDRMC
EDAC/versal: Add a Xilinx Versal memory controller driver
.../xlnx,versal-ddrmc-edac.yaml | 57 +
MAINTAINERS | 7 +
drivers/edac/Kconfig | 11 +
drivers/edac/Makefile | 1 +
drivers/edac/versal_edac.c | 1065 +++++++++++++++++
include/linux/firmware/xlnx-zynqmp.h | 12 +
6 files changed, 1153 insertions(+)
create mode 100644 Documentation/devicetree/bindings/memory-controllers/xlnx,versal-ddrmc-edac.yaml
create mode 100644 drivers/edac/versal_edac.c
--
2.17.1
next reply other threads:[~2023-08-04 12:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 12:19 Shubhrajyoti Datta [this message]
2023-08-04 12:19 ` [PATCH v8 1/2] dt-bindings: memory-controllers: Add support for Xilinx Versal EDAC for DDRMC Shubhrajyoti Datta
2023-08-04 12:19 ` [PATCH v8 2/2] EDAC/versal: Add a Xilinx Versal memory controller driver Shubhrajyoti Datta
2023-09-19 17:03 ` Borislav Petkov
2023-09-22 12:41 ` Datta, Shubhrajyoti
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=20230804121924.18615-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=krzysztof.kozlowski@linaro.org \
--cc=linux-edac@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=michal.simek@amd.com \
--cc=robh+dt@kernel.org \
--cc=rric@kernel.org \
--cc=sai.krishna.potthuri@amd.com \
--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;
as well as URLs for NNTP newsgroup(s).