From: Wolfram Sang <w.sang@pengutronix.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] regulator: add driver for MAX8660/8661
Date: Thu, 24 Sep 2009 20:07:27 +0200 [thread overview]
Message-ID: <20090924180727.GA6408@pengutronix.de> (raw)
In-Reply-To: <20090924173904.GA9082@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]
> > + if (MAX8660_DCDC_MIN_UV + selector * MAX8660_DCDC_STEP > max_uV)
> > + return -EINVAL;
>
> Not important but using list_voltage() here would be a little nicer.
Well, uhm, yeah :)
> > +static struct regulator_ops max8660_dcdc_ops = {
> > + .is_enabled = max8660_dcdc_is_enabled,
> > + .list_voltage = max8660_dcdc_list,
> > + .set_voltage = max8660_dcdc_set,
> > + .get_voltage = max8660_dcdc_get,
> > + /* no set_mode() & friends: forced PWM does not save any power */
>
> Forced PWM is normally a power loss - the benefit it gives is the
> ability to respond to sudden spikes in load without voltage droops. The
> power benefit from not having it enabled is usually only apparent at
> lower loads.
Understood. Well, as this chip automatically switches PWM on/off depending on
the load (formula is in the datasheet), it seems to me that the forced-PWM mode
is mainly used for systems which prefer low-noise on the signal. So, the above
comment could just be dropped. Liam, could you do this, or shall I resend?
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-09-24 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 13:24 [PATCH] regulator: add driver for MAX8660/8661 Wolfram Sang
2009-09-24 17:39 ` Mark Brown
2009-09-24 18:07 ` Wolfram Sang [this message]
2009-09-24 18:13 ` Mark Brown
2009-09-24 18:21 ` Liam Girdwood
2009-09-25 7:39 ` [PATCH V2] " Wolfram Sang
2009-09-25 17:23 ` Mark Brown
2009-09-29 16:46 ` Liam Girdwood
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=20090924180727.GA6408@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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