From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Jeremy McNicoll
<jmcnicol-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Andy Gross <andy.gross-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Bjorn Andersson
<bjorn.andersson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
git-LJ92rlH3Dns@public.gmane.org,
jeremymc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
linux-arm-msm
<linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [RFC V2 PATCH 10/12] arm64: dts: msm8994 issolate non standard bootloader/LK entries
Date: Wed, 12 Oct 2016 12:39:44 +0200 [thread overview]
Message-ID: <2149904.D2eaQZN3bA@wuerfel> (raw)
In-Reply-To: <CAL_Jsq+ew7p6OYPzdTDmB9LAoGOOKasioYzmU=R+jLza2hWQFw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Tuesday, October 11, 2016 7:41:22 PM CEST Rob Herring wrote:
> On Sat, Oct 1, 2016 at 9:38 PM, Jeremy McNicoll <jmcnicol-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
> > These non standard DT entries need to be cast aside as to not
> > pollute the main device tree bindings. Without these essential
> > DT items the bootloader/LK will not pass control over to the kernel
> > and thus never boot.
>
> I discussed this with Stephen recently. I'm okay with leaving these on
> boards that have no chance of getting updated bootloaders to use the
> compatible string instead. Having to use dtbTool is far worse than a
> couple of extra properties IMO. I reserve the right to complain if new
> stuff continues to use these though.
>
> > Signed-off-by: Jeremy McNicoll <jeremymc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> > ---
> > .../arm64/boot/dts/qcom/msm8994-angler-rev-101.dts | 1 -
> > arch/arm64/boot/dts/qcom/msm8994.dtsi | 3 +--
> > .../boot/dts/qcom/nexus6p_bootloader_bits.dtsi | 24 ++++++++++++++++++++++
>
> Just put this into the board file rather than yet another include.
The suggestion that I had was to have two .dts files: the normal
one without these properties, and another .dts file including the
first but adding these three for compatibility with the legacy
bootloaders.
That way we could have a 'clean' .dtb file once the bootloaders
get fixed, and can name the other one appropriately to discourage
copying the method for new machines.
Having the bootloader files included from the main .dts files
would serve no purpose.
Arnd
--
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-10-12 10:39 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 2:38 [RFC V2 PATCH 00/12] msm8992/msm8994: Google Nexus 5X/6P initial board support Jeremy McNicoll
2016-10-02 2:38 ` [RFC V2 PATCH 01/12] msm8994 clocks: global clock support Global clock support for the msm8994 SOC Jeremy McNicoll
2016-10-09 1:28 ` Rob Herring
2016-10-21 8:31 ` Jeremy McNicoll
2016-10-02 2:38 ` [RFC V2 PATCH 02/12] arm64: configs: enable 8994/8992 GCC by default Jeremy McNicoll
2016-10-02 2:38 ` [RFC V2 PATCH 03/12] msm8994 clocks: fix mapping Jeremy McNicoll
[not found] ` <1475375919-618-4-git-send-email-jmcnicol-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-09 1:28 ` Rob Herring
2016-10-10 22:04 ` Jeremy McNicoll
[not found] ` <228eb3b0-6c4e-230a-1750-0f97ec5c024f-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-10 22:47 ` Jeremy McNicoll
[not found] ` <1475375919-618-1-git-send-email-jmcnicol-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-02 2:38 ` [RFC V2 PATCH 04/12] dt-bindings: qcom: Add msm8992 bindings Jeremy McNicoll
[not found] ` <1475375919-618-5-git-send-email-jmcnicol-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-09 1:28 ` Rob Herring
2016-10-11 0:52 ` [RFC V3 PATCH] dt-bindings: qcom: Add msm899(2/4) bindings Jeremy McNicoll
[not found] ` <1476147156-4474-1-git-send-email-jeremymc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-11 16:42 ` Bjorn Andersson
2016-10-11 21:25 ` Jeremy McNicoll
[not found] ` <ab018442-c929-e328-11a3-6e7fd21e56b8-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-12 0:32 ` [RFC V4 " Jeremy McNicoll
2016-10-19 1:13 ` [RFC V3 " Stephen Boyd
2016-10-02 2:38 ` [RFC V2 PATCH 07/12] arm64: dts: msm8992 default serial config Jeremy McNicoll
2016-10-02 2:38 ` [RFC V2 PATCH 05/12] msm8992: defconfig updates to support initrd Jeremy McNicoll
2016-10-09 1:28 ` Rob Herring
2016-10-11 5:19 ` [RFC V3 PATCH] " Jeremy McNicoll
2016-10-11 5:20 ` [RFC V2 PATCH 05/12] " Jeremy McNicoll
2016-10-02 2:38 ` [RFC V2 PATCH 06/12] arm64: dts: msm8992 issolate non standard bootloader/LK entries Jeremy McNicoll
2016-10-02 2:38 ` [RFC V2 PATCH 08/12] arm64: dts: msm8994 SoC and Huawei Angler (Nexus 6P) support Jeremy McNicoll
2016-10-02 2:38 ` [RFC V2 PATCH 09/12] arm64: dts: move Huawei Angler (Nexus 6P) to qcom directory Jeremy McNicoll
[not found] ` <1475375919-618-10-git-send-email-jmcnicol-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-09 1:28 ` Rob Herring
2016-10-10 22:21 ` Jeremy McNicoll
[not found] ` <4611eab0-84b3-3c6f-2df0-87fe21afc8df-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-12 0:32 ` Rob Herring
2016-10-02 2:38 ` [RFC V2 PATCH 10/12] arm64: dts: msm8994 issolate non standard bootloader/LK entries Jeremy McNicoll
[not found] ` <1475375919-618-11-git-send-email-jmcnicol-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-12 0:41 ` Rob Herring
[not found] ` <CAL_Jsq+ew7p6OYPzdTDmB9LAoGOOKasioYzmU=R+jLza2hWQFw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-12 10:39 ` Arnd Bergmann [this message]
2016-10-12 12:11 ` Rob Herring
2016-10-13 0:59 ` Jeremy McNicoll
[not found] ` <17447be1-4357-0eca-a242-69576d3e2799-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-19 14:56 ` Arnd Bergmann
2016-10-19 21:46 ` Andy Gross
[not found] ` <20161019214643.GC3145-3KkwrOJo9xYlRp7syxWybdHuzzzSOjJt@public.gmane.org>
2016-10-20 1:07 ` Rob Herring
[not found] ` <CAL_Jsq+wjnEByg2vgx-P+bLJaQm+s=UX7nj=KwviagnQDG_3hQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-20 3:17 ` Andy Gross
[not found] ` <20161020031712.GD3145-3KkwrOJo9xYlRp7syxWybdHuzzzSOjJt@public.gmane.org>
2016-10-21 19:44 ` Bjorn Andersson
2016-10-21 20:04 ` Stephen Boyd
2016-10-21 20:25 ` Arnd Bergmann
2016-10-21 21:52 ` Bjorn Andersson
2016-10-22 0:07 ` Stephen Boyd
[not found] ` <20161022000733.GO26139-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-10-22 1:14 ` Bjorn Andersson
2016-10-21 22:42 ` Bjorn Andersson
2016-10-22 0:36 ` Stephen Boyd
2016-10-02 2:38 ` [RFC V2 PATCH 11/12] arm64: msm8994 / Nexus 6P remove defconfig Jeremy McNicoll
2016-10-02 2:38 ` [RFC V2 PATCH 12/12] arm64: dts: msm8994 default serial config Jeremy McNicoll
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=2149904.D2eaQZN3bA@wuerfel \
--to=arnd-r2ngtmty4d4@public.gmane.org \
--cc=andy.gross-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=bjorn.andersson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=git-LJ92rlH3Dns@public.gmane.org \
--cc=jeremymc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=jmcnicol-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.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;
as well as URLs for NNTP newsgroup(s).