From: George Hung <ghung.quanta@gmail.com>
To: linux-edac <linux-edac@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: benjaminfair@google.com, wak@google.com, Avi.Fishman@nuvoton.com,
tomer.maimon@nuvoton.com, Richard.Tung@quantatw.com,
Buddy.Huang@quantatw.com, Fran.Hsu@quantatw.com
Subject: [PATCH v1 2/2] dt-binding: edac: add NPCM ECC documentation
Date: Fri, 31 May 2019 19:03:52 +0800 [thread overview]
Message-ID: <20190531110352.30393-2-ghung.quanta@gmail.com> (raw)
In-Reply-To: <20190531110352.30393-1-ghung.quanta@gmail.com>
Add device tree documentation for Nuvoton BMC ECC
Signed-off-by: George Hung <ghung.quanta@gmail.com>
---
.../bindings/edac/npcm7xx-sdram-edac.txt | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
create mode 100644 Documentation/devicetree/bindings/edac/npcm7xx-sdram-edac.txt
diff --git a/Documentation/devicetree/bindings/edac/npcm7xx-sdram-edac.txt b/Documentation/devicetree/bindings/edac/npcm7xx-sdram-edac.txt
new file mode 100644
index 000000000000..dd4dac59a5bd
--- /dev/null
+++ b/Documentation/devicetree/bindings/edac/npcm7xx-sdram-edac.txt
@@ -0,0 +1,17 @@
+Nuvoton NPCM7xx SoC EDAC device driver
+
+The Nuvoton NPCM7xx SoC supports DDR4 memory with/without ECC and the driver
+uses the EDAC framework to implement the ECC detection and corrtection.
+
+Required properties:
+- compatible: should be "nuvoton,npcm7xx-sdram-edac"
+- reg: Memory controller register set should be <0xf0824000 0x1000>
+- interrupts: should be MC interrupt #25
+
+Example:
+
+ mc: memory-controller@f0824000 {
+ compatible = "nuvoton,npcm7xx-sdram-edac";
+ reg = <0xf0824000 0x1000>;
+ interrupts = <0 25 4>;
+ };
--
2.21.0
prev parent reply other threads:[~2019-05-31 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 11:03 [PATCH v1 1/2] edac: npcm: Add Nuvoton NPCM7xx EDAC driver George Hung
2019-05-31 11:03 ` George Hung [this message]
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=20190531110352.30393-2-ghung.quanta@gmail.com \
--to=ghung.quanta@gmail.com \
--cc=Avi.Fishman@nuvoton.com \
--cc=Buddy.Huang@quantatw.com \
--cc=Fran.Hsu@quantatw.com \
--cc=Richard.Tung@quantatw.com \
--cc=benjaminfair@google.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomer.maimon@nuvoton.com \
--cc=wak@google.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).