linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Dhananjay Kangude <dkangude@cadence.com>
Cc: linux-edac@vger.kernel.org, bp@alien8.de, mchehab@kernel.org,
	tony.luck@intel.com, james.morse@arm.com,
	linux-kernel@vger.kernel.org, mparab@cadence.com,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: edac: Add cadence ddr mc support
Date: Tue, 14 Apr 2020 18:49:47 -0500	[thread overview]
Message-ID: <20200414234947.GA24554@bogus> (raw)
In-Reply-To: <20200406131341.1253-2-dkangude@cadence.com>

On Mon, Apr 06, 2020 at 03:13:40PM +0200, Dhananjay Kangude wrote:
> Add documentation for cadence ddr memory controller EDAC DTS bindings
> 
> Signed-off-by: Dhananjay Kangude <dkangude@cadence.com>
> ---
>  .../devicetree/bindings/edac/cdns,ddr-edac.yaml    |   47 ++++++++++++++++++++
>  1 files changed, 47 insertions(+), 0 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/edac/cdns,ddr-edac.yaml
> 
> diff --git a/Documentation/devicetree/bindings/edac/cdns,ddr-edac.yaml b/Documentation/devicetree/bindings/edac/cdns,ddr-edac.yaml
> new file mode 100644
> index 0000000..30ea757
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/edac/cdns,ddr-edac.yaml
> @@ -0,0 +1,47 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/edac/cdns,ddr-edac.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Cadence DDR IP with ECC support (EDAC)
> +
> +description:
> +  This binding describes the Cadence DDR/LPDDR IP with ECC feature enabled
> +  to detect and correct CE/UE errors.
> +
> +maintainers:
> +  - Dhananjay Kangdue <dkangude@cadence.com>
> +
> +properties:
> +  compatible:
> +    enum:
> +      - cdns,ddr4-mc

Surely there's more than 1 version?

> +
> +  reg:
> +    minItems: 1
> +    maxItems: 2
> +    items:
> +      - description:
> +          Register block of DDR/LPDDR apb registers up to mapped area.
> +          Mapped area contains the register set for memory controller,
> +          phy and PI module register set doesn't part of this mapping.

doesn't part of this mapping?

Need a description for the 2nd region.

> +
> +  interrupts:
> +    maxItems: 1
> +
> +required:
> +  - compatible
> +  - reg
> +  - interrupts
> +
> +additionalProperties: false
> +
> +examples:
> +  - |
> +    edac: edac@fd100000 {

memory-controller@

> +        compatible = "cdns,ddr4-mc-edac";

Doesn't match.

> +        reg = <0xfd100000 0x4000>;
> +        interrupts = <0x00 0x01 0x04>;
> +    };
> +...
> -- 
> 1.7.1
> 

  reply	other threads:[~2020-04-14 23:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 13:13 [PATCH v3 0/2] Add EDAC support for Cadence ddr controller Dhananjay Kangude
2020-04-06 13:13 ` [PATCH v3 1/2] dt-bindings: edac: Add cadence ddr mc support Dhananjay Kangude
2020-04-14 23:49   ` Rob Herring [this message]
2020-04-15 14:54     ` Dhananjay Vilasrao Kangude
2020-04-06 13:13 ` [PATCH v3 2/2] EDAC/Cadence:Add EDAC driver for cadence memory controller Dhananjay Kangude

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=20200414234947.GA24554@bogus \
    --to=robh@kernel.org \
    --cc=bp@alien8.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dkangude@cadence.com \
    --cc=james.morse@arm.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=mparab@cadence.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).