All of lore.kernel.org
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Vishwanath Sripathy <vishwanath.bs@ti.com>, linux-omap@vger.kernel.org
Cc: Kevin Hilman <khilman@ti.com>
Subject: RE: [PATCH 2/3] omap: cpufreq: Split omap1 and omap2plus cpufreq drivers.
Date: Fri, 25 Feb 2011 12:52:36 +0530	[thread overview]
Message-ID: <249b719993fd0ebc4f09de6c21d5750f@mail.gmail.com> (raw)
In-Reply-To: <a5de4c2875426c022dd85547c8aff31b@mail.gmail.com>

> -----Original Message-----
> From: Vishwanath Sripathy [mailto:vishwanath.bs@ti.com]
> Sent: Friday, February 25, 2011 12:47 PM
> To: Santosh Shilimkar; linux-omap@vger.kernel.org
> Cc: Kevin Hilman
> Subject: RE: [PATCH 2/3] omap: cpufreq: Split omap1 and omap2plus
> cpufreq drivers.
>
[....]

> > @@ -101,33 +84,44 @@ static int omap_target(struct cpufreq_policy
> > *policy,
> >  	if (target_freq > policy->max)
> >  		target_freq = policy->max;
> >
> > -#ifdef CONFIG_ARCH_OMAP1
> >  	freqs.old = omap_getspeed(0);
> >  	freqs.new = clk_round_rate(mpu_clk, target_freq * 1000) /
> 1000;
> >  	freqs.cpu = 0;
> >
> >  	if (freqs.old == freqs.new)
> >  		return ret;
> > +
> >  	cpufreq_notify_transition(&freqs, CPUFREQ_PRECHANGE);
> > +
> >  #ifdef CONFIG_CPU_FREQ_DEBUG
> > -	printk(KERN_DEBUG "cpufreq-omap: transition: %u --> %u\n",
> > -	       freqs.old, freqs.new);
> > +	pr_info("cpufreq-omap: transition: %u --> %u\n", freqs.old,
> > freqs.new);
> >  #endif
> > +
> >  	ret = clk_set_rate(mpu_clk, freqs.new * 1000);
> > +	if (ret)
> > +		return ret;
> Do you want to return here w/o calling post notifiers and
> readjusting the
> jiffies? Cpufreq updates lpj as part of PRECHANGE notifier when
> frequency
> is scaled up. So in that case returning here will end of having
> wrong lpj I suppose.
You are right. A notifier with old freq is needed here.

Regards,
Santosh

  reply	other threads:[~2011-02-25  7:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25  6:10 [PATCH 0/3] [pm-wip/cpufreq] cpufreq cleanup and SMP support Santosh Shilimkar
2011-02-25  6:10 ` [PATCH 1/3] omap2plus: clock: Add an alias cpu_ck to be used in common cpufreq driver Santosh Shilimkar
2011-03-10 22:13   ` Kevin Hilman
2011-03-14  9:19     ` Santosh Shilimkar
2011-02-25  6:10 ` [PATCH 2/3] omap: cpufreq: Split omap1 and omap2plus cpufreq drivers Santosh Shilimkar
2011-02-25  7:17   ` Vishwanath Sripathy
2011-02-25  7:22     ` Santosh Shilimkar [this message]
2011-02-25  8:19   ` DebBarma, Tarun Kanti
2011-02-25  6:10 ` [PATCH 3/3] omap2plus: cpufreq: Add SMP support to cater OMAP4430 Santosh Shilimkar
2011-02-25  8:10   ` DebBarma, Tarun Kanti
2011-03-10 22:27   ` Kevin Hilman
2011-03-10 22:28 ` [PATCH 0/3] [pm-wip/cpufreq] cpufreq cleanup and SMP support Kevin Hilman
2011-03-11  5:54   ` Santosh Shilimkar

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=249b719993fd0ebc4f09de6c21d5750f@mail.gmail.com \
    --to=santosh.shilimkar@ti.com \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=vishwanath.bs@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.