Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: dtc warnings
Date: Mon, 4 Apr 2016 00:16:56 -0500	[thread overview]
Message-ID: <20160404051656.GV17806@rob-hp-laptop> (raw)
In-Reply-To: <CAKohpomijKf3m07Lc3+fWawxAPwe83F8k9akz1LOTokpZNL2ig@mail.gmail.com>

On Sun, Apr 03, 2016 at 05:57:00PM +0530, Viresh Kumar wrote:
> On 3 April 2016 at 13:38, Krzysztof Kozlowski <k.kozlowski@samsung.com> wrote:
> > Warnings coming from recent linux-next:
> >
> >   DTC     arch/arm/boot/dts/exynos5800-peach-pi.dtb
> > Warning (unit_address_vs_reg): Node /opp_table0/opp at 1800000000 has a unit name, but no reg property
> > Warning (unit_address_vs_reg): Node /opp_table0/opp at 1700000000 has a unit name, but no reg property
> 
> @Rob: What should we be doing about these warnings?
> OPP-entries don't have a reg property obviously and we
> discussed earlier if naming them based on freq is fine or
> not.

We can whitelist opp nodes in dtc, use oppN instead, or ignore the 
warnings for now. 

Rob

  reply	other threads:[~2016-04-04  5:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01  1:40 dtc warnings Rob Herring
2016-04-01  7:49 ` Tomi Valkeinen
2016-04-01  7:53   ` Krzysztof Kozlowski
2016-04-01 13:57     ` Nishanth Menon
2016-04-03  6:59       ` Viresh Kumar
2016-04-03  8:08         ` Krzysztof Kozlowski
2016-04-03 12:27           ` Viresh Kumar
2016-04-04  5:16             ` Rob Herring [this message]
2016-04-04  5:50               ` Viresh Kumar
2016-04-04  5:56                 ` Krzysztof Kozlowski
2016-04-01 13:25   ` Rob Herring
2016-04-01 15:42 ` Tony Lindgren
2016-04-21 12:47 ` Rob Herring

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=20160404051656.GV17806@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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