From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm64: dts: juno/vexpress: fix node name unit-address presence warnings
Date: Fri, 18 Mar 2016 10:32:16 +0000 [thread overview]
Message-ID: <1458297136.2812.7.camel@linaro.org> (raw)
In-Reply-To: <CAL_JsqJeeZ58at95gSRwOMnce_DjDsXVRYH_bMKaX=uDHtZAAA@mail.gmail.com>
On Thu, 2016-03-17 at 16:44 -0500, Rob Herring wrote:
> On Mon, Mar 7, 2016 at 6:12 AM, Sudeep Holla <sudeep.holla@arm.com> wrote:
> > Commit fa38a82096a1 ("scripts/dtc: Update to upstream version
> > 53bf130b1cdd") added warnings on node name unit-address presence/absence
> > mismatch in device trees.
> >
> > This patch fixes those warning on all the juno/vexpress platforms where
> > unit-address is present in node name while the reg/ranges property is
> > not present.
> >
> > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> > ---
> > arch/arm64/boot/dts/arm/foundation-v8.dtsi | 2 +-
> > arch/arm64/boot/dts/arm/juno-base.dtsi | 14 +++++-----
> > arch/arm64/boot/dts/arm/juno-motherboard.dtsi | 30 +++++++++++-----------
> > arch/arm64/boot/dts/arm/rtsm_ve-aemv8a.dts | 2 +-
> > arch/arm64/boot/dts/arm/rtsm_ve-motherboard.dtsi | 14 +++++-----
> > .../boot/dts/arm/vexpress-v2f-1xv7-ca53x2.dts | 10 ++++----
> > 6 files changed, 36 insertions(+), 36 deletions(-)
> >
> > Hi Rob,
> >
> > I am not sure if the intention of commit fa38a82096a1 is to fix even
> > existing warnings or not. I saw warning with today's -next branch.
>
> Yes. I'm dropping it for 4.6 though.
>
> > Let me know.
> >
> > Regards,
> > Sudeep
> >
> > diff --git a/arch/arm64/boot/dts/arm/foundation-v8.dtsi b/arch/arm64/boot/dts/arm/foundation-v8.dtsi
> > index 9314f3943269..ba03c934a861 100644
> > --- a/arch/arm64/boot/dts/arm/foundation-v8.dtsi
> > +++ b/arch/arm64/boot/dts/arm/foundation-v8.dtsi
> > @@ -89,7 +89,7 @@
> > <0 63 4>;
> > };
> >
> > - smb {
> > + smb at 0,08000000 {
>
> Drop the comma and leading zeros. Comma is for distinct fields like
> bus,dev,func on PCI.
So what is the correct way of representing 2 cell addresses? Not just
those that are logically 64-bit addresses, (which I guess could be just
a single number), but things like vexpress motherboard where we have
Chip-select and Offset values?
I looked at ePAPR but it just says 'The unit-address must
match the first address specified in the reg property of the node.' and
lists valid characters for unit address, which includes ,._+-
--
Tixy
WARNING: multiple messages have this Message-ID (diff)
From: "Jon Medhurst (Tixy)" <tixy-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Lorenzo Pieralisi
<lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org>,
Liviu Dudau <liviu.dudau-5wv7dgnIgG8@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH 1/2] arm64: dts: juno/vexpress: fix node name unit-address presence warnings
Date: Fri, 18 Mar 2016 10:32:16 +0000 [thread overview]
Message-ID: <1458297136.2812.7.camel@linaro.org> (raw)
In-Reply-To: <CAL_JsqJeeZ58at95gSRwOMnce_DjDsXVRYH_bMKaX=uDHtZAAA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thu, 2016-03-17 at 16:44 -0500, Rob Herring wrote:
> On Mon, Mar 7, 2016 at 6:12 AM, Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org> wrote:
> > Commit fa38a82096a1 ("scripts/dtc: Update to upstream version
> > 53bf130b1cdd") added warnings on node name unit-address presence/absence
> > mismatch in device trees.
> >
> > This patch fixes those warning on all the juno/vexpress platforms where
> > unit-address is present in node name while the reg/ranges property is
> > not present.
> >
> > Signed-off-by: Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org>
> > ---
> > arch/arm64/boot/dts/arm/foundation-v8.dtsi | 2 +-
> > arch/arm64/boot/dts/arm/juno-base.dtsi | 14 +++++-----
> > arch/arm64/boot/dts/arm/juno-motherboard.dtsi | 30 +++++++++++-----------
> > arch/arm64/boot/dts/arm/rtsm_ve-aemv8a.dts | 2 +-
> > arch/arm64/boot/dts/arm/rtsm_ve-motherboard.dtsi | 14 +++++-----
> > .../boot/dts/arm/vexpress-v2f-1xv7-ca53x2.dts | 10 ++++----
> > 6 files changed, 36 insertions(+), 36 deletions(-)
> >
> > Hi Rob,
> >
> > I am not sure if the intention of commit fa38a82096a1 is to fix even
> > existing warnings or not. I saw warning with today's -next branch.
>
> Yes. I'm dropping it for 4.6 though.
>
> > Let me know.
> >
> > Regards,
> > Sudeep
> >
> > diff --git a/arch/arm64/boot/dts/arm/foundation-v8.dtsi b/arch/arm64/boot/dts/arm/foundation-v8.dtsi
> > index 9314f3943269..ba03c934a861 100644
> > --- a/arch/arm64/boot/dts/arm/foundation-v8.dtsi
> > +++ b/arch/arm64/boot/dts/arm/foundation-v8.dtsi
> > @@ -89,7 +89,7 @@
> > <0 63 4>;
> > };
> >
> > - smb {
> > + smb@0,08000000 {
>
> Drop the comma and leading zeros. Comma is for distinct fields like
> bus,dev,func on PCI.
So what is the correct way of representing 2 cell addresses? Not just
those that are logically 64-bit addresses, (which I guess could be just
a single number), but things like vexpress motherboard where we have
Chip-select and Offset values?
I looked at ePAPR but it just says 'The unit-address must
match the first address specified in the reg property of the node.' and
lists valid characters for unit address, which includes ,._+-
--
Tixy
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-03-18 10:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 12:12 [PATCH 1/2] arm64: dts: juno/vexpress: fix node name unit-address presence warnings Sudeep Holla
2016-03-07 12:12 ` Sudeep Holla
2016-03-07 12:12 ` [PATCH 2/2] ARM: dts: vexpress: " Sudeep Holla
2016-03-07 12:12 ` Sudeep Holla
2016-03-17 21:44 ` [PATCH 1/2] arm64: dts: juno/vexpress: " Rob Herring
2016-03-17 21:44 ` Rob Herring
2016-03-18 10:32 ` Jon Medhurst (Tixy) [this message]
2016-03-18 10:32 ` Jon Medhurst (Tixy)
2016-03-18 13:09 ` Rob Herring
2016-03-18 13:09 ` Rob Herring
2016-03-18 14:15 ` Jon Medhurst (Tixy)
2016-03-18 14:15 ` Jon Medhurst (Tixy)
2016-03-18 14:52 ` Rob Herring
2016-03-18 14:52 ` 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=1458297136.2812.7.camel@linaro.org \
--to=tixy@linaro.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 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.