From: "Heiko Stübner" <heiko@sntech.de>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org, Liam Girdwood <lrg@ti.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] regulator: gpio-regulator: Set the smallest voltage/current in the specified range
Date: Thu, 22 Mar 2012 10:08:58 +0100 [thread overview]
Message-ID: <201203221009.05902.heiko@sntech.de> (raw)
In-Reply-To: <1332396484.3842.2.camel@phoenix>
Am Donnerstag, 22. März 2012, 07:08:04 schrieb Axel Lin:
> Do not assume the gpio regulator states map is sorted in any order.
> This patch ensures we always set the smallest voltage/current that falls
> within the specified range.
>
> Signed-off-by: Axel Lin <axel.lin@gmail.com>
nice addition, thanks
Acked-by: Heiko Stuebner <heiko@sntech.de>
> ---
> drivers/regulator/gpio-regulator.c | 8 ++++----
> 1 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/regulator/gpio-regulator.c
> b/drivers/regulator/gpio-regulator.c index 42e1cb1..b728b36 100644
> --- a/drivers/regulator/gpio-regulator.c
> +++ b/drivers/regulator/gpio-regulator.c
> @@ -105,15 +105,15 @@ static int gpio_regulator_set_value(struct
> regulator_dev *dev, int min, int max)
> {
> struct gpio_regulator_data *data = rdev_get_drvdata(dev);
> - int ptr, target, state;
> + int ptr, target, state, best_val = INT_MAX;
>
> - target = -1;
> for (ptr = 0; ptr < data->nr_states; ptr++)
> - if (data->states[ptr].value >= min &&
> + if (data->states[ptr].value < best_val &&
> + data->states[ptr].value >= min &&
> data->states[ptr].value <= max)
> target = data->states[ptr].gpios;
>
> - if (target < 0)
> + if (best_val == INT_MAX)
> return -EINVAL;
>
> for (ptr = 0; ptr < data->nr_gpios; ptr++) {
next prev parent reply other threads:[~2012-03-22 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 6:08 [PATCH] regulator: gpio-regulator: Set the smallest voltage/current in the specified range Axel Lin
2012-03-22 9:08 ` Heiko Stübner [this message]
2012-03-22 11:50 ` Mark Brown
2012-06-01 8:45 ` Yi Zhang
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=201203221009.05902.heiko@sntech.de \
--to=heiko@sntech.de \
--cc=axel.lin@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.