linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: imx27-eukrea-cpuimx27: Remove 'simple-bus' from clocks node
Date: Mon, 29 Jan 2018 14:36:11 +0800	[thread overview]
Message-ID: <20180129063610.GA26461@dragon> (raw)
In-Reply-To: <1514391804-9518-2-git-send-email-festevam@gmail.com>

On Wed, Dec 27, 2017 at 02:23:24PM -0200, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@nxp.com>
> 
> clock node should not have a 'simple-bus' compatible string, so remove it
> in order to fix the following build warning with W=1:
> 
> arch/arm/boot/dts/imx27-eukrea-mbimxsd27-baseboard.dtb: Warning (simple_bus_reg): Node /clocks/osc26m missing or empty reg/ranges property
> 
> Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
> ---
>  arch/arm/boot/dts/imx27-eukrea-cpuimx27.dtsi | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/arch/arm/boot/dts/imx27-eukrea-cpuimx27.dtsi b/arch/arm/boot/dts/imx27-eukrea-cpuimx27.dtsi
> index 2cf896c..7c75147 100644
> --- a/arch/arm/boot/dts/imx27-eukrea-cpuimx27.dtsi
> +++ b/arch/arm/boot/dts/imx27-eukrea-cpuimx27.dtsi
> @@ -23,7 +23,6 @@
>  	clocks {
>  		#address-cells = <1>;
>  		#size-cells = <0>;
> -		compatible = "simple-bus";
>  
>  		clk14745600: clock at 0 {
>  			#clock-cells = <0>;

We should probably fix it in another way - put the node directly under
root with a unique node name and drop unit-address.

Shawn

  reply	other threads:[~2018-01-29  6:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-27 16:23 [PATCH 1/2] ARM: dts: imx27-eukrea-mbimxsd27-baseboard: Pass missing unit address Fabio Estevam
2017-12-27 16:23 ` [PATCH 2/2] ARM: dts: imx27-eukrea-cpuimx27: Remove 'simple-bus' from clocks node Fabio Estevam
2018-01-29  6:36   ` Shawn Guo [this message]
2018-01-29  6:36 ` [PATCH 1/2] ARM: dts: imx27-eukrea-mbimxsd27-baseboard: Pass missing unit address 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=20180129063610.GA26461@dragon \
    --to=shawnguo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).