From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-kernel@vger.kernel.org, Liam Girdwood <lrg@ti.com>
Subject: Re: DVS regulator drivers
Date: Tue, 20 Nov 2012 19:38:21 +0900 [thread overview]
Message-ID: <20121120103818.GG10560@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1211201054260.21420@axis700.grange>
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
On Tue, Nov 20, 2012 at 11:02:57AM +0100, Guennadi Liakhovetski wrote:
> On Tue, 20 Nov 2012, Mark Brown wrote:
> > On Mon, Nov 19, 2012 at 12:52:09PM +0100, Guennadi Liakhovetski wrote:
> > > /* Always set the ON status to the minimum voltage */
> > > but I actually don't see, where the minimum is selected. It seems instead
> > > in this case the "ON" value is just set:
This is where I was asking you to clarify what you were trying to say :/
> In other words, I don't see where voltages are compared to select the
> minimum to be used for .on_vsel. Instead, it seems, .on_vsel is always set
> to the new value, and, if it is also higher then the old .dvs_vsel value,
> .dvs_vsel is _also_ set to the new voltage, in which case they become
> equal. Is this the intended behaviour?
There's no need to do any comparison because we only ever get one
selector value, there's nothing to compare it against. We're setting it
to the dvs_vsel since normal practice is to keep the upper end of the
voltage range constant. This isn't going to do much good if they but
anyone who actually has that use can worry about it - it's rare.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-11-20 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 11:52 DVS regulator drivers Guennadi Liakhovetski
2012-11-20 1:05 ` Mark Brown
2012-11-20 8:17 ` Guennadi Liakhovetski
2012-11-20 8:27 ` Mark Brown
2012-11-20 10:02 ` Guennadi Liakhovetski
2012-11-20 10:38 ` Mark Brown [this message]
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=20121120103818.GG10560@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.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