From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Wolfram Sang <w.sang@pengutronix.de>
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 10:39:05 -0700 [thread overview]
Message-ID: <20090924173904.GA9082@sirena.org.uk> (raw)
In-Reply-To: <1253798645-9493-1-git-send-email-w.sang@pengutronix.de>
On Thu, Sep 24, 2009 at 03:24:05PM +0200, Wolfram Sang wrote:
> Tested with a MX25-based custom board.
> Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
This looks good - thanks! A couple of little comments below:
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> + 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.
> +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.
next prev parent reply other threads:[~2009-09-24 17:39 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 [this message]
2009-09-24 18:07 ` Wolfram Sang
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=20090924173904.GA9082@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=w.sang@pengutronix.de \
/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.