From: Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Andy Gross <agross-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
Kevin Hilman <khilman-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 1/5] devicetree: bindings: Document qcom board compatible format
Date: Mon, 23 Nov 2015 16:47:22 -0800 [thread overview]
Message-ID: <20151124004722.GL19156@codeaurora.org> (raw)
In-Reply-To: <20151122204935.GA465@rob-hp-laptop>
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-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.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-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/5] devicetree: bindings: Document qcom board compatible format
Date: Mon, 23 Nov 2015 16:47:22 -0800 [thread overview]
Message-ID: <20151124004722.GL19156@codeaurora.org> (raw)
In-Reply-To: <20151122204935.GA465@rob-hp-laptop>
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
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@codeaurora.org>
To: Rob Herring <robh@kernel.org>
Cc: Andy Gross <agross@codeaurora.org>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Olof Johansson <olof@lixom.net>,
Kevin Hilman <khilman@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/5] devicetree: bindings: Document qcom board compatible format
Date: Mon, 23 Nov 2015 16:47:22 -0800 [thread overview]
Message-ID: <20151124004722.GL19156@codeaurora.org> (raw)
In-Reply-To: <20151122204935.GA465@rob-hp-laptop>
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
next prev parent reply other threads:[~2015-11-24 0:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 23:31 [PATCH v2 0/5] Remove the need for qcom,{msm-id,board-id,pmic-id} Stephen Boyd
2015-11-20 23:31 ` Stephen Boyd
2015-11-20 23:31 ` [PATCH v2 1/5] devicetree: bindings: Document qcom board compatible format Stephen Boyd
2015-11-20 23:31 ` Stephen Boyd
2015-11-22 20:49 ` Rob Herring
2015-11-22 20:49 ` Rob Herring
2015-11-24 0:47 ` Stephen Boyd [this message]
2015-11-24 0:47 ` Stephen Boyd
2015-11-24 0:47 ` Stephen Boyd
2016-01-07 1:58 ` Stephen Boyd
2016-01-07 1:58 ` Stephen Boyd
[not found] ` <1448062280-15406-1-git-send-email-sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-11-20 23:31 ` [PATCH v2 2/5] arm64: dts: qcom: Make msm8916-mtp compatible string compliant Stephen Boyd
2015-11-20 23:31 ` Stephen Boyd
2015-11-20 23:31 ` Stephen Boyd
2015-11-20 23:31 ` [PATCH v2 3/5] arm: dts: qcom: Update ifc6540 compat for qcom boot format Stephen Boyd
2015-11-20 23:31 ` Stephen Boyd
2015-11-20 23:31 ` Stephen Boyd
2015-11-20 23:31 ` [PATCH v2 4/5] arm64: dts: qcom: Alias pm8916 on msm8916 devices Stephen Boyd
2015-11-20 23:31 ` Stephen Boyd
2015-11-20 23:31 ` Stephen Boyd
2015-12-09 19:10 ` Frank Rowand
2015-12-09 19:10 ` Frank Rowand
2015-11-20 23:31 ` [PATCH v2 5/5] arm: dts: qcom: Add aliases for PMICs Stephen Boyd
2015-11-20 23:31 ` Stephen Boyd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151124004722.GL19156@codeaurora.org \
--to=sboyd-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \
--cc=agross-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=khilman-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.