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 11:13:59 -0700 [thread overview]
Message-ID: <20090924181357.GB9082@sirena.org.uk> (raw)
In-Reply-To: <20090924180727.GA6408@pengutronix.de>
On Thu, Sep 24, 2009 at 08:07:27PM +0200, Wolfram Sang wrote:
> > 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?
I don't think I've ever seen a regulator that didn't try to scale up so
that under high load they end up as running in forced PWM mode.
The ability to force is there mainly in case the load transients are so
sudden in a systemm that the pulse skipping ends up not responding
quickly enough. There's also a marginal power saving from not doing the
checks if the load is always high but that's not the common case for the
uses we tend to see in Linux.
next prev parent reply other threads:[~2009-09-24 18:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 13:24 Wolfram Sang
2009-09-24 17:39 ` Mark Brown
2009-09-24 18:07 ` Wolfram Sang
2009-09-24 18:13 ` Mark Brown [this message]
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=20090924181357.GB9082@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®