[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9b7676f4-4922-40cc-98b2-67224c901773@gmail.com>
Date: Wed, 13 Dec 2023 16:49:02 +0100
From: Rafał Miłecki <zajec5@...il.com>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Rafał Miłecki <rafal@...ecki.pl>,
Christian Marangi <ansuelsmth@...il.com>
Subject: Re: [PATCH 1/2] dt-bindings: nvmem: add "data-size" property
On 13.12.2023 16:47, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@...ecki.pl>
>
> Allow specifying NVMEM device content size in case it differs from
> device total size.
>
> Cc: Christian Marangi <ansuelsmth@...il.com>
> Signed-off-by: Rafał Miłecki <rafal@...ecki.pl>
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:
Powered by blists - more mailing lists