devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Simon Glass <sjg@chromium.org>
Cc: devicetree@vger.kernel.org,
	Maximilian Brune <maximilian.brune@9elements.com>,
	ron minnich <rminnich@gmail.com>, Tom Rini <trini@konsulko.com>,
	Dhaval Sharma <dhaval@rivosinc.com>,
	U-Boot Mailing List <u-boot@lists.denx.de>,
	Mark Rutland <mark.rutland@arm.com>,
	Yunhui Cui <cuiyunhui@bytedance.com>,
	linux-acpi@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
	Gua Guo <gua.guo@intel.com>,
	Lean Sheng Tan <sheng.tan@9elements.com>,
	Guo Dong <guo.dong@intel.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Chiu Chasel <chasel.chiu@intel.com>
Subject: Re: [PATCH v5 4/4] memory: Add ECC properties
Date: Thu, 7 Sep 2023 11:58:07 -0500	[thread overview]
Message-ID: <CAL_JsqKEbqUtWHpHXmiDSZBY7-Nw4-fLs23BEqomBevSDNBprQ@mail.gmail.com> (raw)
In-Reply-To: <20230830231758.2561402-4-sjg@chromium.org>

On Wed, Aug 30, 2023 at 6:18 PM Simon Glass <sjg@chromium.org> wrote:
>
> Some memories provide ECC detection and/or correction. For software which
> wants to check memory, it is helpful to see which regions provide this
> feature.
>
> Add this as a property of the /memory nodes, since it presumably follows
> the hardware-level memory system.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> Changes in v5:
> - Redo to make this property specific to ECC
> - Provide properties both for detection and correction
>
> Changes in v3:
> - Add new patch to update the /memory nodes
>
>  dtschema/schemas/memory.yaml | 30 ++++++++++++++++++++++++++++++
>  1 file changed, 30 insertions(+)
>
> diff --git a/dtschema/schemas/memory.yaml b/dtschema/schemas/memory.yaml
> index 1d74410..944aa9f 100644
> --- a/dtschema/schemas/memory.yaml
> +++ b/dtschema/schemas/memory.yaml
> @@ -34,7 +34,37 @@ patternProperties:
>          description:
>            For the purpose of identification, each NUMA node is associated with
>            a unique token known as a node id.
> +      ecc-detection:
> +        $ref: /schemas/types.yaml#/definitions/string
> +        enum:
> +          - none
> +          - single-bit
> +          - multi-bit
> +        description: |
> +          If present, this inidcates the type of memory errors which can be

typo

> +          detected and reported by the Error-Correction Code (ECC) memory
> +          subsystem:
>
> +            none       - No error detection is possible
> +            single-bit - Detects and reports single-bit ECC errors
> +            multi-bit  - Detects and reports multiple-bit ECC errors

I don't think 'multi' is specific enough. Perhaps this should be an
int instead with how many bits. (And '-bits' is a standard unit suffix
so a type isn't needed)

> +
> +          If not present, this is equivalent to 'none'.

Can be expressed as schema:

default: none

Though if that's the default why have it as a value? (It's fine though)

> +      ecc-correction:
> +        $ref: /schemas/types.yaml#/definitions/string
> +        enum:
> +          - none
> +          - single-bit
> +          - multi-bit
> +        description: |
> +          If present, this inidcates the type of memory errors which can be

typo

> +          corrected by the Error-Correction Code (ECC) memory subsystem:
> +
> +            none       - No error correction is possible
> +            single-bit - Corrects single-bit ECC errors
> +            multi-bit  - Corrects multiple-bit ECC errors
> +
> +          If not present, this is equivalent to 'none'.

One issue is with 2 properties nonsensical combinations are allowed.
Not really any way to handle that in the schema though.

Rob

  reply	other threads:[~2023-09-07 17:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 23:17 [PATCH v5 1/4] Add reserved-memory Simon Glass
2023-08-30 23:17 ` [PATCH v5 2/4] Bring in some other reserved-memory files Simon Glass
2023-08-30 23:17 ` [PATCH v5 3/4] schemas: Add some common reserved-memory usages Simon Glass
2023-09-05 21:44   ` Ard Biesheuvel
2023-09-06 14:34     ` Rob Herring
2023-09-06 14:53       ` Simon Glass
2023-09-06 16:08         ` Ard Biesheuvel
     [not found]           ` <CAPnjgZ1oGF0Ni3RhK4fv6mJk40YjqyFVJxt6FfS9AW2rkcs9iA@mail.gmail.com>
2023-09-07 13:31             ` Ard Biesheuvel
2023-09-07 13:56               ` Simon Glass
2023-09-07 14:12                 ` Ard Biesheuvel
2023-09-07 14:50                   ` Simon Glass
2023-09-07 15:07                     ` Ard Biesheuvel
2023-09-07 15:56                       ` Simon Glass
2023-09-07 16:19                         ` Ard Biesheuvel
2023-09-07 21:39                           ` Simon Glass
2023-09-07 15:43                 ` Rob Herring
2023-08-30 23:17 ` [PATCH v5 4/4] memory: Add ECC properties Simon Glass
2023-09-07 16:58   ` Rob Herring [this message]
2023-09-07 16:41 ` [PATCH v5 1/4] Add reserved-memory Rob Herring

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=CAL_JsqKEbqUtWHpHXmiDSZBY7-Nw4-fLs23BEqomBevSDNBprQ@mail.gmail.com \
    --to=robh@kernel.org \
    --cc=ardb@kernel.org \
    --cc=chasel.chiu@intel.com \
    --cc=cuiyunhui@bytedance.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dhaval@rivosinc.com \
    --cc=gua.guo@intel.com \
    --cc=guo.dong@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maximilian.brune@9elements.com \
    --cc=rminnich@gmail.com \
    --cc=sheng.tan@9elements.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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).