From: Rajendra Nayak <rnayak@codeaurora.org>
To: mturquette@baylibre.com, sboyd@codeaurora.org
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Rajendra Nayak <rnayak@codeaurora.org>
Subject: [PATCH 0/6] Add support for MSM8996 GDSCs
Date: Thu, 26 Nov 2015 11:24:51 +0530 [thread overview]
Message-ID: <1448517297-32419-1-git-send-email-rnayak@codeaurora.org> (raw)
This series adds support for GDSCs' which are part of gcc and mmcc
in QCOM msm8996 SoC. Series applies on top of the patches[1] which
adds support for MSM8996 clocks.
There are many more cases of gdscs within gdscs (hierarchical power
domains) in msm8996 (msm8974 has one such instance which is supported
upstream) and hence the series adds support within gdsc driver to
handle this.
Also msm8996 has gdscs with gds hw controllers within, for ensuring
slave device idleness before gdscs are powered off, hence the series
also adds support for gdscs with gds hw controllers.
ToDo: Series does not yet add support for gpu gdscs which are part
of mmcc.
Tested on apq8096 dragonboards to make sure all modelled gdscs can
be turned on/off successfully.
[1] https://lkml.org/lkml/2015/11/17/949
Rajendra Nayak (6):
clk: qcom: gdsc: Add support for hierarchical power domains
clk: qcom: gdsc: Add support for gdscs with gds hw controller
clk: qcom: gdsc: Add GDSCs in msm8996 GCC
clk: qcom: gdsc: Add mmcc gdscs for msm8996 family
clk: qcom: gdsc: Do not check for disabled status on votable gdscs
clk: qcom: mmcc8974: Use gdscs .parent and remove genpd calls
arch/arm64/boot/dts/qcom/msm8996.dtsi | 2 +
drivers/clk/qcom/common.c | 14 ++-
drivers/clk/qcom/gcc-msm8996.c | 92 +++++++++++++++
drivers/clk/qcom/gdsc.c | 69 ++++++++---
drivers/clk/qcom/gdsc.h | 34 ++++--
drivers/clk/qcom/mmcc-msm8974.c | 14 +--
drivers/clk/qcom/mmcc-msm8996.c | 157 ++++++++++++++++++++++++++
include/dt-bindings/clock/qcom,gcc-msm8996.h | 11 ++
include/dt-bindings/clock/qcom,mmcc-msm8996.h | 17 +++
9 files changed, 363 insertions(+), 47 deletions(-)
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
next reply other threads:[~2015-11-26 5:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 5:54 Rajendra Nayak [this message]
2015-11-26 5:54 ` [PATCH 1/6] clk: qcom: gdsc: Add support for hierarchical power domains Rajendra Nayak
2015-11-26 5:54 ` [PATCH 2/6] clk: qcom: gdsc: Add support for gdscs with gds hw controller Rajendra Nayak
2015-12-01 2:22 ` Stephen Boyd
2015-12-01 3:08 ` Rajendra Nayak
2015-12-01 7:27 ` Stephen Boyd
2015-12-01 16:01 ` Rajendra Nayak
2015-11-26 5:54 ` [PATCH 3/6] clk: qcom: gdsc: Add GDSCs in msm8996 GCC Rajendra Nayak
2015-11-26 5:54 ` [PATCH 4/6] clk: qcom: gdsc: Add mmcc gdscs for msm8996 family Rajendra Nayak
2015-11-26 5:54 ` [PATCH 5/6] clk: qcom: gdsc: Do not check for disabled status on votable gdscs Rajendra Nayak
2015-12-01 1:53 ` Stephen Boyd
2015-12-01 3:03 ` Rajendra Nayak
2015-11-26 5:54 ` [PATCH 6/6] clk: qcom: mmcc8974: Use gdscs .parent and remove genpd calls Rajendra Nayak
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=1448517297-32419-1-git-send-email-rnayak@codeaurora.org \
--to=rnayak@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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).