From: Manivannan Sadhasivam <mani@kernel.org>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
andersson@kernel.org, viresh.kumar@linaro.org,
krzysztof.kozlowski+dt@linaro.org, rafael@kernel.org,
robh+dt@kernel.org, johan@kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v5 3/3] cpufreq: qcom-hw: Add CPU clock provider support
Date: Wed, 9 Nov 2022 13:25:27 +0530 [thread overview]
Message-ID: <20221109075527.GD4651@thinkpad> (raw)
In-Reply-To: <Y2qfmFVK665b1Nbw@google.com>
On Tue, Nov 08, 2022 at 06:27:36PM +0000, Matthias Kaehlcke wrote:
> Hi,
>
> On Tue, Nov 08, 2022 at 09:10:37PM +0530, Manivannan Sadhasivam wrote:
> > Qcom CPUFreq hardware (EPSS/OSM) controls clock and voltage to the CPU
> > cores. But this relationship is not represented with the clk framework
> > so far.
> >
> > So, let's make the qcom-cpufreq-hw driver a clock provider. This makes the
> > clock producer/consumer relationship cleaner and is also useful for CPU
> > related frameworks like OPP to know the frequency at which the CPUs are
> > running.
> >
> > The clock frequency provided by the driver is for each frequency domain.
> > We cannot get the frequency of each CPU core because, not all platforms
> > support per-core DCVS feature.
> >
> > Also the frequency supplied by the driver is the actual frequency that
> > comes out of the EPSS/OSM block after the DCVS operation. This frequency is
> > not same as what the CPUFreq framework has set but it is the one that gets
> > supplied to the CPUs after throttling by LMh.
> >
> > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> > ---
> > drivers/cpufreq/qcom-cpufreq-hw.c | 43 +++++++++++++++++++++++++++++++
> > 1 file changed, 43 insertions(+)
> >
> > diff --git a/drivers/cpufreq/qcom-cpufreq-hw.c b/drivers/cpufreq/qcom-cpufreq-hw.c
> > index 5e0598730a04..86bb11de347f 100644
> > --- a/drivers/cpufreq/qcom-cpufreq-hw.c
> > +++ b/drivers/cpufreq/qcom-cpufreq-hw.c
> > @@ -4,6 +4,7 @@
> > */
> >
> > #include <linux/bitfield.h>
> > +#include <linux/clk-provider.h>
> > #include <linux/cpufreq.h>
> > #include <linux/init.h>
> > #include <linux/interconnect.h>
> > @@ -54,6 +55,7 @@ struct qcom_cpufreq_data {
> > bool cancel_throttle;
> > struct delayed_work throttle_work;
> > struct cpufreq_policy *policy;
> > + struct clk_hw cpu_clk;
> >
> > bool per_core_dcvs;
> >
> > @@ -615,8 +617,20 @@ static struct cpufreq_driver cpufreq_qcom_hw_driver = {
> > .ready = qcom_cpufreq_ready,
> > };
> >
> > +static unsigned long qcom_cpufreq_hw_recalc_rate(struct clk_hw *hw, unsigned long parent_rate)
> > +{
> > + struct qcom_cpufreq_data *data = container_of(hw, struct qcom_cpufreq_data, cpu_clk);
> > +
> > + return qcom_lmh_get_throttle_freq(data);
> > +}
> > +
> > +static const struct clk_ops qcom_cpufreq_hw_clk_ops = {
> > + .recalc_rate = qcom_cpufreq_hw_recalc_rate,
> > +};
> > +
> > static int qcom_cpufreq_hw_driver_probe(struct platform_device *pdev)
> > {
> > + struct clk_hw_onecell_data *clk_data;
> > struct device *dev = &pdev->dev;
> > struct device *cpu_dev;
> > struct clk *clk;
> > @@ -659,8 +673,16 @@ static int qcom_cpufreq_hw_driver_probe(struct platform_device *pdev)
> >
> > qcom_cpufreq.soc_data = of_device_get_match_data(dev);
> >
> > + clk_data = devm_kzalloc(dev, struct_size(clk_data, hws, num_domains), GFP_KERNEL);
> > + if (!clk_data)
> > + return -ENOMEM;
> > +
> > + clk_data->num = num_domains;
> > +
> > for (i = 0; i < num_domains; i++) {
> > struct qcom_cpufreq_data *data = &qcom_cpufreq.data[i];
> > + struct clk_init_data init = {};
> > + const char *clk_name;
> > struct resource *res;
> > void __iomem *base;
> >
> > @@ -672,6 +694,27 @@ static int qcom_cpufreq_hw_driver_probe(struct platform_device *pdev)
> >
> > data->base = base;
> > data->res = res;
> > +
> > + /* Register CPU clock for each frequency domain */
> > + clk_name = devm_kasprintf(dev, GFP_KERNEL, "qcom_cpufreq%d", i);
> > + init.name = clk_name;
>
> nit: 'clk_name' isn't really needed, the result of devm_kasprintf() could be
> assigned directly to 'init.name'. 'init' could be renamed to 'clk_init' if
> the purpose of using 'clk_name' is to make clear that this is the name of a
> clock.
>
Ack.
Thanks,
Mani
> > + init.flags = CLK_GET_RATE_NOCACHE;
> > + init.ops = &qcom_cpufreq_hw_clk_ops;
> > + data->cpu_clk.init = &init;
> > +
> > + ret = devm_clk_hw_register(dev, &data->cpu_clk);
> > + if (ret < 0) {
> > + dev_err(dev, "Failed to register Qcom CPUFreq clock\n");
> > + return ret;
> > + }
> > +
> > + clk_data->hws[i] = &data->cpu_clk;
> > + }
> > +
> > + ret = devm_of_clk_add_hw_provider(dev, of_clk_hw_onecell_get, clk_data);
> > + if (ret < 0) {
> > + dev_err(dev, "Failed to add Qcom CPUFreq clock provider\n");
> > + return ret;
> > }
> >
> > ret = cpufreq_register_driver(&cpufreq_qcom_hw_driver);
> > --
> > 2.25.1
> >
--
மணிவண்ணன் சதாசிவம்
prev parent reply other threads:[~2022-11-09 7:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 15:40 [PATCH v5 0/3] qcom-cpufreq-hw: Add CPU clock provider support Manivannan Sadhasivam
2022-11-08 15:40 ` [PATCH v5 1/3] dt-bindings: cpufreq: cpufreq-qcom-hw: Add cpufreq clock provider Manivannan Sadhasivam
2022-11-08 15:40 ` [PATCH v5 2/3] arm64: dts: qcom: sm8450: Supply clock from cpufreq node to CPUs Manivannan Sadhasivam
2022-11-08 15:40 ` [PATCH v5 3/3] cpufreq: qcom-hw: Add CPU clock provider support Manivannan Sadhasivam
2022-11-08 15:57 ` Sudeep Holla
2022-11-09 7:49 ` Manivannan Sadhasivam
2022-11-09 11:08 ` Sudeep Holla
2022-11-09 12:35 ` Manivannan Sadhasivam
2022-11-09 16:47 ` Sudeep Holla
2022-11-14 3:16 ` Viresh Kumar
2022-11-14 6:25 ` Manivannan Sadhasivam
2022-11-14 6:51 ` Viresh Kumar
2022-11-08 18:27 ` Matthias Kaehlcke
2022-11-09 7:55 ` Manivannan Sadhasivam [this message]
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=20221109075527.GD4651@thinkpad \
--to=mani@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mka@chromium.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=viresh.kumar@linaro.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).