From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 4/7] cpufreq: add clk-reg cpufreq driver
Date: Tue, 3 Jan 2012 09:06:25 +0000 [thread overview]
Message-ID: <20120103090625.GA2914@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20111226134449.GA4259@richard-laptop>
On Mon, Dec 26, 2011 at 09:44:52PM +0800, Richard Zhao wrote:
> On Mon, Dec 26, 2011 at 11:10:30AM +0000, Mark Brown wrote:
> > The *call* is there in the regulator subsystem, it's just that none of
> > the drivers back it up with an actual implementation yet. Which turns
> > out to be a good thing as cpufreq can't currently understand variable
> > latencies and the governors don't deal well with non-trivial latencies
> > anyway.
> but clk API don't have such calls. and many SoCs only adjust clk frequencies, using
> one single voltage.
That's because it's often not known - especially in the case of PLLs,
data sheets don't tend to specify how long it takes for the PLL to relock
after a requested change. If it's important that the PLL be locked,
there will be a bit to poll (or they'll cause the CPU itself to stall
while the PLL is not locked.)
So, for these kinds of situations, how do you suggest that the clk API
provides this information?
next prev parent reply other threads:[~2012-01-03 9:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 7:09 [PATCH v4 0/7] add a generic cpufreq driver Richard Zhao
2011-12-22 7:09 ` [PATCH v4 1/7] ARM: add cpufreq transiton notifier to adjust loops_per_jiffy for smp Richard Zhao
2011-12-22 7:09 ` [PATCH v4 2/7] arm/imx: cpufreq: remove loops_per_jiffy recalculate " Richard Zhao
2011-12-22 7:09 ` [PATCH v4 3/7] cpufreq: OMAP: " Richard Zhao
2011-12-22 7:09 ` [PATCH v4 4/7] cpufreq: add clk-reg cpufreq driver Richard Zhao
2011-12-23 13:18 ` Mark Brown
2011-12-24 8:55 ` Richard Zhao
2011-12-24 12:24 ` Mark Brown
2011-12-24 13:28 ` Richard Zhao
2011-12-24 13:42 ` Mark Brown
2011-12-24 15:52 ` Richard Zhao
2011-12-26 11:10 ` Mark Brown
2011-12-26 13:44 ` Richard Zhao
2011-12-26 14:22 ` Mark Brown
2011-12-27 1:51 ` Richard Zhao
2011-12-27 10:53 ` Mark Brown
2012-01-03 9:06 ` Russell King - ARM Linux [this message]
2012-01-03 13:25 ` Richard Zhao
2012-01-03 13:47 ` Russell King - ARM Linux
2012-01-03 14:15 ` Richard Zhao
2012-01-03 20:26 ` Mark Brown
2011-12-24 13:10 ` Jamie Iles
2011-12-24 13:24 ` Richard Zhao
2011-12-22 7:09 ` [PATCH v4 5/7] dts/imx6q: add cpufreq property Richard Zhao
2011-12-22 7:09 ` [PATCH v4 6/7] arm/imx6q: register arm_clk as cpu to clkdev Richard Zhao
2011-12-22 7:09 ` [PATCH v4 7/7] arm/imx6q: select ARCH_HAS_CPUFREQ Richard Zhao
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=20120103090625.GA2914@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).