All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@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 13:22:31 +0200	[thread overview]
Message-ID: <5714C377.7080009@denx.de> (raw)
In-Reply-To: <5714C314.9050203@denx.de>

On 04/18/2016 01:20 PM, Heiko Schocher wrote:
> Hello Marek,
> 
> Am 18.04.2016 um 12:36 schrieb Marek Vasut:
>> On 04/18/2016 06:55 AM, Heiko Schocher wrote:
>>> 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!
>>
>> You might want to bring it up on the LKML, like Pavel suggested.
> 
> Do we have the same DTS as linux?
> (If so, isn;t it a bad idea to hold the files on 2 places?)

The DTS should be very similar I hope. U-Boot has QSPI nodes and the
u-boot,dm-pre-reloc properties.

-- 
Best regards,
Marek Vasut

  reply	other threads:[~2016-04-18 11:22 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
2016-04-18 10:36     ` Marek Vasut
2016-04-18 11:20       ` Heiko Schocher
2016-04-18 11:22         ` Marek Vasut [this message]
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=5714C377.7080009@denx.de \
    --to=marex@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.