mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Roger Quadros <quadros.roger@gmail.com>
Cc: lrg@slimlogic.co.uk, philipp.zabel@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] regulator: Add GPIO enable control to fixed voltage regulator driver
Date: Tue, 4 Aug 2009 21:40:54 +0100	[thread overview]
Message-ID: <20090804204053.GA29518@sirena.org.uk> (raw)
In-Reply-To: <1249408730-15430-1-git-send-email-quadros.roger@gmail.com>

On Tue, Aug 04, 2009 at 08:58:50PM +0300, Roger Quadros wrote:
> From: Roger Quadros <ext-roger.quadros@nokia.com>

> Now fixed regulators that have their enable pin connected to a GPIO line
> can use the fixed regulator driver for regulator enable/disable control.
> The GPIO number and polarity information is passed through platform data.
> GPIO enable control is achieved using gpiolib.

> Signed-off-by: Roger Quadros <ext-roger.quadros@nokia.com>

Looks good, thanks for taking the time to do this and fixing up the
review comments.

Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>

A couple of small notes that I don't see as blocking merge:

> +
> +		/* FIXME: Remove below print warning
> +		 *
> +		 * config->gpio must be set to -EINVAL by platform code if
> +		 * GPIO control is not required. However, early adopters
> +		 * not requiring GPIO control may forget to initialize
> +		 * config->gpio to -EINVAL. This will cause GPIO 0 to be used
> +		 * for GPIO control.
> +		 *
> +		 * This warning will be removed once there are a couple of users
> +		 * for this driver.

Probably just for 2.6.33 or something; the point here is that this is an
incompatible change in the platform data which we can get away with here
due to the fact that there aren't any current users.

> +		drvdata->is_enabled = config->enabled_at_boot;
> +		ret = drvdata->is_enabled ?
> +				config->enable_high : !config->enable_high;

Might be more legible without the ternery operator but no point spinning
the patch for that.

  reply	other threads:[~2009-08-04 20:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-04 17:58 Roger Quadros
2009-08-04 20:40 ` Mark Brown [this message]
2009-08-05  8:25   ` Roger Quadros

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=20090804204053.GA29518@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=philipp.zabel@gmail.com \
    --cc=quadros.roger@gmail.com \
    /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®