From: Govind Singh <govinds@codeaurora.org>
To: bjorn.andersson@linaro.org, linux-remoteproc@vger.kernel.org,
sricharan@codeaurora.org, sibis@codeaurora.org,
linux-arm-msm@vger.kernel.org, andy.gross@linaro.org,
david.brown@linaro.org, linux-soc@vger.kernel.org,
devicetree@vger.kernel.org
Cc: Govind Singh <govinds@codeaurora.org>
Subject: [PATCH v2 0/6] Add non PAS wcss Q6 support for QCS404
Date: Fri, 12 Oct 2018 15:10:38 +0530 [thread overview]
Message-ID: <1539337244-9505-1-git-send-email-govinds@codeaurora.org> (raw)
Add non PAS(Peripheral Authentication System) WCSS remoteproc
driver support and wcss clock/reset controls for QCS404 SOC.
Add WCSS q6 bootup and shutdown sequence handled from
Application Processor SubSystem(APSS).
Govind Singh (6):
dt-bindings: clock: qcom: Add QCOM WCSS GCC clock bindings
clk: qcom: Add WCSS gcc clock control for QCS404
dt-bindings: clock: qcom: Introduce QCOM WCSS Q6DSP clock bindings
clk: qcom: Add WCSS Q6DSP clock controller for QCS404
remoteproc: qcom: wcss: populate hardcoded param using driver data
remoteproc: qcom: wcss: Add non pas wcss Q6 support for QCS404
Changes since v1:
Corrected clock names as per comments in v1 patch.
.../devicetree/bindings/clock/qcom,wcsscc.txt | 26 +
.../devicetree/bindings/remoteproc/qcom,q6v5.txt | 1 +
drivers/clk/qcom/Kconfig | 9 +
drivers/clk/qcom/Makefile | 1 +
drivers/clk/qcom/gcc-qcs404.c | 37 +-
drivers/clk/qcom/wcsscc-qcs404.c | 290 +++++++++
drivers/remoteproc/qcom_q6v5_wcss.c | 666 +++++++++++++++++++--
include/dt-bindings/clock/qcom,gcc-qcs404.h | 3 +
include/dt-bindings/clock/qcom,wcss-qcs404.h | 24 +
9 files changed, 1018 insertions(+), 39 deletions(-)
create mode 100644 Documentation/devicetree/bindings/clock/qcom,wcsscc.txt
create mode 100644 drivers/clk/qcom/wcsscc-qcs404.c
create mode 100644 include/dt-bindings/clock/qcom,wcss-qcs404.h
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2018-10-12 17:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 9:40 Govind Singh [this message]
2018-10-12 9:40 ` [PATCH v2 1/6] dt-bindings: clock: qcom: Add QCOM WCSS GCC clock bindings Govind Singh
2018-10-17 20:02 ` Rob Herring
2018-10-12 9:40 ` [PATCH v2 2/6] clk: qcom: Add WCSS gcc clock control for QCS404 Govind Singh
2018-10-16 1:01 ` Stephen Boyd
2018-12-15 17:43 ` Govind Singh
2018-10-12 9:40 ` [PATCH v2 3/6] dt-bindings: clock: qcom: Introduce QCOM WCSS Q6DSP clock bindings Govind Singh
2018-10-17 20:05 ` Rob Herring
2018-10-12 9:40 ` [PATCH v2 4/6] clk: qcom: Add WCSS Q6DSP clock controller for QCS404 Govind Singh
2018-10-16 1:00 ` Stephen Boyd
2018-12-15 17:50 ` Govind Singh
2018-10-12 9:40 ` [PATCH v2 5/6] remoteproc: qcom: wcss: populate hardcoded param using driver data Govind Singh
2018-10-12 9:40 ` [PATCH v2 6/6] remoteproc: qcom: wcss: Add non pas wcss Q6 support for QCS404 Govind Singh
2018-10-17 20:08 ` Rob Herring
2018-12-06 16:48 ` Bjorn Andersson
2018-12-15 18:00 ` Govind Singh
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=1539337244-9505-1-git-send-email-govinds@codeaurora.org \
--to=govinds@codeaurora.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-remoteproc@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=sibis@codeaurora.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).