aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRafał Miłecki <rafal@milecki.pl>2022-02-25 17:58:21 +0000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2022-03-18 14:08:36 +0100
commit82a05d81d82bbe00f58be6c32ec57a59e07e0c05 (patch)
treea3910fcdbef1780c86c7a9568838f8a4bb7e9d0f
parentnvmem: brcm_nvram: parse NVRAM content into NVMEM cells (diff)
downloadlinux-dev-82a05d81d82bbe00f58be6c32ec57a59e07e0c05.tar.xz
linux-dev-82a05d81d82bbe00f58be6c32ec57a59e07e0c05.zip
dt-bindings: nvmem: make "reg" property optional
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. Reviewed-by: Rob Herring <robh@kernel.org> Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> Link: https://lore.kernel.org/r/20220225175822.8293-4-srinivas.kandagatla@linaro.org Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-rw-r--r--Documentation/devicetree/bindings/nvmem/nvmem.yaml3
1 files changed, 0 insertions, 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: