From: Tushar Behera <tushar.behera@linaro.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org, philipspatches@gmail.com,
patches@linaro.org
Subject: Re: [PATCH] regulator: core: Update regulator_is_supported_voltage for fixed voltages
Date: Mon, 12 Nov 2012 10:13:55 +0530 [thread overview]
Message-ID: <50A07E8B.20902@linaro.org> (raw)
In-Reply-To: <20121109170918.GW23807@opensource.wolfsonmicro.com>
On 11/09/2012 10:39 PM, Mark Brown wrote:
> On Fri, Nov 09, 2012 at 04:21:49PM +0530, Tushar Behera wrote:
>
>> In case of fixed regulators for which voltage cannot be changed,
>> regulator_is_supported_voltage should return success only if the
>> min_uV and max_uV parameters are same and it is equal to the current
>> voltage of the regulator.
>
> This makes no sense to me at all. The caller is asking if it's possible
> to set the voltage between the minimum and maximum values, any voltage
> in that range should be OK. Your patch makes the function massively
> less useful.
>
Ok.
In that case, we should modify the test condition as following.
Currently it passes success when the regulator voltage is less than both
min_uV and max_uV. If ok, I will send another patch for this.
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index 1a35251..e90e5c3 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -1974,7 +1974,7 @@ int regulator_is_supported_voltage(struct
regulator *regulator,
if (!(rdev->constraints->valid_ops_mask &
REGULATOR_CHANGE_VOLTAGE)) {
ret = regulator_get_voltage(regulator);
if (ret >= 0)
- return (min_uV >= ret && ret <= max_uV);
+ return (ret >= min_uV && ret <= max_uV);
else
return ret;
}
--
Tushar Behera
next prev parent reply other threads:[~2012-11-12 4:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 10:51 [PATCH] regulator: core: Update regulator_is_supported_voltage for fixed voltages Tushar Behera
2012-11-09 17:09 ` Mark Brown
2012-11-12 4:43 ` Tushar Behera [this message]
2012-11-13 6:48 ` 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=50A07E8B.20902@linaro.org \
--to=tushar.behera@linaro.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.org \
--cc=philipspatches@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 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.