[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <07D4E4D1-BF8C-4583-9505-9F321DB10406@codeaurora.org>
Date: Thu, 5 Mar 2015 14:23:04 -0600
From: Kumar Gala <galak@...eaurora.org>
To: Kevin Hilman <khilman@...nel.org>
Cc: linux-arm-msm@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
arm@...nel.org, devicetree@...r.kernel.org, heiko@...ech.de
Subject: Re: [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id
On Mar 5, 2015, at 1:42 PM, Kevin Hilman <khilman@...nel.org> wrote:
> Kumar Gala <galak@...eaurora.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@...r.kernel.org>
>> Signed-off-by: Kumar Gala <galak@...eaurora.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
- k
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists