Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1275989

Re: [PATCH v2 1/5] devicetree: bindings: Document qcom board compatible format

From Stephen Boyd <sboyd@codeaurora.org>
Newsgroups linux.kernel
Subject Re: [PATCH v2 1/5] devicetree: bindings: Document qcom board compatible format
Date 2015-11-24 01:50 +0100
Message-ID <qy9XX-P0-9@gated-at.bofh.it> (permalink)
References <qx3rz-5CJ-11@gated-at.bofh.it> <qx3rA-5CJ-35@gated-at.bofh.it> <qxJK9-qg-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 11/22, Rob Herring wrote:
> On Fri, Nov 20, 2015 at 03:31:16PM -0800, Stephen Boyd wrote:
> > Some qcom based bootloaders identify the dtb blob based on a set
> > of device properties like SoC, platform, PMIC, and revisions of
> > those components. In downstream kernels, these values are added
> > to the different component dtsi files (i.e. pmic dtsi file, SoC
> > dtsi file, board dtsi file, etc.) via qcom specific DT
> > properties. The dtb files are parsed by a program called dtbTool
> > that picks out these properties and creates a table of contents
> > binary blob with the property information and some offsets into
> > the concatenation of all the dtbs (termed a QCDT image).
> > 
> > The suggestion is to do this via the board compatible string
> > instead, because these qcom specific properties are never used by
> > the kernel. Add a document describing the format of the
> > compatible string that encodes all this information that's
> > currently encoded in the qcom,{msm-id,board-id,pmic-id}
> > properties in downstream devicetrees. Future bootloaders may be
> > updated to look at the compatible field instead of looking for
> > the table of contents image. For non-updateable bootloaders, a
> > new dtbTool program will parse the compatible string and generate
> > a QCDT image from it.
> > 
> > Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> 
> Much more reasonable now. I do find the '/' in it a bit strange though.

I can remove the backslash if you like. Is a dash more preferred?

> 
> Acked-by: Rob Herring <robh@kernel.org>
> 

and if so can I keep the ack? I'll resend with that change and
add the ack.

-- 
Qualcomm Innovation Center, Inc. is a member of 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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH v2 0/5] Remove the need for qcom,{msm-id,board-id,pmic-id} Stephen Boyd <sboyd@codeaurora.org> - 2015-11-21 00:40 +0100
  [PATCH v2 3/5] arm: dts: qcom: Update ifc6540 compat for qcom boot format Stephen Boyd <sboyd@codeaurora.org> - 2015-11-21 00:40 +0100
  [PATCH v2 1/5] devicetree: bindings: Document qcom board compatible format Stephen Boyd <sboyd@codeaurora.org> - 2015-11-21 00:40 +0100
    Re: [PATCH v2 1/5] devicetree: bindings: Document qcom board  compatible format Rob Herring <robh@kernel.org> - 2015-11-22 21:50 +0100
      Re: [PATCH v2 1/5] devicetree: bindings: Document qcom board  compatible format Stephen Boyd <sboyd@codeaurora.org> - 2015-11-24 01:50 +0100
  [PATCH v2 2/5] arm64: dts: qcom: Make msm8916-mtp compatible string compliant Stephen Boyd <sboyd@codeaurora.org> - 2015-11-21 00:40 +0100
  [PATCH v2 4/5] arm64: dts: qcom: Alias pm8916 on msm8916 devices Stephen Boyd <sboyd@codeaurora.org> - 2015-11-21 00:40 +0100
  [PATCH v2 5/5] arm: dts: qcom: Add aliases for PMICs Stephen Boyd <sboyd@codeaurora.org> - 2015-11-21 00:40 +0100

csiph-web