From: Prashant Gaikwad <pgaikwad@nvidia.com>
To: Mike Turquette <mturquette@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
"rnayak@ti.com" <rnayak@ti.com>,
"paul@pwsan.com" <paul@pwsan.com>,
"broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"ccross@android.com" <ccross@android.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/2] [RFC] cpufreq: omap: scale regulator from clk notifier
Date: Tue, 17 Jul 2012 10:50:56 +0530 [thread overview]
Message-ID: <5004F638.6020301@nvidia.com> (raw)
In-Reply-To: <1342225001-22962-3-git-send-email-mturquette@linaro.org>
On Saturday 14 July 2012 05:46 AM, Mike Turquette wrote:
> This patch moves direct control of the MPU voltage regulator out of the
> cpufreq driver .target callback and instead puts that logic into a clock
> rate change notifier callback.
>
> The same frequency/voltage lookup via the OPP library is present, except
> that the calls to regulator_set_voltage are done from the clock
> framework instead of cpufreq.
>
> Ideally it would be nice to reduce the .target callback for OMAP's
> cpufreq driver to a simple call to clk_set_rate. For now there is still
> some other stuff needed there (jiffies per loop, rounding the rate, etc
> etc).
>
> Not-signed-off-by: Mike Turquette<mturquette@linaro.org>
> ---
> drivers/cpufreq/omap-cpufreq.c | 154 +++++++++++++++++++++++++---------------
> 1 file changed, 96 insertions(+), 58 deletions(-)
>
<snip>
>
> -static int __init omap_cpufreq_init(void)
> +static int mpu_clk_volt_scale_handler(struct notifier_block *nb,
> + unsigned long flags, void *data)
> {
> - if (cpu_is_omap24xx())
> - mpu_clk_name = "virt_prcm_set";
> - else if (cpu_is_omap34xx())
> - mpu_clk_name = "dpll1_ck";
> - else if (cpu_is_omap44xx())
> - mpu_clk_name = "dpll_mpu_ck";
> + struct clk_notifier_data *cnd = data;
> + unsigned long tol;
> + int ret, volt_new, volt_old;
> + struct opp *opp;
>
> - if (!mpu_clk_name) {
> - pr_err("%s: unsupported Silicon?\n", __func__);
> - return -EINVAL;
> + volt_old = regulator_get_voltage(mpu_reg);
> + opp = opp_find_freq_exact(mpu_dev, cnd->new_rate, true);
> + volt_new = opp_get_voltage(opp);
> +
> + tol = volt_new * OPP_TOLERANCE / 100;
> +
> + /* scaling up? scale voltage before frequency */
> + if (cnd->new_rate> cnd->old_rate) {
> + dev_dbg(mpu_dev, "cpufreq-omap: %d mV --> %d mV\n",
> + volt_old, volt_new);
> +
> + ret = regulator_set_voltage(mpu_reg, volt_new - tol, volt_new + tol);
> +
> + if (ret< 0) {
> + dev_warn(mpu_dev, "%s: unable to scale voltage up.\n",
> + __func__);
> + return NOTIFY_BAD;
> + }
> + }
> +
> + /* scaling down? scale voltage after frequency */
> + if (cnd->new_rate< cnd->old_rate) {
> + dev_dbg(mpu_dev, "cpufreq-omap: %d mV --> %d mV\n",
> + volt_old, volt_new);
> +
> + ret = regulator_set_voltage(mpu_reg, volt_new - tol, volt_new + tol);
> +
> + if (ret< 0) {
> + dev_warn(mpu_dev, "%s: unable to scale voltage down.\n",
> + __func__);
> + return NOTIFY_BAD;
> + }
> }
How are you checking pre and post rate change condition here? Need
switch case for event?
>
> + return NOTIFY_OK;
> +}
> +
> +static struct notifier_block mpu_clk_volt_scale_nb = {
> + .notifier_call = mpu_clk_volt_scale_handler,
> +};
> +
> +
next prev parent reply other threads:[~2012-07-17 5:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-14 0:16 [PATCH 0/2] [RFC] reentrancy in the common clk framework Mike Turquette
2012-07-14 0:16 ` [PATCH 1/2] [RFC] clk: reentrancy via per-clock locking Mike Turquette
2012-07-14 0:16 ` [PATCH 2/2] [RFC] cpufreq: omap: scale regulator from clk notifier Mike Turquette
2012-07-16 22:28 ` Linus Walleij
2012-07-16 23:22 ` Turquette, Mike
2012-07-20 13:26 ` Sekhar Nori
2012-07-17 5:20 ` Prashant Gaikwad [this message]
2012-07-17 15:42 ` Mike Turquette
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=5004F638.6020301@nvidia.com \
--to=pgaikwad@nvidia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=ccross@android.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=paul@pwsan.com \
--cc=pdeschrijver@nvidia.com \
--cc=rnayak@ti.com \
--cc=rob.herring@calxeda.com \
--cc=shawn.guo@linaro.org \
--cc=tglx@linutronix.de \
--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).