public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Duc Dang <dhdang@apm.com>
Cc: Rob Herring <robh@kernel.org>,
	Devicetree List <devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arm <linux-arm-kernel@lists.infradead.org>
Subject: Re: Warning when compiling DTB on X-Gene platform with dtc 1.4.1-g53bf130b
Date: Tue, 21 Jun 2016 15:25:15 +0200	[thread overview]
Message-ID: <20160621132515.GC22350@lunn.ch> (raw)
In-Reply-To: <CADaLNDnfH8Weo=9jVNAW7LQCvAw23-z5fafwWcer4FSKeYH=ug@mail.gmail.com>

On Tue, Jun 21, 2016 at 02:02:44AM -0700, Duc Dang wrote:
> Hi Rob,
> 
> I got warning on unit_address_vs_reg similar to this
> https://lkml.org/lkml/2016/3/7/43 when using v4.7-rc2 dtc to build dtb
> for X-Gene Mustang:
> 
> dhdang@xgene-next=>./scripts/dtc/dtc -O dtb -R 16 -o mustang.dtb
> arch/arm64/boot/dts/apm/apm-mustang.dts
>   Warning (unit_address_vs_reg): Node /soc/reboot@17000014 has a unit
> name, but no reg property
>   Warning (unit_address_vs_reg): Node /memory has a reg or ranges
> property, but no unit name
>   Warning (unit_address_vs_reg): Node /gpio-keys/button@1 has a unit
> name, but no reg property
> 
> There are nodes that I cannot change the node-name due to backward
> compatible with old firmware reason (/soc/reboot@17000014 as an
> example). Is there any other way to avoid the warning?

I think you have that backwards around. The Kernel needs to be
backwards compatible with old DT blobs. DT blobs don't generally need
to be backwards compatible to older kernels.

However, the kernel should however be happy with or without the unit
name. The unit name is pointless in this case.

	Andrew

  reply	other threads:[~2016-06-21 13:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21  9:02 Warning when compiling DTB on X-Gene platform with dtc 1.4.1-g53bf130b Duc Dang
2016-06-21 13:25 ` Andrew Lunn [this message]
2016-06-21 21:40   ` Duc Dang

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=20160621132515.GC22350@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dhdang@apm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.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