public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	linux-kernel@vger.kernel.org, Mark Brown <broonie@linaro.org>
Subject: Re: [PATCH] regulator: gpio: Don't require a regulator-type property
Date: Thu, 05 Dec 2013 01:44:42 +0100	[thread overview]
Message-ID: <1766701.HGqKkTj0sM@avalon> (raw)
In-Reply-To: <1386203515-6815-1-git-send-email-broonie@kernel.org>

Hi Mark,

Thanks for the patch.

On Thursday 05 December 2013 00:31:55 Mark Brown wrote:
> From: Mark Brown <broonie@linaro.org>
> 
> Since essentially all GPIO controlled regulators are voltage regulators
> make the regulator-type property optional, defaulting to voltage.
> 
> Signed-off-by: Mark Brown <broonie@linaro.org>
> ---
> 
> Compile tested only.
> 
>  drivers/regulator/gpio-regulator.c | 14 ++++++--------
>  1 file changed, 6 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/regulator/gpio-regulator.c
> b/drivers/regulator/gpio-regulator.c index 234960dc9607..13ec94d984ca
> 100644
> --- a/drivers/regulator/gpio-regulator.c
> +++ b/drivers/regulator/gpio-regulator.c
> @@ -203,17 +203,15 @@ of_get_gpio_regulator_config(struct device *dev,
> struct device_node *np) }
>  	config->nr_states = i;
> 
> +	config->type = REGULATOR_VOLTAGE;
>  	ret = of_property_read_string(np, "regulator-type", &regtype);
> -	if (ret < 0) {
> -		dev_err(dev, "Missing 'regulator-type' property\n");
> -		return ERR_PTR(-EINVAL);
> +	if (ret >= 0) {
> +		if (!strncmp("voltage", regtype, 7))
> +			config->type = REGULATOR_VOLTAGE;
> +		else if (!strncmp("current", regtype, 7))
> +			config->type = REGULATOR_CURRENT;

Should we warn or error in case of an unsupported value ?

>  	}
> 
> -	if (!strncmp("voltage", regtype, 7))
> -		config->type = REGULATOR_VOLTAGE;
> -	else if (!strncmp("current", regtype, 7))
> -		config->type = REGULATOR_CURRENT;
> -
>  	return config;
>  }
-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2013-12-05  0:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05  0:31 [PATCH] regulator: gpio: Don't require a regulator-type property Mark Brown
2013-12-05  0:44 ` Laurent Pinchart [this message]
2013-12-05 11:35   ` Mark Brown

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=1766701.HGqKkTj0sM@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=broonie@kernel.org \
    --cc=broonie@linaro.org \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=lgirdwood@gmail.com \
    --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