From: Yi Zhang <zhangyi.hust@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: gpio-regulator: Set the smallest voltage/current in the specified range
Date: Fri, 1 Jun 2012 08:45:33 +0000 (UTC) [thread overview]
Message-ID: <loom.20120601T103409-573@post.gmane.org> (raw)
In-Reply-To: 20120322115009.GG3091@opensource.wolfsonmicro.com
Mark Brown <broonie <at> opensource.wolfsonmicro.com> writes:
>
> On Thu, Mar 22, 2012 at 02:08:04PM +0800, Axel Lin wrote:
> > 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.
>
> Applied, thanks.
>
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)
Here seems something wrong, for best_val is always INT_MAX. From the discussion
above, maybe best_val is should be reassigned in the for loop.
It may be like as the following:
- for (ptr = 0; ptr < data->nr_states; ptr++)
+ for (ptr = 0; ptr < data->nr_states; ptr++) {
if (data->states[ptr].value < best_val &&
data->states[ptr].value >= min &&
- data->states[ptr].value <= max)
+ data->states[ptr].value <= max) {
target = data->states[ptr].gpios;
+ best_val = target;
+ }
What do you think? thanks;
prev parent reply other threads:[~2012-06-01 8:55 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
2012-03-22 11:50 ` Mark Brown
2012-06-01 8:45 ` Yi Zhang [this message]
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=loom.20120601T103409-573@post.gmane.org \
--to=zhangyi.hust@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