public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: dts: socfpga: fix DTC unit name warnings
Date: Mon, 18 Apr 2016 06:55:06 +0200	[thread overview]
Message-ID: <571468AA.9070501@denx.de> (raw)
In-Reply-To: <5710F81B.3090602@denx.de>

Hello Marek,

Am 15.04.2016 um 16:18 schrieb Marek Vasut:
> On 04/15/2016 12:41 PM, Heiko Schocher wrote:
>> Fix following DTC warnings for all socfpga boards:
>> Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/clkmgr at ffd04000/clocks/main_pll has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/clkmgr at ffd04000/clocks/main_pll/mpuclk has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/clkmgr at ffd04000/clocks/main_pll/mainclk has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/clkmgr at ffd04000/clocks/main_pll/dbg_base_clk has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/clkmgr at ffd04000/clocks/main_pll/main_qspi_clk has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/clkmgr at ffd04000/clocks/main_pll/main_nand_sdmmc_clk has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/clkmgr at ffd04000/clocks/main_pll/cfg_h2f_usr0_clk has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/clkmgr at ffd04000/clocks/periph_pll has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/clkmgr at ffd04000/clocks/periph_pll/emac0_clk has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/clkmgr at ffd04000/clocks/periph_pll/emac1_clk has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/clkmgr at ffd04000/clocks/periph_pll/per_qsi_clk has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/clkmgr at ffd04000/clocks/periph_pll/per_nand_mmc_clk has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/clkmgr at ffd04000/clocks/periph_pll/per_base_clk has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/clkmgr at ffd04000/clocks/periph_pll/h2f_usr1_clk has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/clkmgr at ffd04000/clocks/sdram_pll has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/clkmgr at ffd04000/clocks/sdram_pll/ddr_dqs_clk has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/clkmgr at ffd04000/clocks/sdram_pll/ddr_2x_dqs_clk has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/clkmgr at ffd04000/clocks/sdram_pll/ddr_dq_clk has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/clkmgr at ffd04000/clocks/sdram_pll/h2f_usr2_clk has a reg or ranges property, but no unit name
>> Warning (unit_address_vs_reg): Node /soc/usbphy at 0 has a unit name, but no reg property
>
> How come Linux isn't affected by this ?

I think linux is also affected!

>> Signed-off-by: Heiko Schocher <hs@denx.de>
>> ---
>> This warnings pop up with the DTC compiler:
>> $ /tmp/dtc/dtc -v
>> Version: DTC 1.4.1-gbeef80b8
>>
>> This fixes the compile warnings for:
>> https://travis-ci.org/u-boot/u-boot/jobs/122880430
>>
>> see:
>> https://travis-ci.org/hsdenx/u-boot/jobs/123238779
>>
>>   arch/arm/dts/skeleton.dtsi                     |  2 +-
>>   arch/arm/dts/socfpga.dtsi                      | 40 +++++++++++++-------------
>>   arch/arm/dts/socfpga_arria5_socdk.dts          |  2 +-
>>   arch/arm/dts/socfpga_cyclone5_de0_nano_soc.dts |  2 +-
>>   arch/arm/dts/socfpga_cyclone5_mcvevk.dts       |  2 +-
>>   arch/arm/dts/socfpga_cyclone5_socdk.dts        |  2 +-
>>   arch/arm/dts/socfpga_cyclone5_sockit.dts       |  2 +-
>>   arch/arm/dts/socfpga_cyclone5_socrates.dts     |  2 +-
>>   8 files changed, 27 insertions(+), 27 deletions(-)
>>
>> diff --git a/arch/arm/dts/skeleton.dtsi b/arch/arm/dts/skeleton.dtsi
>> index b41d241..a20da0a 100644
>> --- a/arch/arm/dts/skeleton.dtsi
>> +++ b/arch/arm/dts/skeleton.dtsi
>> @@ -9,5 +9,5 @@
>>   	#size-cells = <1>;
>>   	chosen { };
>>   	aliases { };
>> -	memory { device_type = "memory"; reg = <0 0>; };
>> +	memory at 0 { device_type = "memory"; reg = <0 0>; };
>>   };
>
> Can you split this into skeleton.dtsi patch and socfpga-only patch?
> That'd help containing the changes.

Yes, of course!

bye,
Heiko
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2016-04-18  4:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15 10:41 [U-Boot] [PATCH] arm: dts: socfpga: fix DTC unit name warnings Heiko Schocher
2016-04-15 14:18 ` Marek Vasut
2016-04-18  4:55   ` Heiko Schocher [this message]
2016-04-18 10:36     ` Marek Vasut
2016-04-18 11:20       ` Heiko Schocher
2016-04-18 11:22         ` Marek Vasut
2016-04-17 21:55 ` Pavel Machek
2016-04-18  6:07   ` Heiko Schocher
2016-04-18 10:00     ` Pavel Machek
2016-04-18 10:35       ` Marek Vasut
2016-04-18 11:06       ` Heiko Schocher
2016-04-18 15:31 ` Tom Rini
2016-04-18 15:37   ` Marek Vasut
2016-04-18 15:46     ` Tom Rini
2016-04-18 17:52       ` Marek Vasut
2016-04-19  5:01         ` Heiko Schocher
2016-04-19 10:38           ` Marek Vasut
2016-04-19  4:47       ` Heiko Schocher

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=571468AA.9070501@denx.de \
    --to=hs@denx.de \
    --cc=u-boot@lists.denx.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