devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@codeaurora.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Bjorn Andersson" <bjorn@kryo.se>,
	"Olof Johansson" <olof@lixom.net>,
	"Kevin Hilman" <khilman@kernel.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"arm@kernel.org" <arm@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Heiko Stübner" <heiko@sntech.de>
Subject: Re: [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id
Date: Wed, 11 Mar 2015 15:35:22 -0500	[thread overview]
Message-ID: <79FFFE06-191C-404D-8923-48C9C28C61F7@codeaurora.org> (raw)
In-Reply-To: <2155628.BceQuZbXC8@wuerfel>


On Mar 11, 2015, at 3:20 PM, Arnd Bergmann <arnd@arndb.de> wrote:

> On Wednesday 11 March 2015 08:33:04 Bjorn Andersson wrote:
>> 
>> But are these values actually used by the boot loader?
>> 
>> As far as I could see in 8974 the dtbTool provided by Qualcomm
>> extracts the values from the list of dtbs and use them to create the
>> table-of-content in the QCDT blob. The boot loader then looks in this
>> TOC to pick the right dtb to use.
>> 
> 
> I guess if I understand this right, we just need to fix that dtbTool
> then to look at the top-level compatible property and/or machine
> name instead?
> 
> 	Arnd

Correct, and it means updating the tool for every board/dts that gets created in the future.

Thus, the feeling was that having the ids kept with the dtb made maintenance far easier.

- k

-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2015-03-11 20:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04 21:13 [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Kumar Gala
2015-03-04 21:13 ` [PATCH v2 2/3] arm64: qcom: Add support for Qualcomm MSM8916 SoC Kumar Gala
2015-03-04 22:33   ` Stephen Boyd
2015-03-05 15:06     ` Kumar Gala
2015-03-05 16:03       ` Stephen Boyd
2015-03-04 21:13 ` [PATCH v2 3/3] arm64: dts: Add Qualcomm MSM8916 SoC and evaluation board dts Kumar Gala
2015-03-04 21:19 ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Arnd Bergmann
2015-03-04 21:22   ` Kumar Gala
2015-03-05 19:42 ` Kevin Hilman
2015-03-05 20:23   ` Kumar Gala
2015-03-06  1:59     ` Olof Johansson
2015-03-06  2:28       ` Rob Clark
     [not found]         ` <CAF6AEGssMoo6c3nf_7fcATwocuETGZ8nbpGQpUO=KcKWC+rvHw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-06 15:09           ` Christopher Covington
2015-03-06 16:08       ` Kumar Gala
2015-03-06 19:15         ` Olof Johansson
2015-03-06 20:37           ` Kumar Gala
2015-03-09 12:11             ` Arnd Bergmann
2015-03-10 17:13               ` Kumar Gala
     [not found]                 ` <F5017A7F-0EA2-41B3-A9DD-6123CCFD36FA-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-03-10 17:55                   ` Olof Johansson
2015-03-10 18:10                     ` Kumar Gala
2015-03-10 19:52                       ` Arnd Bergmann
2015-03-10 19:57                         ` Kumar Gala
2015-03-11 15:33                           ` Bjorn Andersson
2015-03-11 15:57                             ` Kumar Gala
     [not found]                             ` <CAJAp7OiVwvPjRbrBxw7Dndvk4Apwz_bx=CzSqeqd3JzYhmB7Kw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-11 20:20                               ` Arnd Bergmann
2015-03-11 20:35                                 ` Kumar Gala [this message]
2015-03-11 21:48                                   ` Arnd Bergmann
2015-03-10 22:01                         ` Rob Clark

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=79FFFE06-191C-404D-8923-48C9C28C61F7@codeaurora.org \
    --to=galak@codeaurora.org \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bjorn@kryo.se \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    /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).