From mboxrd@z Thu Jan 1 00:00:00 1970 From: galak@codeaurora.org (Kumar Gala) Date: Fri, 6 Mar 2015 14:37:52 -0600 Subject: [PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id In-Reply-To: References: <1425503602-24916-1-git-send-email-galak@codeaurora.org> <7h8ufbjkod.fsf@deeprootsystems.com> <07D4E4D1-BF8C-4583-9505-9F321DB10406@codeaurora.org> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mar 6, 2015, at 1:15 PM, Olof Johansson wrote: > On Fri, Mar 6, 2015 at 8:08 AM, Kumar Gala wrote: >> >> On Mar 5, 2015, at 7:59 PM, Olof Johansson wrote: >> >>> On Thu, Mar 5, 2015 at 12:23 PM, Kumar Gala wrote: >>>> >>>> On Mar 5, 2015, at 1:42 PM, Kevin Hilman wrote: >>>> >>>>> Kumar Gala 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: >>>>>> Signed-off-by: Kumar Gala >>>>> >>>>> 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