devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Kumar Gala <galak@codeaurora.org>
Cc: "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: Fri, 6 Mar 2015 11:15:11 -0800	[thread overview]
Message-ID: <CAOesGMjpOx4SxY7j8jnoEwLG+mhPKB2st8qCb-hduHLOVw=RcQ@mail.gmail.com> (raw)
In-Reply-To: <B8019148-3B26-453E-A3F0-9D67874083E0@codeaurora.org>

On Fri, Mar 6, 2015 at 8:08 AM, Kumar Gala <galak@codeaurora.org> wrote:
>
> On Mar 5, 2015, at 7:59 PM, Olof Johansson <olof@lixom.net> wrote:
>
>> On Thu, Mar 5, 2015 at 12:23 PM, Kumar Gala <galak@codeaurora.org> wrote:
>>>
>>> On Mar 5, 2015, at 1:42 PM, Kevin Hilman <khilman@kernel.org> wrote:
>>>
>>>> Kumar Gala <galak@codeaurora.org> writes:
>>>>
>>>>> 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?


-Olof

  reply	other threads:[~2015-03-06 19:15 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 [this message]
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
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='CAOesGMjpOx4SxY7j8jnoEwLG+mhPKB2st8qCb-hduHLOVw=RcQ@mail.gmail.com' \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.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 \
    /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).