From: Michael Turquette <mike.turquette@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH 1/2] cpufreq: arm_big_little: check if the frequency is set correctly
Date: Mon, 30 Mar 2015 18:48:54 -0700 [thread overview]
Message-ID: <20150331014854.25195.34023@quantum> (raw)
In-Reply-To: <551951F4.9070804@arm.com>
Quoting Sudeep Holla (2015-03-30 06:39:00)
>
>
> On 30/03/15 14:27, Viresh Kumar wrote:
> > On 30 March 2015 at 17:57, Sudeep Holla <sudeep.holla@arm.com> wrote:
> >> The actual frequency is set through "clk_change_rate" which is void
> >> function. If the underlying hardware fails and returns error, the error
> >> is lost in the clk layer. In order to track such failures, we need to
> >> read back the frequency(just the cached value as clk_recalc called after
> >> clk->ops->set_rate gets the frequency)
> >>
> >> This patch adds check to see if the frequency is set correctly or if
> >> they were any hardware failures and sends the appropriate errors to the
> >> cpufreq core.
> >>
> >> Cc: Viresh Kumar <viresh.kumar@linaro.org>
> >> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> >> ---
> >> drivers/cpufreq/arm_big_little.c | 2 ++
> >> 1 file changed, 2 insertions(+)
> >>
> >> diff --git a/drivers/cpufreq/arm_big_little.c b/drivers/cpufreq/arm_big_little.c
> >> index e1a6ba66a7f5..3fc676c63f91 100644
> >> --- a/drivers/cpufreq/arm_big_little.c
> >> +++ b/drivers/cpufreq/arm_big_little.c
> >> @@ -186,6 +186,8 @@ bL_cpufreq_set_rate(u32 cpu, u32 old_cluster, u32 new_cluster, u32 rate)
> >> mutex_unlock(&cluster_lock[old_cluster]);
> >> }
> >>
> >> + if (bL_cpufreq_get_rate(cpu) != new_rate)
> >> + return -EIO;
> >> return 0;
> >> }
> >
> > This doesn't look to me the right place for fixing this.
> >
>
> Yes I agree, after going through clk.c, I thought pre-/post- notifiers
> are designed for such purpose. I tried using them but found it
> unnecessary when it can be as simple as in this patch. However it's good
> to hear from Mike as I seem to have assumed a lot here.
Viresh & Sudeep,
clk_set_rate returns an error (and always has), so it seems to me that
this patch is unnecessary. bL_cpufreq_set_rate checks for an error from
clk_set_rate and handles it.
clk_change_rate is static and not exposed outside of drivers/clk/clk.c.
This patch gets a NAK from me.
Regards,
Mike
>
> Regards,
> Sudeep
next prev parent reply other threads:[~2015-03-31 1:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 12:27 [PATCH 1/2] cpufreq: arm_big_little: check if the frequency is set correctly Sudeep Holla
2015-03-30 12:27 ` [PATCH 2/2] cpufreq: arm_big_little: remove unused cpu-cluster.<n> clock name Sudeep Holla
2015-03-30 13:31 ` Viresh Kumar
2015-03-30 13:39 ` Sudeep Holla
2015-03-30 13:27 ` [PATCH 1/2] cpufreq: arm_big_little: check if the frequency is set correctly Viresh Kumar
2015-03-30 13:39 ` Sudeep Holla
2015-03-31 1:48 ` Michael Turquette [this message]
2015-03-31 9:24 ` Sudeep Holla
2015-04-01 10:01 ` Sudeep Holla
2015-04-01 21:48 ` Michael Turquette
2015-04-02 8:55 ` Sudeep Holla
2015-04-13 5:08 ` Michael Turquette
2015-04-13 10:21 ` Sudeep Holla
2015-04-13 10:25 ` Viresh Kumar
2015-04-13 15:14 ` Sudeep Holla
-- strict thread matches above, loose matches on Subject: below --
2015-04-27 9:51 Sudeep Holla
2015-04-27 10:26 ` Viresh Kumar
2015-05-15 0:20 ` Rafael J. Wysocki
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=20150331014854.25195.34023@quantum \
--to=mike.turquette@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.com \
--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).