[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160621132515.GC22350@lunn.ch>
Date: Tue, 21 Jun 2016 15:25:15 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Duc Dang <dhdang@....com>
Cc: Rob Herring <robh@...nel.org>,
Devicetree List <devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-arm <linux-arm-kernel@...ts.infradead.org>
Subject: Re: Warning when compiling DTB on X-Gene platform with dtc
1.4.1-g53bf130b
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@...ne-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@...00014 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@...00014 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
Powered by blists - more mailing lists