linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	s.hauer@pengutronix.de, kernel@pengutronix.de,
	festevam@gmail.com, linux-imx@nxp.com, aisheng.dong@nxp.com,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH V2 2/6] arm64: dts: imx8ulp: correct the scmi sram node name
Date: Mon, 5 Sep 2022 11:20:39 +0800	[thread overview]
Message-ID: <20220905032039.GG1728671@dragon> (raw)
In-Reply-To: <20220831142552.43393-3-peng.fan@oss.nxp.com>

On Wed, Aug 31, 2022 at 10:25:48PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
> 
> Follow sram/sram.yaml to update the sram node name.
> 
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
>  arch/arm64/boot/dts/freescale/imx8ulp.dtsi | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arm64/boot/dts/freescale/imx8ulp.dtsi b/arch/arm64/boot/dts/freescale/imx8ulp.dtsi
> index 8460a3cba107..7a88d7016b49 100644
> --- a/arch/arm64/boot/dts/freescale/imx8ulp.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx8ulp.dtsi
> @@ -112,7 +112,7 @@ sram@2201f000 {
>  		#size-cells = <1>;
>  		ranges = <0 0x0 0x2201f000 0x1000>;
>  
> -		scmi_buf: scmi-buf@0 {
> +		scmi_buf: scmi-sram-section@0 {

While the commit log mentions sram/sram.yaml, the binding doc says:

  $nodename:
    pattern: "^sram(@.*)?"

Does scmi-sram-section match the pattern?

Shawn

>  			compatible = "arm,scmi-shmem";
>  			reg = <0x0 0x400>;
>  		};
> -- 
> 2.37.1
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-09-05  4:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31 14:25 [PATCH V2 0/6] arm64: dts: imx8ulp: several updates Peng Fan (OSS)
2022-08-31 14:25 ` [PATCH V2 1/6] arm64: dts: imx8ulp: drop undocumented property in cgc Peng Fan (OSS)
2022-08-31 14:25 ` [PATCH V2 2/6] arm64: dts: imx8ulp: correct the scmi sram node name Peng Fan (OSS)
2022-09-05  3:20   ` Shawn Guo [this message]
2022-09-05  3:32     ` Peng Fan
2022-08-31 14:25 ` [PATCH V2 3/6] arm64: dts: imx8ulp: add #reset-cells for pcc Peng Fan (OSS)
2022-08-31 14:25 ` [PATCH V2 4/6] arm64: dts: imx8ulp: add pmu node Peng Fan (OSS)
2022-08-31 14:25 ` [PATCH V2 5/6] arm64: dts: imx8ulp: add mailbox node Peng Fan (OSS)
2022-08-31 14:25 ` [PATCH V2 6/6] arm64: dts: imx8ulp: increase the clock speed of LPSPI Peng Fan (OSS)
2022-09-05  3:39 ` [PATCH V2 0/6] arm64: dts: imx8ulp: several updates Shawn Guo

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=20220905032039.GG1728671@dragon \
    --to=shawnguo@kernel.org \
    --cc=aisheng.dong@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).