From: Rob Herring <robh@kernel.org>
To: Chris Lew <clew@codeaurora.org>
Cc: bjorn.andersson@linaro.org, andy.gross@linaro.org,
david.brown@linaro.org, mark.rutland@arm.com,
aneela@codeaurora.org, smaliyap@codeaurora.org,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: soc: qcom: Support GLINK intents
Date: Fri, 27 Oct 2017 09:38:28 -0500 [thread overview]
Message-ID: <20171027142342.wuxzdyns27fmxajs@rob-hp-laptop> (raw)
In-Reply-To: <1509056936-26578-2-git-send-email-clew@codeaurora.org>
On Thu, Oct 26, 2017 at 03:28:54PM -0700, Chris Lew wrote:
> Virtual GLINK channels may know what throughput to expect from a
> remoteproc. An intent advertises to the remoteproc this channel is
> ready to receive data. Allow a channel to define the size and amount of
> intents to be prequeued.
>
> Signed-off-by: Chris Lew <clew@codeaurora.org>
> ---
>
> Changes since v1:
> - Change intents property to qcom,intents and update example
> - Change second sentence in definition to better describe usage
>
> Documentation/devicetree/bindings/soc/qcom/qcom,glink.txt | 10 ++++++++++
> 1 file changed, 10 insertions(+)
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2017-10-27 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 22:28 [PATCH v2 0/3] GLINK intent preallocation support Chris Lew
2017-10-26 22:28 ` [PATCH v2 1/3] dt-bindings: soc: qcom: Support GLINK intents Chris Lew
2017-10-27 14:38 ` Rob Herring [this message]
2017-10-26 22:28 ` [PATCH v2 2/3] rpmsg: glink: Add support to preallocate intents Chris Lew
2017-10-26 22:28 ` [PATCH v2 3/3] rpmsg: glink: Use best fit intent during tx Chris Lew
2017-10-31 4:26 ` [PATCH v2 0/3] GLINK intent preallocation support Bjorn Andersson
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=20171027142342.wuxzdyns27fmxajs@rob-hp-laptop \
--to=robh@kernel.org \
--cc=andy.gross@linaro.org \
--cc=aneela@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=clew@codeaurora.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-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=smaliyap@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®