From: Stephen Boyd <sboyd@codeaurora.org>
To: Avaneesh Kumar Dwivedi <akdwived@codeaurora.org>
Cc: bjorn.andersson@linaro.org, stanimir.varbanov@linaro.org,
agross@codeaurora.org, linux-arm-msm@vger.kernel.org
Subject: Re: [RESEND PATCH v2] remoteproc: qcom: Add venus rproc support on msm8996 platform.
Date: Tue, 29 Nov 2016 11:27:02 -0800 [thread overview]
Message-ID: <20161129192702.GA6095@codeaurora.org> (raw)
In-Reply-To: <1480416647-3518-2-git-send-email-akdwived@codeaurora.org>
On 11/29, Avaneesh Kumar Dwivedi wrote:
> This patch is based on
> https://patchwork.kernel.org/patch/9415627/
> https://patchwork.kernel.org/patch/9415651/
>
> This patch add clock initialization, enable and disable support.
> Required resource name string and rating are differentiated based
> on compatible string. Also added documentation for venus pil on
> msm8996.
>
> Signed-off-by: Avaneesh Kumar Dwivedi <akdwived@codeaurora.org>
> ---
> .../devicetree/bindings/remoteproc/qcom,venus.txt | 26 ++++-
> drivers/remoteproc/qcom_venus_pil.c | 116 ++++++++++++++++++++-
> 2 files changed, 140 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,venus.txt b/Documentation/devicetree/bindings/remoteproc/qcom,venus.txt
> index 2d73ba1..417026b 100644
> --- a/Documentation/devicetree/bindings/remoteproc/qcom,venus.txt
> +++ b/Documentation/devicetree/bindings/remoteproc/qcom,venus.txt
> @@ -6,13 +6,30 @@ on the Qualcomm Venus remote processor core.
> - compatible:
> Usage: required
> Value type: <string>
> - Definition: must contain "qcom,venus-pil"
> + Definition: must contain "qcom,venus-pil" or
> + "qcom,venus-msm8996-pil"
>
> - memory-region:
> Usage: required
> Value type: <phandle>
> Definition: a phandle to a node describing reserved memory
>
> +- clocks:
> + Usage: required
> + Value type: <prop-encoded-array>
> + Definition: reference to the core, iface and bus and maxi clocks to be held on
> + behalf of the booting of the venus core
> +
> +- clock-names:
> + Usage: required
> + Value type: <stringlist>
> + Definition: should be "core_clk", "iface_clk", "bus_clk", "maxi_clk"
Please drop _clk from all clock names.
> +
> +- power-domains:
> + Usage: required
> + Value type: <prop-encoded-array>
> + Definition: reference to the venus gdsc to be turned on before booting venus core
All these new properties can't be required if the original
compatible is used, right?
> +
> * An example
> reserved-memory {
> #address-cells = <2>;
> @@ -29,5 +46,12 @@ on the Qualcomm Venus remote processor core.
>
> rproc_venus@0 {
> compatible = "qcom,venus-pil";
> + clocks = <&mmcc VIDEO_CORE_CLK>,
> + <&mmcc VIDEO_AHB_CLK>,
> + <&mmcc VIDEO_AXI_CLK>,
> + <&mmcc VIDEO_MAXI_CLK>;
> +
> + clock-names = "core_clk", "iface_clk", "bus_clk", "maxi_clk";
> + power-domains = <&mmcc VENUS_GDSC>;
> memory-region = <&venus_mem>;
> };
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-11-29 19:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 10:50 [RESEND PATCH v2] remoteproc: qcom: Venus firmware loader support for msm8996 Avaneesh Kumar Dwivedi
2016-11-29 10:50 ` [RESEND PATCH v2] remoteproc: qcom: Add venus rproc support on msm8996 platform Avaneesh Kumar Dwivedi
2016-11-29 19:27 ` Stephen Boyd [this message]
2016-11-30 5:24 ` Dwivedi, Avaneesh Kumar (avani)
2016-11-30 9:22 ` Stanimir Varbanov
2016-12-05 9:46 ` Dwivedi, Avaneesh Kumar (avani)
2016-12-07 10:49 ` Stanimir Varbanov
2016-12-13 6:51 ` Bjorn Andersson
2016-12-17 0:56 ` Stephen Boyd
2016-12-17 7:11 ` Bjorn Andersson
2016-12-21 6:40 ` Dwivedi, Avaneesh Kumar (avani)
2017-01-25 12:37 ` Stanimir Varbanov
2016-11-29 19:24 ` [RESEND PATCH v2] remoteproc: qcom: Venus firmware loader support for msm8996 Stephen Boyd
2016-11-30 5:15 ` Dwivedi, Avaneesh Kumar (avani)
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=20161129192702.GA6095@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=akdwived@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=stanimir.varbanov@linaro.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.