From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rob Herring <robh@kernel.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 11:20:00 +0530 [thread overview]
Message-ID: <20160404055000.GA3622@vireshk-i7> (raw)
In-Reply-To: <20160404051656.GV17806@rob-hp-laptop>
On 04-04-16, 00:16, Rob Herring wrote:
> 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
Something isn't right in my setup, as I am not hitting these:
$ make CROSS_COMPILE="arm-linux-gnueabihf-" ARCH=arm O=../bexynos dtbs
make[1]: Entering directory '/mnt/ssd/all/work/repos/devel/bexynos'
CHK include/config/kernel.release
Using /mnt/ssd/all/work/repos/devel/linux as source for kernel
GEN ./Makefile
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
make[2]: 'include/generated/mach-types.h' is up to date.
CHK include/generated/bounds.h
CHK include/generated/timeconst.h
CHK include/generated/asm-offsets.h
CALL /mnt/ssd/all/work/repos/devel/linux/scripts/checksyscalls.sh
<stdin>:1310:2: warning: #warning syscall preadv2 not implemented [-Wcpp]
<stdin>:1313:2: warning: #warning syscall pwritev2 not implemented [-Wcpp]
DTC arch/arm/boot/dts/exynos3250-artik5-eval.dtb
DTC arch/arm/boot/dts/exynos3250-monk.dtb
DTC arch/arm/boot/dts/exynos3250-rinato.dtb
DTC arch/arm/boot/dts/exynos4210-origen.dtb
DTC arch/arm/boot/dts/exynos4210-smdkv310.dtb
DTC arch/arm/boot/dts/exynos4210-trats.dtb
DTC arch/arm/boot/dts/exynos4210-universal_c210.dtb
DTC arch/arm/boot/dts/exynos4412-odroidu3.dtb
DTC arch/arm/boot/dts/exynos4412-odroidx.dtb
DTC arch/arm/boot/dts/exynos4412-odroidx2.dtb
DTC arch/arm/boot/dts/exynos4412-origen.dtb
DTC arch/arm/boot/dts/exynos4412-smdk4412.dtb
DTC arch/arm/boot/dts/exynos4412-tiny4412.dtb
DTC arch/arm/boot/dts/exynos4412-trats2.dtb
DTC arch/arm/boot/dts/exynos5250-arndale.dtb
DTC arch/arm/boot/dts/exynos5250-smdk5250.dtb
DTC arch/arm/boot/dts/exynos5250-snow.dtb
DTC arch/arm/boot/dts/exynos5250-snow-rev5.dtb
DTC arch/arm/boot/dts/exynos5250-spring.dtb
DTC arch/arm/boot/dts/exynos5260-xyref5260.dtb
DTC arch/arm/boot/dts/exynos5410-smdk5410.dtb
DTC arch/arm/boot/dts/exynos5420-arndale-octa.dtb
DTC arch/arm/boot/dts/exynos5420-peach-pit.dtb
DTC arch/arm/boot/dts/exynos5420-smdk5420.dtb
DTC arch/arm/boot/dts/exynos5422-odroidxu3.dtb
DTC arch/arm/boot/dts/exynos5422-odroidxu3-lite.dtb
DTC arch/arm/boot/dts/exynos5422-odroidxu4.dtb
DTC arch/arm/boot/dts/exynos5440-sd5v1.dtb
DTC arch/arm/boot/dts/exynos5440-ssdk5440.dtb
DTC arch/arm/boot/dts/exynos5800-peach-pi.dtb
make[1]: Leaving directory '/mnt/ssd/all/work/repos/devel/bexynos'
> >
> > @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.
I will be required to update check_unit_address_vs_reg() for that, right ? Or
is there a easier way for doing this ? :)
--
viresh
next prev parent reply other threads:[~2016-04-04 5:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 1:40 dtc warnings Rob Herring
[not found] ` <CAL_Jsq+=OjY8y_8x7OSm-MWYKbrHN5cbv4TLwULxhNq+gfiMtw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-01 7:49 ` Tomi Valkeinen
[not found] ` <56FE27F9.2070100-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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
2016-04-04 5:50 ` Viresh Kumar [this message]
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=20160404055000.GA3622@vireshk-i7 \
--to=viresh.kumar@linaro.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=robh@kernel.org \
--cc=tomi.valkeinen@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).