[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <79FFFE06-191C-404D-8923-48C9C28C61F7@codeaurora.org>
Date: Wed, 11 Mar 2015 15:35:22 -0500
From: Kumar Gala <galak@...eaurora.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: Bjorn Andersson <bjorn@...o.se>, Olof Johansson <olof@...om.net>,
Kevin Hilman <khilman@...nel.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"arm@...nel.org" <arm@...nel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Heiko Stübner <heiko@...ech.de>
Subject: Re: [PATCH v2 1/3] devicetree: bindings: Document qcom,msm-id and qcom,board-id
On Mar 11, 2015, at 3:20 PM, Arnd Bergmann <arnd@...db.de> wrote:
> On Wednesday 11 March 2015 08:33:04 Bjorn Andersson wrote:
>>
>> But are these values actually used by the boot loader?
>>
>> As far as I could see in 8974 the dtbTool provided by Qualcomm
>> extracts the values from the list of dtbs and use them to create the
>> table-of-content in the QCDT blob. The boot loader then looks in this
>> TOC to pick the right dtb to use.
>>
>
> I guess if I understand this right, we just need to fix that dtbTool
> then to look at the top-level compatible property and/or machine
> name instead?
>
> Arnd
Correct, and it means updating the tool for every board/dts that gets created in the future.
Thus, the feeling was that having the ids kept with the dtb made maintenance far easier.
- 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