From: Sherry Sun <sherry.sun@nxp.com>
To: robh+dt@kernel.org, krzk+dt@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, manish.narani@xilinx.com,
michal.simek@xilinx.com, dinguyen@kernel.org, bp@suse.de
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-imx@nxp.com
Subject: [PATCH V2 2/2] arm64: dts: imx8mp: add ddr controller node to support EDAC on imx8mp
Date: Mon, 21 Mar 2022 15:51:31 +0800 [thread overview]
Message-ID: <20220321075131.17811-3-sherry.sun@nxp.com> (raw)
In-Reply-To: <20220321075131.17811-1-sherry.sun@nxp.com>
i.MX8MP use synopsys V3.70a ddr controller IP, so add edac support
for i.MX8MP based on "snps,ddrc-3.80a" synopsys edac driver.
Signed-off-by: Sherry Sun <sherry.sun@nxp.com>
---
arch/arm64/boot/dts/freescale/imx8mp.dtsi | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/imx8mp.dtsi b/arch/arm64/boot/dts/freescale/imx8mp.dtsi
index 3f8703f3ba5b..f39da2b12ddc 100644
--- a/arch/arm64/boot/dts/freescale/imx8mp.dtsi
+++ b/arch/arm64/boot/dts/freescale/imx8mp.dtsi
@@ -902,6 +902,12 @@
interrupt-parent = <&gic>;
};
+ edacmc: memory-controller@3d400000 {
+ compatible = "snps,ddrc-3.80a";
+ reg = <0x3d400000 0x400000>;
+ interrupts = <GIC_SPI 147 IRQ_TYPE_LEVEL_HIGH>;
+ };
+
ddr-pmu@3d800000 {
compatible = "fsl,imx8mp-ddr-pmu", "fsl,imx8m-ddr-pmu";
reg = <0x3d800000 0x400000>;
--
2.17.1
next prev parent reply other threads:[~2022-03-21 7:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 7:51 [PATCH V2 0/2] add ddr controller node to support EDAC on imx8mp Sherry Sun
2022-03-21 7:51 ` [PATCH V2 1/2] dt-bindings: memory: snps,ddrc-3.80a compatible also need interrupts Sherry Sun
2022-03-21 8:10 ` Krzysztof Kozlowski
2022-04-04 17:08 ` (subset) " Krzysztof Kozlowski
2022-03-21 7:51 ` Sherry Sun [this message]
2022-03-21 8:09 ` [PATCH V2 2/2] arm64: dts: imx8mp: add ddr controller node to support EDAC on imx8mp Krzysztof Kozlowski
2022-04-10 1:34 ` Shawn Guo
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=20220321075131.17811-3-sherry.sun@nxp.com \
--to=sherry.sun@nxp.com \
--cc=bp@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manish.narani@xilinx.com \
--cc=michal.simek@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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).