[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <888120c8-f45c-ce4a-56e7-7b68c2014a68@linaro.org>
Date: Fri, 25 Feb 2022 13:30:30 +0000
From: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To: Rafał Miłecki <zajec5@...il.com>,
Rob Herring <robh+dt@...nel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
Florian Fainelli <f.fainelli@...il.com>,
Hauke Mehrtens <hauke@...ke-m.de>,
bcm-kernel-feedback-list@...adcom.com, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Rafał Miłecki <rafal@...ecki.pl>,
Rob Herring <robh@...nel.org>
Subject: Re: [PATCH V3 1/3] dt-bindings: nvmem: make "reg" property optional
On 18/02/2022 07:07, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@...ecki.pl>
>
> Most NVMEM providers have cells at hardcoded addresses however there are
> some exceptions. Some devices store cells layout in internal structs
> using custom formats.
>
> It's important to allow NVMEM consumers to still reference such NVMEM
> cells. Making "reg" optional allows defining NVMEM cells by their names
> only and using them with phandles.
>
> Signed-off-by: Rafał Miłecki <rafal@...ecki.pl>
> Reviewed-by: Rob Herring <robh@...nel.org>
Applied thanks,
--srini
> ---
> Documentation/devicetree/bindings/nvmem/nvmem.yaml | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/nvmem/nvmem.yaml b/Documentation/devicetree/bindings/nvmem/nvmem.yaml
> index 43ed7e32e5ac..3bb349c634cb 100644
> --- a/Documentation/devicetree/bindings/nvmem/nvmem.yaml
> +++ b/Documentation/devicetree/bindings/nvmem/nvmem.yaml
> @@ -60,9 +60,6 @@ patternProperties:
> description:
> Size in bit within the address range specified by reg.
>
> - required:
> - - reg
> -
> additionalProperties: true
>
> examples:
Powered by blists - more mailing lists