X86 platform drivers
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: "R, Durgadoss" <durgadoss.r@intel.com>,
	lm-sensors@lm-sensors.org, Alan Cox <alan@linux.intel.com>,
	platform-driver-x86@vger.kernel.org
Subject: Re: [lm-sensors] A new Subsystem for Current Management
Date: Wed, 9 Nov 2011 12:09:20 +0000	[thread overview]
Message-ID: <20111109120919.GB31441@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20111108175749.2ef50f93@endymion.delvare>

On Tue, Nov 08, 2011 at 05:57:49PM +0100, Jean Delvare wrote:
> On Tue, 8 Nov 2011 16:54:26 +0000, Mark Brown wrote:

> > Actually the regulator API isn't really about power savings - it's about
> > voltage and current regulation.  Higher layers can use these features to
> > save power but it's not somethnig the regulator API cares about.  If the
> > documentation suggests it is we might want to fix that up.

> I came up to this conclusion after reading the CONFIG_REGULATOR help
> text in Kconfig. I'll let you decide if this should get improved in any
> way.

I think the current text is OK, it's saying that it allows other
subsystems do things which save power which is what's happening.

  reply	other threads:[~2011-11-09 12:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-05  7:13 A new Subsystem for Current Management R, Durgadoss
2011-11-05 13:42 ` Bill Gatliff
2011-11-05 16:36   ` [lm-sensors] " R, Durgadoss
2011-11-06 13:13     ` Jean Delvare
2011-11-08 16:54       ` Mark Brown
2011-11-08 16:57         ` Jean Delvare
2011-11-09 12:09           ` Mark Brown [this message]
2011-11-05 15:50 ` Guenter Roeck
2011-11-05 16:50   ` R, Durgadoss
2011-11-06 13:53     ` [lm-sensors] " Jean Delvare
2011-11-06 13:05 ` Jean Delvare

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=20111109120919.GB31441@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alan@linux.intel.com \
    --cc=durgadoss.r@intel.com \
    --cc=khali@linux-fr.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=platform-driver-x86@vger.kernel.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