From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Amit Daniel Kachhap <amit.kachhap@gmail.com>,
Javi Merino <javi.merino@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Eduardo Valentin <edubezval@gmail.com>,
linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH 2/3] thermal: cpu_cooling: Check OPP for errors
Date: Tue, 7 Feb 2017 09:28:15 +0530 [thread overview]
Message-ID: <20170207035815.GK3131@vireshk-i7> (raw)
In-Reply-To: <2237771.GAr8QlFsVi@aspire.rjw.lan>
On 06-02-17, 13:02, Rafael J. Wysocki wrote:
> On Monday, February 06, 2017 03:56:28 PM Viresh Kumar wrote:
> > It is possible for dev_pm_opp_find_freq_exact() to return errors. It was
> > all fine earlier as dev_pm_opp_get_voltage() had a check within it to
> > check for invalid OPPs, but dev_pm_opp_put() doesn't have any similar
> > checks and the callers need to make sure OPP is valid before calling
> > them.
> >
> > Also update the later dev_warn_ratelimited() to not print the error
> > message as the OPP is guaranteed to be valid now.
> >
> > Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> > ---
> > drivers/thermal/cpu_cooling.c | 11 +++++++++--
> > 1 file changed, 9 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/thermal/cpu_cooling.c b/drivers/thermal/cpu_cooling.c
> > index 85fdbf762fa0..9534540434e2 100644
> > --- a/drivers/thermal/cpu_cooling.c
> > +++ b/drivers/thermal/cpu_cooling.c
> > @@ -431,13 +431,20 @@ static int get_static_power(struct cpufreq_cooling_device *cpufreq_device,
> >
> > opp = dev_pm_opp_find_freq_exact(cpufreq_device->cpu_dev, freq_hz,
> > true);
> > + if (IS_ERR(opp)) {
> > + dev_warn_ratelimited(cpufreq_device->cpu_dev,
> > + "Failed to find OPP for frequency %lu: %ld\n",
> > + freq_hz, PTR_ERR(opp));
>
> I'm quite unconvinced about the WARN level of these messages.
>
> They seem to be mostly useful for the people who provide device trees for
> platforms (ie. system integrators). If users see them, there is not much
> they can do to fix the problem by themselves and the hardware is OK,
> actually.
Sure. I just wanted to keep it consistent within the function.
--
viresh
next prev parent reply other threads:[~2017-02-07 3:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 10:26 [PATCH 1/3] thermal: devfreq: Simplify expression Viresh Kumar
2017-02-06 10:26 ` [PATCH 2/3] thermal: cpu_cooling: Check OPP for errors Viresh Kumar
2017-02-06 12:02 ` Rafael J. Wysocki
2017-02-07 3:58 ` Viresh Kumar [this message]
2017-02-06 10:26 ` [PATCH 3/3] thermal: devfreq: " 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=20170207035815.GK3131@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=amit.kachhap@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=edubezval@gmail.com \
--cc=javi.merino@kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=vincent.guittot@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