From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: Common clock and dvfs
Date: Mon, 25 Apr 2011 12:03:03 +0100 [thread overview]
Message-ID: <20110425110303.GB30859@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <BANLkTikhAiujU=Fmpvp-hWAeoTBNXZoEEA@mail.gmail.com>
On Fri, Apr 22, 2011 at 02:18:06PM -0700, Colin Cross wrote:
> I see. Do you happen to know if there are any max voltage
> requirements for clocks? Would running one clock in a group at a low
> operating point and another at a high operating point cause a problem,
> assuming the voltage is set to what is required by the high operating
> point?
I'm not aware of any such requirements, and my understanding of the
electrical engineering issues suggests that they'd be unlikely.
next prev parent reply other threads:[~2011-04-25 11:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 18:15 Common clock and dvfs 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 [this message]
2011-04-25 8:33 ` Paul Walmsley
2011-04-25 18:26 ` Turquette, Mike
[not found] <4DC07F10.6010305@ti.com>
2011-05-05 5:08 ` Cousson, Benoit
2011-05-05 5:08 ` Cousson, Benoit
2011-05-05 6:11 ` Colin Cross
2011-05-05 6:11 ` Colin Cross
2011-05-05 6:35 ` Paul Walmsley
2011-05-05 6:35 ` Paul Walmsley
2011-05-05 6:50 ` Colin Cross
2011-05-05 6:50 ` Colin Cross
2011-05-05 13:59 ` Mark Brown
2011-05-05 13:59 ` Mark Brown
2011-05-05 21:08 ` Cousson, Benoit
2011-05-05 21:08 ` Cousson, Benoit
2011-05-05 23:15 ` Colin Cross
2011-05-05 23:15 ` Colin Cross
2011-05-06 17:36 ` Paul Walmsley
2011-05-06 17:36 ` Paul Walmsley
2011-05-06 8:13 ` MyungJoo Ham
2011-05-06 8:13 ` MyungJoo Ham
2011-05-05 6:25 ` Paul Walmsley
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=20110425110303.GB30859@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.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 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.