From: Rob Herring <robh@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Rob Herring <rob.herring@linaro.org>, Nishanth Menon <nm@ti.com>,
Tomi Valkeinen <tomi.valkeinen@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
arm-platform-maintainers@lists.infradead.org,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: 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@1800000000 has a unit name, but no reg property
> > Warning (unit_address_vs_reg): Node /opp_table0/opp@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
next prev parent reply other threads:[~2016-04-04 5:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAL_Jsq+=OjY8y_8x7OSm-MWYKbrHN5cbv4TLwULxhNq+gfiMtw@mail.gmail.com>
[not found] ` <56FE27F9.2070100@gmail.com>
[not found] ` <CAJKOXPdDyVbfSyshu4j21Ax2J-VwPpMZgAGEeO8VtgFYh4hTmw@mail.gmail.com>
2016-04-01 13:57 ` dtc warnings 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
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=arm-platform-maintainers@lists.infradead.org \
--cc=devicetree@vger.kernel.org \
--cc=k.kozlowski@samsung.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rob.herring@linaro.org \
--cc=tomi.valkeinen@gmail.com \
--cc=viresh.kumar@linaro.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