From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Colin Cross <ccross@google.com>
Cc: Paul Walmsley <paul@pwsan.com>, "Hilman, Kevin" <khilman@ti.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
"Cousson, Benoit" <b-cousson@ti.com>,
"tony@atomide.com" <tony@atomide.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Turquette, Mike" <mturquette@ti.com>
Subject: Re: Common clock and dvfs
Date: Thu, 5 May 2011 14:59:02 +0100 [thread overview]
Message-ID: <20110505135901.GA26651@sirena.org.uk> (raw)
In-Reply-To: <BANLkTimfN-1J8LifEzsnJ-GFfp0GXGDm+A@mail.gmail.com>
On Wed, May 04, 2011 at 11:50:52PM -0700, Colin Cross wrote:
> True, that was an oversimplificaiton. I meant the minimum voltage that
> scales with clock frequencies only depends on the clock frequency, not
> the device. Devices do need to be able to specify a higher minimum
> voltage, and the regulator api needs to handle it.
The regulator API already supports this so we're fine there.
next prev parent reply other threads:[~2011-05-05 13:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4DC07F10.6010305@ti.com>
2011-05-05 5:08 ` Common clock and dvfs Cousson, Benoit
2011-05-05 6:11 ` Colin Cross
2011-05-05 6:35 ` Paul Walmsley
2011-05-05 6:50 ` Colin Cross
2011-05-05 13:59 ` Mark Brown [this message]
2011-05-05 21:08 ` Cousson, Benoit
2011-05-05 23:15 ` Colin Cross
2011-05-06 17:36 ` Paul Walmsley
2011-05-06 8:13 ` MyungJoo Ham
2011-05-05 6:25 ` Paul Walmsley
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=20110505135901.GA26651@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=b-cousson@ti.com \
--cc=ccross@google.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mturquette@ti.com \
--cc=myungjoo.ham@samsung.com \
--cc=paul@pwsan.com \
--cc=santosh.shilimkar@ti.com \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox