From: Rob Herring <robh+dt@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
Mark Rutland <mark.rutland@arm.com>,
Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>,
"open list:REMOTE PROCESSOR (REMOTEPROC) SUBSYSTEM"
<linux-remoteproc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
"open list:ARM/QUALCOMM SUPPORT" <linux-soc@vger.kernel.org>
Subject: Re: [PATCH 2/2] dt-bindings: soc: qcom: Extend GLINK to cover SMEM
Date: Fri, 1 Sep 2017 10:36:59 -0500 [thread overview]
Message-ID: <CAL_JsqJmmRpAEDqwdgQX2EmB6F8Lzqj3YF+xwMb5xi8EbboB2w@mail.gmail.com> (raw)
In-Reply-To: <20170829231336.24454-2-bjorn.andersson@linaro.org>
On Tue, Aug 29, 2017 at 6:13 PM, Bjorn Andersson
<bjorn.andersson@linaro.org> wrote:
> In addition to using GLINK for communication with the RPM it can be
> used ontop of SMEM for communicating with remoteprocs, extend the
> binding to also describe this case and reference the GLINK binding from
> the affected remoteproc bindings.
>
> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> ---
> Documentation/devicetree/bindings/remoteproc/qcom,adsp.txt | 7 ++++---
> Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt | 5 +++++
> Documentation/devicetree/bindings/soc/qcom/qcom,glink.txt | 13 +++++++------
> 3 files changed, 16 insertions(+), 9 deletions(-)
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2017-09-01 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 23:13 [PATCH 1/2] remoteproc: qcom: adsp: Allow defining GLINK edge Bjorn Andersson
2017-08-29 23:13 ` Bjorn Andersson
2017-08-29 23:13 ` [PATCH 2/2] dt-bindings: soc: qcom: Extend GLINK to cover SMEM Bjorn Andersson
2017-08-29 23:13 ` Bjorn Andersson
2017-09-01 15:36 ` Rob Herring [this message]
2017-09-01 15:36 ` Rob Herring
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=CAL_JsqJmmRpAEDqwdgQX2EmB6F8Lzqj3YF+xwMb5xi8EbboB2w@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ohad@wizery.com \
/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.