Re: [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id

[Olof Johansson]

On Fri, Mar 6, 2015 at 8:08 AM, Kumar Gala <galak@xxxxxxxxxxxxxx> wrote:
>
> On Mar 5, 2015, at 7:59 PM, Olof Johansson <olof@xxxxxxxxx> wrote:
>
>> On Thu, Mar 5, 2015 at 12:23 PM, Kumar Gala <galak@xxxxxxxxxxxxxx> wrote:
>>>
>>> On Mar 5, 2015, at 1:42 PM, Kevin Hilman <khilman@xxxxxxxxxx> wrote:
>>>
>>>> Kumar Gala <galak@xxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxx>
>>>>> Signed-off-by: Kumar Gala <galak@xxxxxxxxxxxxxx>
>>>>
>>>> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/