Thread (20 messages) 20 messages, 7 authors, 2015-03-11

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

From: Kumar Gala <hidden>
Date: 2015-03-06 20:38:07
Also in: linux-arm-msm, linux-devicetree, lkml

On Mar 6, 2015, at 1:15 PM, Olof Johansson [off-list ref] wrote:
On Fri, Mar 6, 2015 at 8:08 AM, Kumar Gala [off-list ref] wrote:
quoted
On Mar 5, 2015, at 7:59 PM, Olof Johansson [off-list ref] wrote:
quoted
On Thu, Mar 5, 2015 at 12:23 PM, Kumar Gala [off-list ref] wrote:
quoted
On Mar 5, 2015, at 1:42 PM, Kevin Hilman [off-list ref] wrote:
quoted
Kumar Gala [off-list ref] writes:
quoted
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: <redacted>
Signed-off-by: Kumar Gala <redacted>
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.

- k

-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help