public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id
Date: Wed, 11 Mar 2015 22:48:13 +0100	[thread overview]
Message-ID: <7229476.C4So9noUlf@wuerfel> (raw)
In-Reply-To: <79FFFE06-191C-404D-8923-48C9C28C61F7@codeaurora.org>

On Wednesday 11 March 2015 15:35:22 Kumar Gala wrote:
> 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.
> 

Part of my objection was to having nonstandard properties that are
not even used anywhere in the kernel. If you could just encode
them in the root compatible property as a string, that would be
a lot nicer.

	Arnd

  reply	other threads:[~2015-03-11 21:48 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
2015-03-06 15:09         ` [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id Christopher Covington
2015-03-06 16:08       ` [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id 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
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
2015-03-11 20:20                           ` Arnd Bergmann
2015-03-11 20:35                             ` Kumar Gala
2015-03-11 21:48                               ` Arnd Bergmann [this message]
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=7229476.C4So9noUlf@wuerfel \
    --to=arnd@arndb.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox