public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lg@opensource.wolfsonmicro.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.arm.linux.org.uk,
	broonie@opensource.wolfsonmicro.com
Subject: Re: [PATCH 0/13] Updated V4  - Regulator Framework
Date: Sat, 03 May 2008 11:31:32 +0100	[thread overview]
Message-ID: <1209810693.12502.97.camel@odin> (raw)
In-Reply-To: <20080502165248.dba934e9.akpm@linux-foundation.org>

On Fri, 2008-05-02 at 16:52 -0700, Andrew Morton wrote:
> On Fri, 02 May 2008 16:40:41 +0100
> Liam Girdwood <lg@opensource.wolfsonmicro.com> wrote:
> 
> > This is an updated version of the kernel voltage & current regulator
> > framework based on comments received from version 3 of the patch series.
> > 
> > The regulator framework is designed to provide a standard kernel
> > interface to control voltage and current regulators on SoC based
> > systems.
> > 
> > The intention is to allow systems to dynamically control regulator power
> > output in order to save power and prolong battery life. This applies to
> > both voltage regulators (where voltage output is controllable) and
> > current sinks (where current limit is controllable).
> > 
> 
> oh gee.
> 
> I (and others) reviewed and commented on all this code last month.  Now
> here it is again and, although I'm sure it is delightful code, nobody wants
> to have to read it all again ;)
> 
> The one-month gap between v3 and v4 is unfortunate.  It means that everyone
> has forgotten everything.
> 

Sorry about this. It really couldn't be helped as I've been on the road
a lot lately. I was even in the audience for your talk at CELF ;)

> 
> Was all the review feedback satisfactorily handled to the reviewers'
> satisfaction?
> 

Summary of changes re V3 comments :-

 o Added lots of documentation.
 o Added ABI documentation.
 o Changed debug option Kconfig style.
 o Regulator no longer a class device.
 o sysfs naming changes, ie. now uses microvolts and microamps.
 o sysfs entries only export one value.
 o get_current() macro undef removed.
 o set_voltage(), set_current_limit() now take a lower and upper
acceptable value.
 o Fixed a locking issue.
 o Made 'compiled out' interface all static inline instead of macros.
 o Removed dynamic voltage control where the voltage would be
dynamically managed to be the lowest for all consumers (no known users
of this code atm - although spoke with someone at CELF who was
interested in this feature for the future).
 o Checkpatch fixes.
 o Removed comments describing some functions from the headers - now all
such comments are in the c files.

> Is there any new material in here which would require a re-review?

Yes. Other additions :-

 o Test harness added to aid developers with testing regulator drivers
(virtual.c - patch 07/13).
 o Support for fixed output regulators. i.e. regulators that cannot be
controlled by software but coexist on systems with software controllable
regulators (fixed.h, fixed.c - patches 04/13 and 06/13)
 o Bulk operations for consumers that may have multiple regulator
supplies (consumer.h, core.c - patches 01/13 and 05/13)
 o Changed core file and header names to be more meaningful. i.e
reg-core.c -> core.c, regulator/regulator.h -> regulator/consumer.h,
etc.

Lastly, I've forgotten the MAINTAINERS patch but this can be added
later.

Liam


  reply	other threads:[~2008-05-03 10:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 15:40 [PATCH 0/13] Updated V4 - Regulator Framework Liam Girdwood
2008-05-02 23:52 ` Andrew Morton
2008-05-03 10:31   ` Liam Girdwood [this message]
2008-05-08  6:35 ` Harald Welte
2008-05-08 20:16   ` Mark Brown
2008-05-08 20:51   ` Liam Girdwood
2008-05-09  4:37     ` Harald Welte
2008-05-09 19:44       ` Liam Girdwood
2008-05-11 14:39         ` Liam Girdwood
2008-07-10  9:08 ` Andrew Morton
2008-07-29 20:33   ` Liam Girdwood
2008-07-29 20:40     ` Andrew Morton

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=1209810693.12502.97.camel@odin \
    --to=lg@opensource.wolfsonmicro.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@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