On Thu, Sep 7, 2023 at 4:40 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 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 | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/dtschema/schemas/memory.yaml b/dtschema/schemas/memory.yaml index 1d74410..1a48b1c 100644 --- a/dtschema/schemas/memory.yaml +++ b/dtschema/schemas/memory.yaml @@ -31,10 +31,21 @@ patternProperties:
numa-node-id: $ref: types.yaml#/definitions/uint32
description:
description: |
Why? '|' is not needed for any of these.
For the purpose of identification, each NUMA node is associated with a unique token known as a node id.
blank line between properties.
I can fix these up when applying.
ecc-detection-bits:default: 0description: |If present, this indicates the number of bits of memory error whichcan be detected and reported by the Error-Correction Code (ECC) memorysubsystem (typically 0, 1 or 2).ecc-correction-bits:default: 0description: |If present, this indicates the number of bits of memory error whichcan be corrected by the Error-Correction Code (ECC) memory subsystem(typically 0, 1 or 2).required: - device_type
-- 2.42.0.283.g2d96d420d3-goog