From: Paul Walmsley <paul@pwsan.com>
To: r-woodruff2@ti.com
Cc: "Kim Kyuwon" <chammoru@gmail.com>,
"Kevin Hilman" <khilman@deeprootsystems.com>,
OMAP <linux-omap@vger.kernel.org>,
"Nayak, Rajendra" <rnayak@ti.com>,
박경민 <kyungmin.park@samsung.com>, 민병호 <bhmin@samsung.com>,
"Tony Lindgren" <tony@atomide.com>
Subject: Re: PM: 4 Problems in OMAP3430 DVFS (SmartReflex, Cpufreq)
Date: Thu, 23 Apr 2009 02:52:51 -0600 (MDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0904230245440.6400@utopia.booyaka.com> (raw)
In-Reply-To: <4d34a0a70904222200oc699378k56367cf3b378b5d9@mail.gmail.com>
Hello Richard,
On Thu, 23 Apr 2009, Kim Kyuwon wrote:
> 4. Current PM code didn't enable the maximum clock (i.e. CPU: 600Mhz)
> according to the comment as below:
>
> /* Avoid registering the 120% Overdrive with CPUFreq */
> prcm = mpu_opps + MAX_VDD1_OPP - 1;
>
> But in some cases, we should use 600Mhz for multimedia application.
> And, even thought we enable the maximum clock, CPU frequency seldom
> goes into maximum clock. I think we don't have to avoid registering
> the max OPP.
Do you know if this restriction can be lifted now, i.e., can the silicon
run at VDD1 OPP1 100% of the time and meet the device lifespan targets?
- Paul
next prev parent reply other threads:[~2009-04-23 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 5:00 PM: 4 Problems in OMAP3430 DVFS (SmartReflex, Cpufreq) Kim Kyuwon
2009-04-23 8:52 ` Paul Walmsley [this message]
2009-04-23 15:39 ` Woodruff, Richard
2009-05-07 7:42 ` Kim Kyuwon
2009-04-23 23:27 ` Woodruff, Richard
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=alpine.DEB.2.00.0904230245440.6400@utopia.booyaka.com \
--to=paul@pwsan.com \
--cc=bhmin@samsung.com \
--cc=chammoru@gmail.com \
--cc=khilman@deeprootsystems.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-omap@vger.kernel.org \
--cc=r-woodruff2@ti.com \
--cc=rnayak@ti.com \
--cc=tony@atomide.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.