From: Viresh Kumar <viresh.kumar@linaro.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
b.zolnierkie@samsung.com, nm@ti.com, sboyd@codeaurora.org,
Tomasz Figa <tomasz.figa@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Javier Martinez Canillas <javier@dowhile0.org>,
Thomas Abraham <thomas.ab@samsung.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Len Brown <len.brown@intel.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] opp: add dev_pm_opp_is_turbo() helper
Date: Wed, 29 Jul 2015 15:54:35 +0530 [thread overview]
Message-ID: <20150729102435.GB9584@linux> (raw)
In-Reply-To: <20150728142713.GB17745@amd>
On 28-07-15, 16:27, Pavel Machek wrote:
> Typo.
>
> And this is not exactly most helpful comment. opp is turbo... returns
> if opp was turbo. Explanation what "turbo" means in this context would
> be nice. I'm pretty sure it is not about air compression :-).
Does this make it any better:
diff --git a/drivers/base/power/opp.c b/drivers/base/power/opp.c
index e039cf024a6c..da8ec7f824d5 100644
--- a/drivers/base/power/opp.c
+++ b/drivers/base/power/opp.c
@@ -281,9 +281,13 @@ unsigned long dev_pm_opp_get_freq(struct dev_pm_opp *opp)
EXPORT_SYMBOL_GPL(dev_pm_opp_get_freq);
/**
- * dev_pm_opp_is_turbo() - Returns true if opp was trubo OPP
+ * dev_pm_opp_is_turbo() - Returns if opp is turbo OPP or not
* @opp: opp for which turbo mode is being verified
*
+ * Turbo OPPs are not for normal use, and can be enabled (under certain
+ * conditions) for short duration of times to finish high throughput work
+ * quickly. Running on them for longer times may overheat the chip.
+ *
* Return: true if opp is turbo opp, else false.
*
* Locking: This function must be called under rcu_read_lock(). opp is a rcu
--
viresh
next prev parent reply other threads:[~2015-07-29 10:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 11:19 [PATCH 0/4] cpufreq/opp: Turbo/boost mode support Viresh Kumar
2015-07-28 11:20 ` [PATCH 1/4] opp: add dev_pm_opp_is_turbo() helper Viresh Kumar
2015-07-28 14:27 ` Pavel Machek
2015-07-29 10:24 ` Viresh Kumar [this message]
2015-07-29 10:53 ` Pavel Machek
2015-07-29 10:56 ` Viresh Kumar
2015-07-28 11:20 ` [PATCH 2/4] cpufreq: Update boost flag while initializing freq table from OPPs Viresh Kumar
2015-07-28 11:20 ` [PATCH 3/4] cpufreq: Allow drivers to enable boost support after registering driver Viresh Kumar
2015-07-28 13:48 ` Viresh Kumar
2015-07-28 11:20 ` [PATCH 4/4] cpufreq: dt: Add support for turbo/boost mode Viresh Kumar
2015-07-28 11:22 ` [PATCH 0/4] cpufreq/opp: Turbo/boost mode support Viresh Kumar
2015-07-28 11:55 ` Bartlomiej Zolnierkiewicz
2015-07-28 12:18 ` Viresh Kumar
2015-07-28 13:38 ` Bartlomiej Zolnierkiewicz
2015-07-28 13:47 ` 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=20150729102435.GB9584@linux \
--to=viresh.kumar@linaro.org \
--cc=b.zolnierkie@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=javier@dowhile0.org \
--cc=len.brown@intel.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nm@ti.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.org \
--cc=thomas.ab@samsung.com \
--cc=tomasz.figa@gmail.com \
/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).