From: Viresh Kumar <viresh.kumar@linaro.org>
To: Nick Fan <nick.fan@mediatek.com>
Cc: Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, srv_heupstream@mediatek.com,
tfiga@chromium.org, Chiawen.Lee@mediatek.com,
erin.lo@mediatek.com
Subject: Re: [PATCH] opp: Add API for getting voltage from supplies
Date: Thu, 13 Dec 2018 12:08:50 +0530 [thread overview]
Message-ID: <20181213063850.c5nu3bbe7gm647ca@vireshk-i7> (raw)
In-Reply-To: <1544445372.3502.42.camel@mtksdaap41>
On 10-12-18, 20:36, Nick Fan wrote:
> 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);
Fair enough. I couldn't find anything wrong with the patch. Will it be
possible to send this patch as part of a series which uses the new API
? So that we are sure of somebody using it eventually.
--
viresh
next prev parent reply other threads:[~2018-12-13 6:38 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
2018-12-13 6:38 ` Viresh Kumar [this message]
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=20181213063850.c5nu3bbe7gm647ca@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--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=nick.fan@mediatek.com \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@chromium.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