From: Sudeep Holla <sudeep.holla@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Cristian Marussi <cristian.marussi@arm.com>,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH] cpufreq: scmi: Fix OPP addition failure with a dummy clock provider
Date: Wed, 11 Nov 2020 11:05:13 +0000 [thread overview]
Message-ID: <20201111110513.but7tzvmkoxqmwlb@bogus> (raw)
In-Reply-To: <20201110112414.abrqtf4v76sth54m@vireshk-i7>
On Tue, Nov 10, 2020 at 04:54:14PM +0530, Viresh Kumar wrote:
> On 10-11-20, 11:10, Sudeep Holla wrote:
> > Commit dd461cd9183f ("opp: Allow dev_pm_opp_get_opp_table() to return
> > -EPROBE_DEFER") handles -EPROBE_DEFER for the clock/interconnects within
> > _allocate_opp_table() which is called from dev_pm_opp_add and it
> > now propagates the error back to the caller.
> >
> > SCMI performance domain re-used clock bindings to keep it simple. However
> > with the above mentioned change, if clock property is present in a device
> > node, opps fails to get added with below errors until clk_get succeeds.
> >
> > cpu0: failed to add opp 450000000Hz
> > cpu0: failed to add opps to the device
> > ....(errors on cpu1-cpu4)
> > cpu5: failed to add opp 450000000Hz
> > cpu5: failed to add opps to the device
> >
> > So, in order to fix the issue, we need to register dummy clock provider.
> > With the dummy clock provider, clk_get returns NULL(no errors!), then opp
> > core proceeds to add OPPs for the CPUs.
> >
> > Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
> > Cc: Viresh Kumar <viresh.kumar@linaro.org>
> > Fixes: dd461cd9183f ("opp: Allow dev_pm_opp_get_opp_table() to return -EPROBE_DEFER")
> > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> > ---
> > drivers/cpufreq/scmi-cpufreq.c | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/drivers/cpufreq/scmi-cpufreq.c b/drivers/cpufreq/scmi-cpufreq.c
> > index e855e8612a67..78318508a6d6 100644
> > --- a/drivers/cpufreq/scmi-cpufreq.c
> > +++ b/drivers/cpufreq/scmi-cpufreq.c
> > @@ -8,6 +8,7 @@
> >
> > #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
> >
> > +#include <linux/clk-provider.h>
> > #include <linux/cpu.h>
> > #include <linux/cpufreq.h>
> > #include <linux/cpumask.h>
> > @@ -228,12 +229,17 @@ static struct cpufreq_driver scmi_cpufreq_driver = {
> > static int scmi_cpufreq_probe(struct scmi_device *sdev)
> > {
> > int ret;
> > + struct device *dev = &sdev->dev;
> >
> > handle = sdev->handle;
> >
> > if (!handle || !handle->perf_ops)
> > return -ENODEV;
> >
> > + /* dummy clock provider as needed by OPP if clocks property is used */
> > + if (of_find_property(dev->of_node, "#clock-cells", NULL))
> > + devm_of_clk_add_hw_provider(dev, of_clk_hw_simple_get, NULL);
> > +
> > ret = cpufreq_register_driver(&scmi_cpufreq_driver);
> > if (ret) {
> > dev_err(&sdev->dev, "%s: registering cpufreq failed, err: %d\n",
>
> For 5.10-rc.
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>
Thanks Viresh, I assume Rafael will take this directly as fix for v5.10
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-11 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 11:10 [PATCH] cpufreq: scmi: Fix OPP addition failure with a dummy clock provider Sudeep Holla
2020-11-10 11:24 ` Viresh Kumar
2020-11-11 11:05 ` Sudeep Holla [this message]
2020-11-17 4:35 ` Viresh Kumar
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=20201111110513.but7tzvmkoxqmwlb@bogus \
--to=sudeep.holla@arm.com \
--cc=cristian.marussi@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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