From: Taniya Das <tdas@codeaurora.org>
To: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>
Cc: Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
Amit Nischal <anischal@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Taniya Das <tdas@codeaurora.org>
Subject: [PATCH v4 2/2] clk: qcom: gcc: Register QUPv3 RCGs for DFS on SDM845
Date: Sat, 11 Aug 2018 07:23:56 +0530 [thread overview]
Message-ID: <1533952436-17221-3-git-send-email-tdas@codeaurora.org> (raw)
In-Reply-To: <1533952436-17221-1-git-send-email-tdas@codeaurora.org>
QUPv3 clocks support DFS and thus register the RCGs which require support
for the same.
Signed-off-by: Taniya Das <tdas@codeaurora.org>
---
drivers/clk/qcom/gcc-sdm845.c | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
diff --git a/drivers/clk/qcom/gcc-sdm845.c b/drivers/clk/qcom/gcc-sdm845.c
index fa1a196..fef6732 100644
--- a/drivers/clk/qcom/gcc-sdm845.c
+++ b/drivers/clk/qcom/gcc-sdm845.c
@@ -3458,9 +3458,29 @@ enum {
};
MODULE_DEVICE_TABLE(of, gcc_sdm845_match_table);
+static struct clk_rcg2 *gcc_dfs_clocks[] = {
+ &gcc_qupv3_wrap0_s0_clk_src,
+ &gcc_qupv3_wrap0_s1_clk_src,
+ &gcc_qupv3_wrap0_s2_clk_src,
+ &gcc_qupv3_wrap0_s3_clk_src,
+ &gcc_qupv3_wrap0_s4_clk_src,
+ &gcc_qupv3_wrap0_s5_clk_src,
+ &gcc_qupv3_wrap0_s6_clk_src,
+ &gcc_qupv3_wrap0_s7_clk_src,
+ &gcc_qupv3_wrap1_s0_clk_src,
+ &gcc_qupv3_wrap1_s1_clk_src,
+ &gcc_qupv3_wrap1_s2_clk_src,
+ &gcc_qupv3_wrap1_s3_clk_src,
+ &gcc_qupv3_wrap1_s4_clk_src,
+ &gcc_qupv3_wrap1_s5_clk_src,
+ &gcc_qupv3_wrap1_s6_clk_src,
+ &gcc_qupv3_wrap1_s7_clk_src,
+};
+
static int gcc_sdm845_probe(struct platform_device *pdev)
{
struct regmap *regmap;
+ int ret;
regmap = qcom_cc_map(pdev, &gcc_sdm845_desc);
if (IS_ERR(regmap))
@@ -3470,6 +3490,11 @@ static int gcc_sdm845_probe(struct platform_device *pdev)
regmap_update_bits(regmap, 0x09ffc, 0x3, 0x3);
regmap_update_bits(regmap, 0x71028, 0x3, 0x3);
+ ret = qcom_cc_register_rcg_dfs(regmap, gcc_dfs_clocks,
+ ARRAY_SIZE(gcc_dfs_clocks));
+ if (ret)
+ return ret;
+
return qcom_cc_really_probe(pdev, &gcc_sdm845_desc, regmap);
}
--
Qualcomm INDIA, on behalf of Qualcomm Innovation Center, Inc.is a member
of the Code Aurora Forum, hosted by the Linux Foundation.
next prev parent reply other threads:[~2018-08-11 1:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-11 1:53 [PATCH v4 0/2] clk: qcom: Add support for RCG to register for DFS Taniya Das
2018-08-11 1:53 ` [PATCH v4 1/2] " Taniya Das
2018-08-11 1:53 ` Taniya Das [this message]
2018-08-18 2:12 ` [PATCH v4 0/2] " Stephen Boyd
2018-08-18 2:12 ` Stephen Boyd
2018-08-18 2:12 ` Stephen Boyd
2018-08-18 18:01 ` Taniya Das
2018-08-21 11:36 ` Taniya Das
2018-08-21 15:30 ` Stephen Boyd
2018-08-21 15:30 ` Stephen Boyd
2018-08-22 10:28 ` Taniya Das
2018-08-23 18:25 ` Stephen Boyd
2018-08-23 18:25 ` Stephen Boyd
2018-08-27 21:04 ` Stephen Boyd
2018-08-27 21:04 ` Stephen Boyd
2018-08-28 9:06 ` Taniya Das
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=1533952436-17221-3-git-send-email-tdas@codeaurora.org \
--to=tdas@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=anischal@codeaurora.org \
--cc=david.brown@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rnayak@codeaurora.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.