On 13.12.2023 16:47, Rafał Miłecki wrote:
From: Rafał Miłecki <rafal@xxxxxxxxxx> Allow specifying NVMEM device content size in case it differs from device total size. Cc: Christian Marangi <ansuelsmth@xxxxxxxxx> Signed-off-by: Rafał Miłecki <rafal@xxxxxxxxxx>
I forgot to link Rob's comment where he suggested we may need such a property: https://patchwork.ozlabs.org/comment/3154781/ Let's now see if I got it right.
--- Documentation/devicetree/bindings/nvmem/nvmem.yaml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Documentation/devicetree/bindings/nvmem/nvmem.yaml b/Documentation/devicetree/bindings/nvmem/nvmem.yaml index 4fd015d402ce..095aed4250de 100644 --- a/Documentation/devicetree/bindings/nvmem/nvmem.yaml +++ b/Documentation/devicetree/bindings/nvmem/nvmem.yaml @@ -26,6 +26,13 @@ properties: "#size-cells": const: 1+ data-size:+ $ref: /schemas/types.yaml#/definitions/uint32 + description: + NVMEM device actual data (content) size. It may be need to be specified + if it differs by design from the total NVMEM device size and it's + impossible to determine it on runtime. + read-only: $ref: /schemas/types.yaml#/definitions/flag description:
