From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: Device tree binding for DVFS table
Date: Thu, 12 Jul 2012 15:23:20 +0000 [thread overview]
Message-ID: <20120712152320.GA7256@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FFE4FE6.20109@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 472 bytes --]
On Thu, Jul 12, 2012 at 09:47:42AM +0530, Prashant Gaikwad wrote:
> On Wednesday 11 July 2012 08:14 PM, Mark Brown wrote:
> >I'd also expect to see a range of voltages for each frequency rather
> >than a specific voltage; usually things are at least characterised with
> >a specified tolerance.
> But then how will you determine the operating voltage for a frequency?
By passing the range into the regulator API - the regulator API always
takes a voltage range anyway.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-07-12 15:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 13:08 Device tree binding for DVFS table 함명주
2012-07-11 13:08 ` Prashant Gaikwad
2012-07-11 14:03 ` Rob Herring
2012-07-11 14:44 ` Mark Brown
2012-07-11 20:04 ` Mike Turquette
2012-07-12 4:26 ` Prashant Gaikwad
2012-07-12 14:10 ` Peter De Schrijver
2012-07-12 17:10 ` Mike Turquette
2012-07-12 17:15 ` Mark Brown
2012-07-13 10:34 ` Peter De Schrijver
2012-07-13 17:25 ` Mike Turquette
2012-07-12 4:29 ` Prashant Gaikwad
2012-07-12 15:23 ` Mark Brown [this message]
2012-07-12 17:01 ` Mike Turquette
2012-07-12 8:19 ` Peter De Schrijver
2012-07-12 4:20 ` Prashant Gaikwad
2012-07-13 18:42 ` Prashant Gaikwad
2012-07-15 21:40 ` Mark Brown
2012-07-15 23:42 ` Rob Herring
2012-07-16 18:36 ` Turquette, Mike
2012-07-17 12:49 ` Prashant Gaikwad
2012-07-17 13:20 ` Mark Brown
2012-07-17 14:34 ` Prashant Gaikwad
2012-07-17 14:37 ` Mark Brown
2012-07-18 12:58 ` Prashant Gaikwad
2012-07-18 21:19 ` Mark Brown
2012-07-18 17:08 ` Shawn Guo
2012-07-11 13:49 ` Peter De Schrijver
2012-07-11 13:49 ` Peter De Schrijver
2012-07-12 4:34 ` Prashant Gaikwad
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=20120712152320.GA7256@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 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).