From: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
To: jorge.ramirez-ortiz@linaro.org, sboyd@kernel.org,
agross@kernel.org, mturquette@baylibre.com,
bjorn.andersson@linaro.org
Cc: niklas.cassel@linaro.org, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/5] Clock changes to support cpufreq on QCS404
Date: Thu, 12 Sep 2019 16:15:29 +0200 [thread overview]
Message-ID: <20190912141534.28870-1-jorge.ramirez-ortiz@linaro.org> (raw)
The following clock changes are required to enable cpufreq support on
the QCS404
v2: sboyd review of v1
-------------------
missing cover letter
reorder the patchset
use clk_parent data to speficy the parent clock
dong ignore the clock position abi
Jorge Ramirez-Ortiz (5):
clk: qcom: gcc: limit GPLL0_AO_OUT operating frequency
clk: qcom: hfpll: register as clock provider
clk: qcom: hfpll: CLK_IGNORE_UNUSED
clk: qcom: hfpll: use clk_parent_data to specify the parent
clk: qcom: apcs-msm8916: get parent clock names from DT
drivers/clk/qcom/apcs-msm8916.c | 15 ++++++++++++---
drivers/clk/qcom/clk-alpha-pll.c | 8 ++++++++
drivers/clk/qcom/clk-alpha-pll.h | 1 +
drivers/clk/qcom/gcc-qcs404.c | 2 +-
drivers/clk/qcom/hfpll.c | 21 +++++++++++++++++++--
5 files changed, 41 insertions(+), 6 deletions(-)
--
2.23.0
next reply other threads:[~2019-09-12 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 14:15 Jorge Ramirez-Ortiz [this message]
2019-09-12 14:15 ` [PATCH v2 1/5] clk: qcom: gcc: limit GPLL0_AO_OUT operating frequency Jorge Ramirez-Ortiz
2019-09-12 14:15 ` [PATCH v2 2/5] clk: qcom: hfpll: register as clock provider Jorge Ramirez-Ortiz
2019-09-12 14:15 ` [PATCH v2 3/5] clk: qcom: hfpll: CLK_IGNORE_UNUSED Jorge Ramirez-Ortiz
2019-09-12 14:15 ` [PATCH v2 4/5] clk: qcom: hfpll: use clk_parent_data to specify the parent Jorge Ramirez-Ortiz
2019-09-12 14:15 ` [PATCH v2 5/5] clk: qcom: apcs-msm8916: get parent clock names from DT Jorge Ramirez-Ortiz
2019-11-07 22:19 ` 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=20190912141534.28870-1-jorge.ramirez-ortiz@linaro.org \
--to=jorge.ramirez-ortiz@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.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=niklas.cassel@linaro.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 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).