linux-remoteproc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: gokulsri@codeaurora.org
To: bjorn.andersson@linaro.org, linux-remoteproc@vger.kernel.org,
	sboyd@kernel.org, linux-clk@vger.kernel.org,
	linux-arm-msm@vger.kernel.org
Cc: agross@kernel.org, linux-soc@vger.kernel.org,
	devicetree@vger.kernel.org, govinds@codeaurora.org,
	sricharan@codeaurora.org
Subject: Re: [PATCH v8 0/4] Add non PAS wcss Q6 support for QCS404
Date: Tue, 25 Aug 2020 17:30:02 +0530	[thread overview]
Message-ID: <3476a019b5b847de979fb327183c3239@codeaurora.org> (raw)
In-Reply-To: <1596111244-28411-1-git-send-email-gokulsri@codeaurora.org>

Bjorn,

Awaiting your rewiew on this series [PATCH v8 0/4] Add non PAS wcss Q6 
support for QCS404 and the dependant series [v7,0/9] remoteproc: qcom: 
q6v5-wcss: Add support for secure pil 
(https://patchwork.kernel.org/cover/11692941/)


Thanks,
Gokul

On 2020-07-30 17:44, Gokul Sriram Palanisamy wrote:
> Changes since v7:
>  Addressed review comments from	Stephen Boyd
> 
> Changes since v6:
>  Removed duplicate structure entry added during rebase in v5
> 
> Changes since v5:
>  Rebased all the unmerged patches on top of linux-5.8-rc3
>  Added dt-binding for qcom,qcs404-wcss-pil
>  Removed typo
> 
> Changes since v4:
>  removed QDSP6SS clock controls and moved to wcss rproc.
>  renamed wcsccc to q6sstopcc.
>  cleanup/refactoring.
> 
> Changes since v3:
>  dt binding cleanup.
>  Fixed remoteproc recovery.
>  Added remoteproc dump support.
>  wcsscc cleanup/refactoring.
> 
> Changes since v2:
>  Removed unused properties.
>  Refactored code to have common logic b/w ipq8074 and QCS404, wherever 
> possible.
>  Added compatible example.
>  Removed wcss-protected bool.
> 
> Changes since v1:
>   Corrected clock names as per comments in v1 patch.
> 
> Govind Singh (4):
>   remoteproc: qcom: wcss: populate hardcoded param using driver data
>   dt-bindings: remoteproc: qcom: Add Q6V5 Modem PIL binding for QCS404
>   remoteproc: qcom: wcss: Add non pas wcss Q6 support for QCS404
>   remoteproc: qcom: wcss: explicitly request exclusive reset control
> 
>  .../devicetree/bindings/remoteproc/qcom,q6v5.txt   |   9 +
>  drivers/remoteproc/qcom_q6v5_wcss.c                | 591 
> +++++++++++++++++++--
>  2 files changed, 558 insertions(+), 42 deletions(-)

      parent reply	other threads:[~2020-08-25 12:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-30 12:14 [PATCH v8 0/4] Add non PAS wcss Q6 support for QCS404 Gokul Sriram Palanisamy
2020-07-30 12:14 ` [PATCH v8 1/4] remoteproc: qcom: wcss: populate hardcoded param using driver data Gokul Sriram Palanisamy
2020-07-30 12:14 ` [PATCH v8 2/4] dt-bindings: remoteproc: qcom: Add Q6V5 Modem PIL binding for QCS404 Gokul Sriram Palanisamy
2020-07-30 12:14 ` [PATCH v8 3/4] remoteproc: qcom: wcss: Add non pas wcss Q6 support " Gokul Sriram Palanisamy
2020-07-30 12:14 ` [PATCH v8 4/4] remoteproc: qcom: wcss: explicitly request exclusive reset control Gokul Sriram Palanisamy
2020-08-25 12:00 ` gokulsri [this message]

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=3476a019b5b847de979fb327183c3239@codeaurora.org \
    --to=gokulsri@codeaurora.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=govinds@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=linux-soc@vger.kernel.org \
    --cc=sboyd@kernel.org \
    --cc=sricharan@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;
as well as URLs for NNTP newsgroup(s).