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: Tue, 10 Mar 2015 20:52:01 +0100	[thread overview]
Message-ID: <10886228.vUHyKm1ubP@wuerfel> (raw)
In-Reply-To: <3A588B25-66ED-4BB5-8C8F-D050D8A2F9F3@codeaurora.org>

On Tuesday 10 March 2015 13:10:08 Kumar Gala wrote:
> >>>>>>>>> The top level qcom,msm-id and qcom,board-id are utilized by bootloaders
> >>>>>>>>>> on Qualcomm MSM platforms to determine which device tree should be
> >>>>>>>>>> utilized and passed to the kernel.
> >>>>>>>>>> 
> >>>>>>>>>> Cc: <devicetree@vger.kernel.org>
> >>>>>>>>>> Signed-off-by: Kumar Gala <galak@codeaurora.org>
> >>>>>>>>> 
> >>>>>>>>> Is this the special magic that allows qcom bootloaders to take a kernel
> >>>>>>>>> plus multiple DTBs and figure out which DTB to pass?
> >>>>>>>>> 
> >>>>>>>>> Kevin
> >>>>>>>> 
> >>>>>>>> yes
> >>>>>>> 
> >>>>>>> That's a bummer.
> >>>>>>> 
> >>>>>>> Luckily, the solution for upstream is still quite simple: Provide only
> >>>>>>> one devicetree, and it'll be used, right?
> >>>>>> 
> >>>>>> We can provide only one, we still need the IDs in the DT.
> >>>>> 
> >>>>> How are the DTS provided? Concatenated with the kernel, or in a
> >>>>> wrapped data format? Or in a separate partition from the kernel?
> >>>> 
> >>>> Its a wrapped data format that is than concatenated with the kernel if I remember correctly.
> >>> 
> >>> Then you should be able to create a tool that can write this concatenated
> >>> format and insert these properties from a table that matches the boot
> >>> loader, right?
> >>> 
> >>>      Arnd
> >> 
> >> Are you suggesting the tool insert the properties in the DT?  I?m not sure I understand what the point of doing that would be.
> > 
> > To insert platform-local properties that mean nothing outside of the
> > firmware packaging of the device trees, which is the case here?
> > 
> > I think the idea of having the installer script inserting them is
> > quite reasonable in this case.
> > 
> > 
> > -Olof
> 
> These values are static, so not sure what the point of having the installer script do that?
> 

It combines two hacks to work around a nonstandard boot loader.
Once the bootloader is fixed, you can stop using that script.

	Arnd

  reply	other threads:[~2015-03-10 19:52 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 [this message]
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
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=10886228.vUHyKm1ubP@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