From: Nick Fan <nick.fan@mediatek.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Nishanth Menon <nm@ti.com>,
Chiawen.Lee@mediatek.com, srv_heupstream@mediatek.com,
linux-pm@vger.kernel.org, Stephen Boyd <sboyd@kernel.org>,
Viresh Kumar <vireshk@kernel.org>,
erin.lo@mediatek.com, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, tfiga@chromium.org,
linux-mediatek@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] opp: Add API for getting voltage from supplies
Date: Mon, 10 Dec 2018 20:36:12 +0800 [thread overview]
Message-ID: <1544445372.3502.42.camel@mtksdaap41> (raw)
In-Reply-To: <20181204082158.rb7uzdiwmcotwoxh@vireshk-i7>
On Tue, 2018-12-04 at 13:51 +0530, Viresh Kumar wrote:
> On 04-12-18, 14:59, Nick Fan wrote:
> > Add API to get voltage for multiple supplies from opp table
>
> And who needs to use this new API ? It would be better to add the user in the
> same series to make sure this really gets used.
This new API would be required when handling multiple regulators.
You can check the example 4 in
Documentation/devicetree/bindings/opp/opp.txt for multiple regulators.
When we specify multiple regulator voltages in device tree, we are not
able to access the secondary supply voltages.
Because the dev_pm_opp_get_voltage only returns the first supply
voltages, this new API is required to get the specific supply.
>
> > Signed-off-by: Nick Fan <Nick.Fan@mediatek.com>
> > ---
> > drivers/opp/core.c | 28 ++++++++++++++++++++++++++++
> > include/linux/pm_opp.h | 3 +++
> > 2 files changed, 31 insertions(+)
> >
> > diff --git a/drivers/opp/core.c b/drivers/opp/core.c
> > index 2c2df4e..ee73546 100644
> > --- a/drivers/opp/core.c
> > +++ b/drivers/opp/core.c
> > @@ -113,6 +113,34 @@ unsigned long dev_pm_opp_get_voltage(struct dev_pm_opp *opp)
> > EXPORT_SYMBOL_GPL(dev_pm_opp_get_voltage);
> >
> > /**
> > + * dev_pm_opp_get_voltage_supply() - Gets the voltage corresponding to an opp
> > + * with index
> > + * @opp: opp for which voltage has to be returned for
> > + * @index: index to specify the returned supplies
> > + *
> > + * Return: voltage in micro volt corresponding to the opp with index, else
> > + * return 0
> > + *
> > + * This is useful for devices with multiple power supplies.
> > + */
> > +unsigned long dev_pm_opp_get_voltage_supply(struct dev_pm_opp *opp,
> > + unsigned int index)
>
> How will the users of this API get the index ?
For the users who only use one supply, they can use
dev_pm_opp_get_voltage to get the voltage data from an opp.
But if the users who use more than one supply, they will need this API
to get their voltage data from OPP.
The users should know about the supply count while creating opp table by
using dev_pm_opp_set_regulators function.
By using this API, the users can get the voltages by using index to
specify which supplies they want.
The following is a simple example to get multiple regulators by this
API.
for (i = 0; i < regulator_num; i++)
target_volt[i] = dev_pm_opp_get_voltage_supply(opp, i);
>
> > +{
> > + if (IS_ERR_OR_NULL(opp)) {
> > + pr_err("%s: Invalid parameters\n", __func__);
> > + return 0;
> > + }
> > +
> > + if (index >= opp->opp_table->regulator_count) {
> > + pr_err("%s: Invalid supply index: %u\n", __func__, index);
> > + return 0;
> > + }
> > +
> > + return opp->supplies[index].u_volt;
>
Nick Fan
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-10 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1543906760-15631-1-git-send-email-Nick.Fan@mediatek.com>
2018-12-04 8:21 ` [PATCH] opp: Add API for getting voltage from supplies Viresh Kumar
2018-12-10 12:36 ` Nick Fan [this message]
2018-12-13 6:38 ` Viresh Kumar
2018-12-13 10:36 ` Nick Fan
2018-12-13 10:42 ` Viresh Kumar
2018-12-14 1:36 ` Nick Fan
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=1544445372.3502.42.camel@mtksdaap41 \
--to=nick.fan@mediatek.com \
--cc=Chiawen.Lee@mediatek.com \
--cc=erin.lo@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@chromium.org \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@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