From: Govind Singh <govinds@codeaurora.org>
To: robh@kernel.org, sboyd@kernel.org
Cc: bjorn.andersson@linaro.org, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-soc@vger.kernel.org, linux-remoteproc@vger.kernel.org,
Govind Singh <govinds@codeaurora.org>
Subject: [PATCH v4 0/2] Add Q6SSTOP clock controller for QCS404
Date: Fri, 11 Oct 2019 18:59:26 +0530 [thread overview]
Message-ID: <20191011132928.9388-1-govinds@codeaurora.org> (raw)
Add support for the Q6SSTOP clock control used on qcs404
based devices. This would allow wcss remoteproc driver to
control the required WCSS Q6SSTOP clock/reset controls to
bring the subsystem out of reset and shutdown the WCSS Q6DSP.
Changes in v4:
- changed binding doc license to (GPL-2.0-only OR BSD-2-Clause).
Changes in v3:
- Fixed dt binding errors.
Changes in v2:
- changed binding doc to yaml format.
- Fixed alignment in q6sstop cc driver.
Govind Singh (2):
dt-bindings: clock: qcom: Add QCOM Q6SSTOP clock controller bindings
clk: qcom: Add Q6SSTOP clock controller for QCS404
.../bindings/clock/qcom,q6sstopcc.yaml | 43 ++++
drivers/clk/qcom/Kconfig | 8 +
drivers/clk/qcom/Makefile | 1 +
drivers/clk/qcom/q6sstop-qcs404.c | 223 ++++++++++++++++++
.../dt-bindings/clock/qcom,q6sstopcc-qcs404.h | 18 ++
5 files changed, 293 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/qcom,q6sstopcc.yaml
create mode 100644 drivers/clk/qcom/q6sstop-qcs404.c
create mode 100644 include/dt-bindings/clock/qcom,q6sstopcc-qcs404.h
--
2.22.0
next reply other threads:[~2019-10-11 13:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 13:29 Govind Singh [this message]
2019-10-11 13:29 ` [PATCH v4 1/2] dt-bindings: clock: qcom: Add QCOM Q6SSTOP clock controller bindings Govind Singh
2019-10-14 14:40 ` Rob Herring
2019-10-14 14:40 ` Rob Herring
2019-11-07 19:32 ` Stephen Boyd
2019-11-07 19:32 ` Stephen Boyd
2019-10-11 13:29 ` [PATCH v4 2/2] clk: qcom: Add Q6SSTOP clock controller for QCS404 Govind Singh
2019-11-07 19:32 ` Stephen Boyd
2019-11-07 19:32 ` Stephen Boyd
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=20191011132928.9388-1-govinds@codeaurora.org \
--to=govinds@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.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=robh@kernel.org \
--cc=sboyd@kernel.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.