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

Kumar Gala galak at codeaurora.org
Fri Mar 6 08:08:09 PST 2015

On Mar 5, 2015, at 7:59 PM, Olof Johansson <olof at lixom.net> wrote:

> On Thu, Mar 5, 2015 at 12:23 PM, Kumar Gala <galak at codeaurora.org> wrote:
>> On Mar 5, 2015, at 1:42 PM, Kevin Hilman <khilman at kernel.org> wrote:
>>> Kumar Gala <galak at 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 at vger.kernel.org>
>>>> Signed-off-by: Kumar Gala <galak at 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.

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

More information about the linux-arm-kernel mailing list