devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: devicetree@vger.kernel.org
Cc: Rob Herring <robh@kernel.org>, Ard Biesheuvel <ardb@kernel.org>,
	Chiu Chasel <chasel.chiu@intel.com>,
	U-Boot Mailing List <u-boot@lists.denx.de>,
	Gua Guo <gua.guo@intel.com>,
	linux-acpi@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
	Yunhui Cui <cuiyunhui@bytedance.com>,
	ron minnich <rminnich@gmail.com>, Tom Rini <trini@konsulko.com>,
	Lean Sheng Tan <sheng.tan@9elements.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Simon Glass <sjg@chromium.org>
Subject: [PATCH v3 2/2] memory: Add ECC property
Date: Tue, 22 Aug 2023 14:34:43 -0600	[thread overview]
Message-ID: <20230822203446.4111742-2-sjg@chromium.org> (raw)
In-Reply-To: <20230822203446.4111742-1-sjg@chromium.org>

Some memories provides ECC 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 v3:
- Add new patch to update the /memory nodes

 dtschema/schemas/memory.yaml | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/dtschema/schemas/memory.yaml b/dtschema/schemas/memory.yaml
index 1d74410..981af04 100644
--- a/dtschema/schemas/memory.yaml
+++ b/dtschema/schemas/memory.yaml
@@ -34,7 +34,14 @@ patternProperties:
         description:
           For the purpose of identification, each NUMA node is associated with
           a unique token known as a node id.
-
+      attr:
+        $ref: /schemas/types.yaml#/definitions/string-array
+        description: |
+          Attributes possessed by this memory region:
+
+            "single-bit-ecc" - supports single-bit ECC
+            "multi-bit-ecc" - supports multiple-bit ECC
+            "no-ecc" - non-ECC memory
 
     required:
       - device_type
-- 
2.42.0.rc1.204.g551eb34607-goog


  reply	other threads:[~2023-08-22 20:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22 20:34 [PATCH v3 1/2] schemas: Add a schema for memory map Simon Glass
2023-08-22 20:34 ` Simon Glass [this message]
2023-08-23  8:58 ` Mark Rutland
2023-08-23 14:23   ` Ard Biesheuvel
2023-08-23 20:04     ` Simon Glass
2023-08-24  9:10       ` Ard Biesheuvel
2023-08-29 16:01         ` Simon Glass
2023-08-29 19:17         ` Simon Glass
2023-08-29 21:32           ` Ard Biesheuvel
2023-08-30 21:10             ` Simon Glass
2023-08-31 12:28               ` Ard Biesheuvel
2023-08-31 19:02                 ` Simon Glass
2023-08-31 21:47                   ` Ard Biesheuvel
2023-08-31 22:17                     ` Simon Glass
2023-08-31 22:39                       ` Ard Biesheuvel
2023-09-01  1:12                         ` Simon Glass
2023-09-01 10:48                           ` Ard Biesheuvel
2023-09-01 11:54                             ` Simon Glass

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=20230822203446.4111742-2-sjg@chromium.org \
    --to=sjg@chromium.org \
    --cc=ardb@kernel.org \
    --cc=chasel.chiu@intel.com \
    --cc=cuiyunhui@bytedance.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gua.guo@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rminnich@gmail.com \
    --cc=robh@kernel.org \
    --cc=sheng.tan@9elements.com \
    --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).