[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BY5PR12MB4258CAD5AA8BEFAAB444E4E3DB6B9@BY5PR12MB4258.namprd12.prod.outlook.com>
Date: Tue, 16 Aug 2022 12:43:22 +0000
From: "Potthuri, Sai Krishna" <sai.krishna.potthuri@....com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Michal Simek <michal.simek@...inx.com>,
Borislav Petkov <bp@...en8.de>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Tony Luck <tony.luck@...el.com>,
James Morse <james.morse@....com>,
Robert Richter <rric@...nel.org>
CC: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"saikrishna12468@...il.com" <saikrishna12468@...il.com>,
"git (AMD-Xilinx)" <git@....com>,
Shubhrajyoti Datta <shubhrajyoti.datta@...inx.com>
Subject: RE: [PATCH 1/2] dt-bindings: edac: Add bindings for Xilinx ZynqMP OCM
Hi Krzysztof,
> -----Original Message-----
> From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
> Sent: Tuesday, August 16, 2022 1:29 PM
> To: Potthuri, Sai Krishna <sai.krishna.potthuri@....com>; Rob Herring
> <robh+dt@...nel.org>; Krzysztof Kozlowski
> <krzysztof.kozlowski+dt@...aro.org>; Michal Simek
> <michal.simek@...inx.com>; Borislav Petkov <bp@...en8.de>; Mauro
> Carvalho Chehab <mchehab@...nel.org>; Tony Luck <tony.luck@...el.com>;
> James Morse <james.morse@....com>; Robert Richter <rric@...nel.org>
> Cc: devicetree@...r.kernel.org; linux-arm-kernel@...ts.infradead.org; linux-
> kernel@...r.kernel.org; linux-edac@...r.kernel.org;
> saikrishna12468@...il.com; git (AMD-Xilinx) <git@....com>; Shubhrajyoti
> Datta <shubhrajyoti.datta@...inx.com>
> Subject: Re: [PATCH 1/2] dt-bindings: edac: Add bindings for Xilinx ZynqMP
> OCM
>
> On 16/08/2022 10:32, Sai Krishna Potthuri wrote:
> > From: Shubhrajyoti Datta <shubhrajyoti.datta@...inx.com>
> >
> > Add bindings for Xilinx ZynqMP OCM controller.
> >
> > Signed-off-by: Shubhrajyoti Datta <shubhrajyoti.datta@...inx.com>
> > Signed-off-by: Sai Krishna Potthuri <sai.krishna.potthuri@....com>
> > ---
> > .../bindings/edac/xlnx,zynqmp-ocmc.yaml | 41 +++++++++++++++++++
> > 1 file changed, 41 insertions(+)
> > create mode 100644
> > Documentation/devicetree/bindings/edac/xlnx,zynqmp-ocmc.yaml
> >
> > diff --git
> > a/Documentation/devicetree/bindings/edac/xlnx,zynqmp-ocmc.yaml
> > b/Documentation/devicetree/bindings/edac/xlnx,zynqmp-ocmc.yaml
> > new file mode 100644
> > index 000000000000..9bcecaccade2
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/edac/xlnx,zynqmp-ocmc.yaml
> > @@ -0,0 +1,41 @@
> > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) %YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/edac/xlnx,zynqmp-ocmc.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Xilinx Zynqmp OCM EDAC driver
>
> s/EDAC driver//
> Is it a memory controller?
This driver is about Error Detection and Correction feature for OCM (On Chip
Memory) controller which supports ECC functionality.
>
> > +
> > +maintainers:
> > + - Shubhrajyoti Datta <shubhrajyoti.datta@....com>
> > + - Sai Krishna Potthuri <sai.krishna.potthuri@....com>
> > +
> > +description: |
> > + Xilinx ZynqMP OCM EDAC driver, it does reports the OCM ECC single
> > +bit errors
>
> The same. Describe the hardware, not the Linux driver or its subsystem.
I will fix in v2.
>
> > + that are corrected and double bit ecc errors that are detected by
> > + the OCM
>
> s/ecc/ECC/
I will fix in v2.
>
> > + ECC controller.
> > +
> > +properties:
> > + compatible:
> > + const: xlnx,zynqmp-ocmc-1.0
> > +
> > + reg:
> > + maxItems: 1
> > +
> > + interrupts:
> > + maxItems: 1
> > +
> > +required:
> > + - compatible
> > + - reg
> > + - interrupts
> > +
> > +unevaluatedProperties: false
> > +
> > +examples:
> > + - |
> > + memory-controller@...60000 {
> > + compatible = "xlnx,zynqmp-ocmc-1.0";
> > + reg = <0xff960000 0x1000>;
> > + interrupts = <0 10 4>;
>
> Isn't the interrupt using common flags? If so, use proper defines.
I will fix in v2.
Regards
Sai Krishna
>
> > + };
>
>
> Best regards,
> Krzysztof
Powered by blists - more mailing lists