[PATCH v2 1/3] devicetree: bindings: Document qcom, msm-id and qcom, board-id
arnd at arndb.de
Wed Mar 11 14:48:13 PDT 2015
On Wednesday 11 March 2015 15:35:22 Kumar Gala wrote:
> On Mar 11, 2015, at 3:20 PM, Arnd Bergmann <arnd at arndb.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.
Part of my objection was to having nonstandard properties that are
not even used anywhere in the kernel. If you could just encode
them in the root compatible property as a string, that would be
a lot nicer.
More information about the linux-arm-kernel