From: ccross@google.com (Colin Cross)
To: linux-arm-kernel@lists.infradead.org
Subject: Common clock and dvfs
Date: Wed, 4 May 2011 23:50:52 -0700 [thread overview]
Message-ID: <BANLkTimfN-1J8LifEzsnJ-GFfp0GXGDm+A@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1105050026420.30136@utopia.booyaka.com>
On Wed, May 4, 2011 at 11:35 PM, Paul Walmsley <paul@pwsan.com> wrote:
> On Wed, 4 May 2011, Colin Cross wrote:
>
>> Imagine a chip where a clock can feed devices A, B, and C. ?If the
>> devices are always clocked at the same rate, and can't gate their
>> clocks, the minimum voltage that can be applied to a rail is
>> determined ONLY by the rate of the clock.
>
> That's not so -- although admittedly it's a side issue, and not
> particularly related to DVFS.
>
> For example, the device may have some external I/O lines which need to be
> at least some minimum voltage level for the externally-connected device to
> function. ?This minimum voltage level can be unrelated to the device's
> clock frequency.
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.
next prev parent reply other threads:[~2011-05-05 6:50 UTC|newest]
Thread overview: 22+ 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 [this message]
2011-05-05 13:59 ` Mark Brown
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
2011-04-22 18:15 Colin Cross
2011-04-22 19:37 ` Thomas Gleixner
2011-04-23 1:21 ` Saravana Kannan
2011-04-23 1:35 ` Saravana Kannan
2011-04-23 13:14 ` Thomas Gleixner
2011-04-22 19:40 ` Mark Brown
2011-04-22 19:48 ` Colin Cross
2011-04-22 20:35 ` Mark Brown
2011-04-22 21:18 ` Colin Cross
2011-04-25 11:03 ` Mark Brown
2011-04-25 8:33 ` Paul Walmsley
2011-04-25 18:26 ` Turquette, Mike
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=BANLkTimfN-1J8LifEzsnJ-GFfp0GXGDm+A@mail.gmail.com \
--to=ccross@google.com \
--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).