From: Taras Kondratiuk <taras@ti.com>
To: <lgirdwood@gmail.com>, <broonie@kernel.org>, <rjw@sisk.pl>,
<viresh.kumar@linaro.org>, <shawn.guo@linaro.org>
Cc: <cpufreq@vger.kernel.org>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Taras Kondratiuk <taras@ti.com>,
Philip Rakity <prakity@nvidia.com>,
Eric Miao <eric.y.miao@gmail.com>
Subject: [RFC PATCH 1/2] regulator: core: Add regulator_set_voltage_min()
Date: Fri, 19 Apr 2013 14:55:53 +0300 [thread overview]
Message-ID: <1366372554-20866-2-git-send-email-taras@ti.com> (raw)
In-Reply-To: <1366372554-20866-1-git-send-email-taras@ti.com>
Sometimes it is a need to constrain only a minimum voltage
and let system constraints to limit maximum.
Add a new function regulator_set_voltage_min() for this.
Signed-off-by: Taras Kondratiuk <taras@ti.com>
---
include/linux/regulator/consumer.h | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/include/linux/regulator/consumer.h b/include/linux/regulator/consumer.h
index 7bc732c..d40d909 100644
--- a/include/linux/regulator/consumer.h
+++ b/include/linux/regulator/consumer.h
@@ -380,4 +380,10 @@ static inline int regulator_is_supported_voltage_tol(struct regulator *regulator
target_uV + tol_uV);
}
+static inline int regulator_set_voltage_min(struct regulator *regulator,
+ int new_uV)
+{
+ return regulator_set_voltage(regulator, new_uV, INT_MAX);
+}
+
#endif
--
1.7.9.5
next prev parent reply other threads:[~2013-04-19 12:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 11:55 [RFC PATCH 0/2] cpufreq/regulator: Limit minimum voltage only Taras Kondratiuk
2013-04-19 11:55 ` Taras Kondratiuk [this message]
2013-04-22 13:19 ` [RFC PATCH 1/2] regulator: core: Add regulator_set_voltage_min() Mark Brown
2013-04-22 16:49 ` Taras Kondratiuk
2013-04-23 8:48 ` Mark Brown
2013-04-23 11:44 ` Taras Kondratiuk
2013-04-23 13:45 ` Mark Brown
2013-04-23 18:45 ` Taras Kondratiuk
2013-04-24 9:38 ` Mark Brown
2013-04-19 11:55 ` [RFC PATCH 2/2] cpufreq: cpufreq-cpu0: Limit minimum voltage only Taras Kondratiuk
2013-04-19 16:21 ` [RFC PATCH 0/2] cpufreq/regulator: " Nishanth Menon
2013-04-20 0:24 ` Kondratiuk, Taras
2013-04-22 6:11 ` Bedia, Vaibhav
2013-04-22 13:25 ` Mark Brown
2013-04-22 16:25 ` Taras Kondratiuk
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=1366372554-20866-2-git-send-email-taras@ti.com \
--to=taras@ti.com \
--cc=broonie@kernel.org \
--cc=cpufreq@vger.kernel.org \
--cc=eric.y.miao@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=prakity@nvidia.com \
--cc=rjw@sisk.pl \
--cc=shawn.guo@linaro.org \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®