devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: devicetree@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
	Rob Herring <robh@kernel.org>,
	Lean Sheng Tan <sheng.tan@9elements.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Dhaval Sharma <dhaval@rivosinc.com>,
	Maximilian Brune <maximilian.brune@9elements.com>,
	Yunhui Cui <cuiyunhui@bytedance.com>,
	Guo Dong <guo.dong@intel.com>, Tom Rini <trini@konsulko.com>,
	ron minnich <rminnich@gmail.com>, Gua Guo <gua.guo@intel.com>,
	Chiu Chasel <chasel.chiu@intel.com>,
	linux-acpi@vger.kernel.org,
	U-Boot Mailing List <u-boot@lists.denx.de>,
	Ard Biesheuvel <ardb@kernel.org>, Simon Glass <sjg@chromium.org>
Subject: [PATCH v7 1/2] schemas: memory: Add ECC properties
Date: Tue, 26 Sep 2023 13:42:38 -0600	[thread overview]
Message-ID: <20230926194242.2732127-1-sjg@chromium.org> (raw)

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 v7:
- Drop unnecessary |
- Add a blank line between properties

Changes in v6:
- Use a number of bits instead of a string property
- Fix inidcates typo

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 | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/dtschema/schemas/memory.yaml b/dtschema/schemas/memory.yaml
index 1d74410..b3bf3c9 100644
--- a/dtschema/schemas/memory.yaml
+++ b/dtschema/schemas/memory.yaml
@@ -35,6 +35,19 @@ patternProperties:
           For the purpose of identification, each NUMA node is associated with
           a unique token known as a node id.
 
+      ecc-detection-bits:
+        default: 0
+        description: |
+          If present, this indicates the number of bits of memory error which
+          can be detected and reported by the Error-Correction Code (ECC) memory
+          subsystem (typically 0, 1 or 2).
+
+      ecc-correction-bits:
+        default: 0
+        description: |
+          If present, this indicates the number of bits of memory error which
+          can be corrected by the Error-Correction Code (ECC) memory subsystem
+          (typically 0, 1 or 2).
 
     required:
       - device_type
-- 
2.42.0.515.g380fc7ccd1-goog


             reply	other threads:[~2023-09-26 19:42 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26 19:42 Simon Glass [this message]
2023-09-26 19:42 ` [PATCH v7 2/2] schemas: Add some common reserved-memory usages Simon Glass
2023-10-02 17:53   ` Simon Glass
2023-10-06 17:33     ` Ard Biesheuvel
2023-10-06 18:17       ` Simon Glass
2023-10-06 22:59         ` Ard Biesheuvel
2023-10-07  0:03           ` Simon Glass
2023-10-09 20:14             ` Simon Glass
2023-10-11 20:40             ` Ard Biesheuvel
2023-10-13 20:42             ` Rob Herring
2023-10-13 21:09               ` Simon Glass
2023-10-16 16:50                 ` Rob Herring
2023-10-16 21:54                   ` Simon Glass
2023-10-31 15:56                     ` Simon Glass
2023-11-07 16:57                       ` Simon Glass
2023-11-07 18:07                       ` Rob Herring
2023-11-08 11:38                         ` Ard Biesheuvel
2023-11-08 13:57                           ` Rob Herring
2023-11-08 14:20                             ` Ard Biesheuvel
2023-11-10 18:20   ` Chiu, Chasel
2023-11-11 11:03     ` Ard Biesheuvel
2023-11-13 18:09       ` Chiu, Chasel
2023-11-21  2:12         ` Simon Glass
2023-11-21 16:41           ` Ard Biesheuvel
2023-11-21 18:34             ` Chiu, Chasel
2023-11-21 18:37               ` Chiu, Chasel
2023-11-28 18:07                 ` Ard Biesheuvel
2023-11-28 20:30                   ` Chiu, Chasel
2023-12-11 17:52                     ` Simon Glass
2023-12-20  4:46                       ` Simon Glass
2023-12-21 14:30                     ` Ard Biesheuvel
2023-12-21 16:50                       ` Chiu, Chasel
2023-12-22 12:47                         ` Ard Biesheuvel
2023-12-22 19:52                           ` Chiu, Chasel
2024-01-03 15:22                             ` Ard Biesheuvel
2024-01-04  0:25                               ` Chiu, Chasel
2024-01-04  8:43                                 ` Ard Biesheuvel
2024-01-04 17:53                                   ` Chiu, Chasel
2024-01-16 14:34                                     ` Ard Biesheuvel
2024-01-03 16:00                           ` Rob Herring
2024-01-03 19:36                             ` Chiu, Chasel
2024-01-03 20:54                             ` Simon Glass
2023-10-09 19:22 ` [PATCH v7 1/2] schemas: memory: Add ECC properties Simon Glass
2023-10-16 19:57 ` Rob Herring
2023-10-16 21: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=20230926194242.2732127-1-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=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=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).