From: "Rafał Miłecki" <zajec5@gmail.com> To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, Rob Herring <robh+dt@kernel.org> Cc: "Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>, "Florian Fainelli" <f.fainelli@gmail.com>, "Hauke Mehrtens" <hauke@hauke-m.de>, bcm-kernel-feedback-list@broadcom.com, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl>, "Rob Herring" <robh@kernel.org> Subject: [PATCH V3 1/3] dt-bindings: nvmem: make "reg" property optional Date: Fri, 18 Feb 2022 08:07:27 +0100 [thread overview] Message-ID: <20220218070729.3256-2-zajec5@gmail.com> (raw) In-Reply-To: <20220218070729.3256-1-zajec5@gmail.com> From: Rafał Miłecki <rafal@milecki.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@milecki.pl> Reviewed-by: Rob Herring <robh@kernel.org> --- 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: -- 2.34.1
WARNING: multiple messages have this Message-ID (diff)
From: "Rafał Miłecki" <zajec5@gmail.com> To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, Rob Herring <robh+dt@kernel.org> Cc: "Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>, "Florian Fainelli" <f.fainelli@gmail.com>, "Hauke Mehrtens" <hauke@hauke-m.de>, bcm-kernel-feedback-list@broadcom.com, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl>, "Rob Herring" <robh@kernel.org> Subject: [PATCH V3 1/3] dt-bindings: nvmem: make "reg" property optional Date: Fri, 18 Feb 2022 08:07:27 +0100 [thread overview] Message-ID: <20220218070729.3256-2-zajec5@gmail.com> (raw) In-Reply-To: <20220218070729.3256-1-zajec5@gmail.com> From: Rafał Miłecki <rafal@milecki.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@milecki.pl> Reviewed-by: Rob Herring <robh@kernel.org> --- 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: -- 2.34.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-02-18 7:07 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-24 16:02 [PATCH 0/3] nvmem: allow specifying cells by just names in DT Rafał Miłecki 2022-01-24 16:02 ` Rafał Miłecki 2022-01-24 16:02 ` [PATCH 1/3] dt-bindings: nvmem: make "reg" property optional Rafał Miłecki 2022-01-24 16:02 ` Rafał Miłecki 2022-02-11 12:38 ` Rob Herring 2022-02-11 12:38 ` Rob Herring 2022-01-24 16:02 ` [PATCH 2/3] dt-bindings: nvmem: brcm,nvram: add NVMEM cell to example Rafał Miłecki 2022-01-24 16:02 ` [PATCH 2/3] dt-bindings: nvmem: brcm, nvram: " Rafał Miłecki 2022-02-11 12:45 ` [PATCH 2/3] dt-bindings: nvmem: brcm,nvram: " Rob Herring 2022-02-11 12:45 ` Rob Herring 2022-01-24 16:03 ` [PATCH 3/3] nvmem: core: add cell name based matching of DT cell nodes Rafał Miłecki 2022-01-24 16:03 ` Rafał Miłecki 2022-02-11 13:05 ` [PATCH V2 0/3] nvmem: allow specifying cells by just names in DT Rafał Miłecki 2022-02-11 13:05 ` Rafał Miłecki 2022-02-11 13:05 ` [PATCH V2 1/3] dt-bindings: nvmem: make "reg" property optional Rafał Miłecki 2022-02-11 13:05 ` Rafał Miłecki 2022-02-11 13:05 ` [PATCH V2 2/3] dt-bindings: nvmem: brcm,nvram: add NVMEM cell to example Rafał Miłecki 2022-02-11 13:05 ` [PATCH V2 2/3] dt-bindings: nvmem: brcm, nvram: " Rafał Miłecki 2022-02-17 23:58 ` Rob Herring 2022-02-17 23:58 ` [PATCH V2 2/3] dt-bindings: nvmem: brcm,nvram: " Rob Herring 2022-02-11 13:05 ` [PATCH V2 3/3] nvmem: core: add cell name based matching of DT cell nodes Rafał Miłecki 2022-02-11 13:05 ` Rafał Miłecki 2022-02-18 7:07 ` [PATCH V3 0/3] nvmem: allow specifying cells by just names in DT Rafał Miłecki 2022-02-18 7:07 ` Rafał Miłecki 2022-02-18 7:07 ` Rafał Miłecki [this message] 2022-02-18 7:07 ` [PATCH V3 1/3] dt-bindings: nvmem: make "reg" property optional Rafał Miłecki 2022-02-25 13:30 ` Srinivas Kandagatla 2022-02-25 13:30 ` Srinivas Kandagatla 2022-02-18 7:07 ` [PATCH V3 2/3] dt-bindings: nvmem: brcm,nvram: add basic NVMEM cells Rafał Miłecki 2022-02-18 7:07 ` Rafał Miłecki 2022-02-24 19:55 ` Rob Herring 2022-02-24 19:55 ` Rob Herring 2022-02-25 13:30 ` Srinivas Kandagatla 2022-02-25 13:30 ` Srinivas Kandagatla 2022-02-18 7:07 ` [PATCH V3 3/3] nvmem: core: add cell name based matching of DT cell nodes Rafał Miłecki 2022-02-18 7:07 ` Rafał Miłecki 2022-02-25 12:10 ` Srinivas Kandagatla 2022-02-25 12:10 ` Srinivas Kandagatla
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220218070729.3256-2-zajec5@gmail.com \ --to=zajec5@gmail.com \ --cc=bcm-kernel-feedback-list@broadcom.com \ --cc=devicetree@vger.kernel.org \ --cc=f.fainelli@gmail.com \ --cc=hauke@hauke-m.de \ --cc=krzysztof.kozlowski@canonical.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=rafal@milecki.pl \ --cc=robh+dt@kernel.org \ --cc=robh@kernel.org \ --cc=srinivas.kandagatla@linaro.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.