From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Praveen Teja Kundanala <praveen.teja.kundanala@amd.com>,
srinivas.kandagatla@linaro.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
michal.simek@amd.com, praveent@amd.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 3/5] arm64: zynqmp: Add ZynqnMP nvmem nodes
Date: Thu, 19 Oct 2023 11:27:41 +0200 [thread overview]
Message-ID: <1fa867b2-3930-4ff3-90cd-022d855036c7@linaro.org> (raw)
In-Reply-To: <20231019060651.23341-4-praveen.teja.kundanala@amd.com>
On 19/10/2023 08:06, Praveen Teja Kundanala wrote:
> Add nvmem DT nodes for ZynqMP SOC
>
> Signed-off-by: Praveen Teja Kundanala <praveen.teja.kundanala@amd.com>
> ---
> arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 59 +++++++++++++++++++++++++-
> 1 file changed, 57 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi b/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
> index b61fc99cd911..b7433e6b9d6c 100644
> --- a/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
> +++ b/arch/arm64/boot/dts/xilinx/zynqmp.dtsi
> @@ -194,14 +194,69 @@ zynqmp_power: zynqmp-power {
> mbox-names = "tx", "rx";
> };
>
> - nvmem_firmware {
> + nvmem-firmware {
Node names should be generic. See also an explanation and list of
examples (not exhaustive) in DT specification:
https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
> compatible = "xlnx,zynqmp-nvmem-fw";
It does not look like you tested the DTS against bindings. Please run
`make dtbs_check W=1` (see
Documentation/devicetree/bindings/writing-schema.rst or
https://www.linaro.org/blog/tips-and-tricks-for-validating-devicetree-sources-with-the-devicetree-schema/
for instructions).
> #address-cells = <1>;
> #size-cells = <1>;
>
> - soc_revision: soc_revision@0 {
> + soc_revision: soc-revision@0 {
> reg = <0x0 0x4>;
> };
Wasn't this fixed already by Michal?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-10-19 9:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 6:06 [PATCH V2 0/5] Add ZynqMP efuse access support Praveen Teja Kundanala
2023-10-19 6:06 ` [PATCH V2 1/5] firmware: xilinx: Add ZynqMP efuse access API Praveen Teja Kundanala
2023-10-19 6:06 ` [PATCH V2 2/5] dt-bindings: nvmem: Convert xlnx,zynqmp-nvmem.txt to yaml Praveen Teja Kundanala
2023-10-19 9:26 ` Krzysztof Kozlowski
2023-10-19 10:35 ` Kundanala, Praveen Teja
2023-10-19 6:06 ` [PATCH V2 3/5] arm64: zynqmp: Add ZynqnMP nvmem nodes Praveen Teja Kundanala
2023-10-19 9:27 ` Krzysztof Kozlowski [this message]
2023-10-19 10:32 ` Kundanala, Praveen Teja
2023-10-20 7:23 ` Michal Simek
2023-10-19 6:06 ` [PATCH V2 4/5] nvmem: zynqmp_nvmem: Add support to access efuse Praveen Teja Kundanala
2023-10-19 6:06 ` [PATCH V2 5/5] MAINTAINERS: Add maintainers for ZynqMP NVMEM driver Praveen Teja Kundanala
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=1fa867b2-3930-4ff3-90cd-022d855036c7@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=praveen.teja.kundanala@amd.com \
--cc=praveent@amd.com \
--cc=robh+dt@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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®