U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] ARM: zynq: Remove DTC 1.2 warnings
Date: Tue, 15 Nov 2016 20:01:16 +0100	[thread overview]
Message-ID: <5bd8c14d-196e-ec85-3be9-1e40ac96cd4b@monstr.eu> (raw)
In-Reply-To: <20161115142239.GT27304@bill-the-cat>

On 15.11.2016 15:22, Tom Rini wrote:
> On Tue, Nov 15, 2016 at 03:16:51PM +0100, Michal Simek wrote:
>> On 11.11.2016 18:33, Tom Rini wrote:
>>> On Fri, Nov 11, 2016 at 06:32:15PM +0100, Michal Simek wrote:
>>>> Hi,
>>>>
>>>> 2016-11-11 17:04 GMT+01:00 Tom Rini <trini@konsulko.com>:
>>>>
>>>>> On Fri, Nov 11, 2016 at 01:26:05PM +0100, Michal Simek wrote:
>>>>>
>>>>>> DTC 1.2 reports these warnings:
>>>>>> Warning (unit_address_vs_reg): Node /memory has a reg or ranges
>>>>>> property, but no unit name
>>>>>> Warning (unit_address_vs_reg): Node /pmu has a reg or ranges property,
>>>>>> but no unit name
>>>>>> Warning (unit_address_vs_reg): Node /fixedregulator at 0 has a unit name,
>>>>>> but no reg property
>>>>>>
>>>>>> This patch is fixing them.
>>>>>>
>>>>>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
>>>>>
>>>>> Have you addressed these in Linux as well?
>>>>
>>>> Going to do so next week.
>>>> Both should be in sync.
>>>
>>> Agreed.  I'd prefer to pull them in via Linux but at least once they're
>>> on their way into the right tree for upstream we can bring them in here
>>> as well (as I want to ensure future re-syncs are easy).  Thanks!
>>>
>>
>> I have sent them to Linux too.
>> http://lists.infradead.org/pipermail/linux-arm-kernel/2016-November/467965.html
>> http://lists.infradead.org/pipermail/linux-arm-kernel/2016-November/467967.html
>> http://lists.infradead.org/pipermail/linux-arm-kernel/2016-November/467968.html
> 
> OK.
> 
>> For our case we have more dtses in u-boot especially for arm64 than in
>> Linux.
> 
> Intentional or just boards that have not yet made it there?

Simply because getting these stuff to U-Boot is easier then to Linux.

>> Also u-boot,dm-pre-reloc AFAIK hasn't been validated via dt mailing
>> list. I see one thread in 2015 without any resolution.
> 
> Yes, this is something that might get a re-visit someday, but is indeed
> local to U-Boot only for now.

Adding this to chosen node with list of IPs should be IMHO reasonable
solution.

>> That's why taking stuff from Linux is sort of goal but nothing what we
>> can do without additional work.
> 
> So long as everything relevant to upstream has been posted upstream (and
> you're saying it is, so good, I'm happy) then we're in good shape here.

Trying to keep all stuff in sync as much as possible and definitely we
need to do more Linux upstreaming.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP SoCs


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161115/a83e71c9/attachment.sig>

  reply	other threads:[~2016-11-15 19:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 12:26 [U-Boot] [PATCH 1/2] ARM: zynq: Remove DTC 1.2 warnings Michal Simek
2016-11-11 12:26 ` [U-Boot] [PATCH 2/2] ARM64: zynqmp: " Michal Simek
2016-11-11 16:04 ` [U-Boot] [PATCH 1/2] ARM: zynq: " Tom Rini
2016-11-11 17:32   ` Michal Simek
2016-11-11 17:33     ` Tom Rini
2016-11-15 14:16       ` Michal Simek
2016-11-15 14:22         ` Tom Rini
2016-11-15 19:01           ` Michal Simek [this message]
2016-11-16  0:34             ` Masahiro Yamada
2016-11-16  7:26               ` Michal Simek

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=5bd8c14d-196e-ec85-3be9-1e40ac96cd4b@monstr.eu \
    --to=monstr@monstr.eu \
    --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