From: Viresh Kumar <viresh.kumar@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: linaro-kernel@lists.linaro.org, sboyd@codeaurora.org, nm@ti.com,
Liam Girdwood <lgirdwood@gmail.com>,
"open list:VOLTAGE AND CURRENT REGULATOR FRAMEWORK"
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regulator: core: Define regulator_set_voltage_triplet()
Date: Mon, 17 Aug 2015 07:49:23 +0530 [thread overview]
Message-ID: <20150817021923.GM1162@linux> (raw)
In-Reply-To: <20150815140805.GB10748@sirena.org.uk>
On 15-08-15, 07:08, Mark Brown wrote:
> On Sat, Aug 15, 2015 at 08:41:49AM +0530, Viresh Kumar wrote:
>
> > Hopefully below version looks better ?
>
> Please don't bury patches at the end of replies to messages in the
> middle of threads, send them in a form where they can be applied
> directly.
Okay. I thought its fine to send patches like this and this can be
applied directly with the --scissors option to git am or with
mailinfo.scissors option set in configuration file.
But will surely send patches separately to you.
> > Subject: [PATCH] regulator: core: Define regulator_set_voltage_triplet()
> >
> > The OPP (Operating performance points) v2 bindings allows regulator
> > voltage to be supplied as a triplet of <target min max> voltages.
> >
> > Add regulator_set_voltage_triplet() API in regulator core to support
> > that.
>
> This should explain why this is useful at a regulator API level, not
> explain that some user decided to do something.
Okay.
> > +static inline int regulator_set_voltage_triplet(struct regulator *regulator,
> > + int min_uV, int target_uV,
> > + int max_uV)
> > +{
> > + if (!regulator_set_voltage(regulator, target_uV, max_uV))
>
> Make this a check for == 0 which is what you mean here, this isn't a
> boolean function.
Okay.
--
viresh
prev parent reply other threads:[~2015-08-17 2:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 12:00 [PATCH] regulator: core: Define regulator_set_voltage_triplet() Viresh Kumar
2015-08-14 16:25 ` Mark Brown
2015-08-15 3:11 ` Viresh Kumar
2015-08-15 14:08 ` Mark Brown
2015-08-17 2:19 ` Viresh Kumar [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=20150817021923.GM1162@linux \
--to=viresh.kumar@linaro.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=sboyd@codeaurora.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