[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0c90f9376c0e425c9a226379f7e5bfad@quantatw.com>
Date: Tue, 9 Jul 2019 09:48:59 +0000
From: George Hung (洪忠敬) <George.Hung@...ntatw.com>
To: Rob Herring <robh@...nel.org>, George Hung <ghung.quanta@...il.com>
CC: Mark Rutland <mark.rutland@....com>,
Linus Walleij <linus.walleij@...aro.org>,
Tali Perry <tali.perry1@...il.com>,
"paulmck@...ux.ibm.com" <paulmck@...ux.ibm.com>,
"wak@...gle.com" <wak@...gle.com>,
"benjaminfair@...gle.com" <benjaminfair@...gle.com>,
"openbmc@...ts.ozlabs.org" <openbmc@...ts.ozlabs.org>,
"tomer.maimon@...oton.com" <tomer.maimon@...oton.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Borislav Petkov <bp@...en8.de>,
"Avi.Fishman@...oton.com" <Avi.Fishman@...oton.com>,
"Jonathan Cameron" <Jonathan.Cameron@...wei.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
linux-edac <linux-edac@...r.kernel.org>,
"Patrick Venture" <venture@...gle.com>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
James Morse <james.morse@....com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"davem@...emloft.net" <davem@...emloft.net>
Subject: RE: [PATCH 5.2 v2 2/2] dt-binding: edac: add NPCM ECC documentation
Hi Rob,
> -----Original Message-----
> From: openbmc
> [mailto:openbmc-bounces+george.hung=quantatw.com@...ts.ozlabs.org] On
> Behalf Of Rob Herring
> Sent: Tuesday, July 09, 2019 9:41 AM
> To: George Hung
> Cc: Mark Rutland; Linus Walleij; Tali Perry; paulmck@...ux.ibm.com;
> wak@...gle.com; benjaminfair@...gle.com; openbmc@...ts.ozlabs.org;
> tomer.maimon@...oton.com; devicetree@...r.kernel.org; Borislav Petkov;
> Avi.Fishman@...oton.com; Jonathan Cameron; Mauro Carvalho Chehab;
> linux-edac; Patrick Venture; Nicolas Ferre; linux-kernel; James Morse; Greg
> Kroah-Hartman; davem@...emloft.net
> Subject: Re: [PATCH 5.2 v2 2/2] dt-binding: edac: add NPCM ECC
> documentation
>
> On Wed, Jun 05, 2019 at 10:12:53PM +0800, George Hung wrote:
> > Add device tree documentation for Nuvoton BMC ECC
> >
> > Signed-off-by: George Hung <ghung.quanta@...il.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"
>
> Is this for the whole SDRAM controller or just ECC related registers?
> In the former case, the naming should just reflect the block name and not a
> Linux term.
Sorry for confused naming, the address space is for the whole memory controller registers indeed,
but the driver only uses the ECC related registers.
Should I change the name to "nuvoton,npcm7xx-edac" ?
>
> > +- reg: Memory controller register set should be <0xf0824000
> 0x1000>
> > +- interrupts: should be MC interrupt #25
> > +
> > +Example:
> > +
> > + mc: memory-controller@...24000 {
> > + compatible = "nuvoton,npcm7xx-sdram-edac";
> > + reg = <0xf0824000 0x1000>;
> > + interrupts = <0 25 4>;
> > + };
> > --
> > 2.21.0
> >
Powered by blists - more mailing lists