From: Roger Lu <roger.lu@mediatek.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
"Nishanth Menon" <nm@ti.com>,
"Andrew-sh Cheng (鄭式勳)" <andrew-sh.cheng@mediatek.com>,
srv_heupstream <srv_heupstream@mediatek.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Stephen Boyd" <sboyd@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
yt.lee@mediatek.com, "Chanwoo Choi" <cw00.choi@samsung.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
"MyungJoo Ham" <myungjoo.ham@samsung.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Fan Chen (陳凡)" <fan.chen@mediatek.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 6/8] PM / OPP: Support adjusting OPP voltages at runtime
Date: Mon, 29 Jul 2019 11:39:15 +0800 [thread overview]
Message-ID: <1564371555.18434.11.camel@mtksdaap41> (raw)
In-Reply-To: <20190520044704.unftq6q5vy73z5bo@vireshk-i7>
Dear Stephen Boyd,
This patch is derived from [1]. Please kindly shares the suggestion to
us. Thanks very much.
[1]: https://lore.kernel.org/patchwork/patch/599279/
Dear Viresh,
I followed _opp_set_availability() coding style to refine
dev_pm_opp_adjust_voltage() from this patch. Is this refinement suitable
for OPP core? Thanks a lot.
On Mon, 2019-05-20 at 12:47 +0800, Viresh Kumar wrote:
> On 16-05-19, 17:08, Andrew-sh.Cheng wrote:
> > From: Stephen Boyd <sboyd@codeaurora.org>
> >
> > On some SoCs the Adaptive Voltage Scaling (AVS) technique is
> > employed to optimize the operating voltage of a device. At a
> > given frequency, the hardware monitors dynamic factors and either
> > makes a suggestion for how much to adjust a voltage for the
> > current frequency, or it automatically adjusts the voltage
> > without software intervention. Add an API to the OPP library for
> > the former case, so that AVS type devices can update the voltages
> > for an OPP when the hardware determines the voltage should
> > change. The assumption is that drivers like CPUfreq or devfreq
> > will register for the OPP notifiers and adjust the voltage
> > according to suggestions that AVS makes.
> >
> > This patch is devired from [1] submitted by Stephen.
> > [1] https://lore.kernel.org/patchwork/patch/599279/
> >
> > Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> > Signed-off-by: Roger Lu <roger.lu@mediatek.com>
> > ---
> > drivers/opp/core.c | 78 ++++++++++++++++++++++++++++++++++++++++++++++++++
> > include/linux/pm_opp.h | 11 +++++++
> > 2 files changed, 89 insertions(+)
>
> This is an rcu implementation which got removed long back from OPP core. Please
> align this with the latest changes.
>
/**
* dev_pm_opp_adjust_voltage() - helper to change the voltage of an OPP
* @dev: device for which we do this operation
* @freq: OPP frequency to adjust voltage of
* @u_volt: new OPP voltage
*
* Return: -EINVAL for bad pointers, -ENOMEM if no memory available for
the
* copy operation, returns 0 if no modifcation was done OR modification
was
* successful.
*/
int dev_pm_opp_adjust_voltage(struct device *dev, unsigned long freq,
unsigned long u_volt)
{
struct opp_table *opp_table;
struct dev_pm_opp *tmp_opp, *opp = ERR_PTR(-ENODEV);
int r = 0;
/* Find the opp_table */
opp_table = _find_opp_table(dev);
if (IS_ERR(opp_table)) {
r = PTR_ERR(opp_table);
dev_warn(dev, "%s: Device OPP not found (%d)\n", __func__, r);
return r;
}
mutex_lock(&opp_table->lock);
/* Do we have the frequency? */
list_for_each_entry(tmp_opp, &opp_table->opp_list, node) {
if (tmp_opp->rate == freq) {
opp = tmp_opp;
break;
}
}
if (IS_ERR(opp)) {
r = PTR_ERR(opp);
goto adjust_unlock;
}
/* Is update really needed? */
if (opp->supplies->u_volt == u_volt)
goto adjust_unlock;
opp->supplies->u_volt = u_volt;
dev_pm_opp_get(opp);
mutex_unlock(&opp_table->lock);
/* Notify the voltage change of the OPP */
blocking_notifier_call_chain(&opp_table->head,
OPP_EVENT_ADJUST_VOLTAGE,
opp);
dev_pm_opp_put(opp);
goto adjust_put_table;
adjust_unlock:
mutex_unlock(&opp_table->lock);
adjust_put_table:
dev_pm_opp_put_opp_table(opp_table);
return r;
}
Sincerely,
Roger Lu.
_______________________________________________
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:[~2019-07-29 3:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 9:08 [PATCH 0/8] Add cpufreq and cci devfreq for mt8183, and SVS support Andrew-sh.Cheng
2019-05-16 9:08 ` [PATCH 1/8] cpufreq: mediatek: change to regulator_get_optional Andrew-sh.Cheng
2019-05-16 9:08 ` [PATCH 2/8] cpufreq: mediatek: add clock enable for intermediate clock Andrew-sh.Cheng
2019-05-16 9:08 ` [PATCH 3/8] cpufreq: mediatek: Add support for mt8183 Andrew-sh.Cheng
2019-05-16 9:08 ` [PATCH 4/8] dt-bindings: devfreq: add compatible for mt8183 cci devfreq Andrew-sh.Cheng
2019-05-20 4:43 ` Viresh Kumar
2019-05-16 9:08 ` [PATCH 5/8] devfreq: add mediatek " Andrew-sh.Cheng
2019-05-16 9:08 ` [PATCH 6/8] PM / OPP: Support adjusting OPP voltages at runtime Andrew-sh.Cheng
2019-05-20 4:47 ` Viresh Kumar
2019-07-29 3:39 ` Roger Lu [this message]
2019-07-29 9:20 ` Viresh Kumar
2019-05-16 9:08 ` [PATCH 7/8] cpufreq: mediatek: add opp notification for SVS support Andrew-sh.Cheng
2019-05-27 7:02 ` Hsin-Yi Wang
2019-05-16 9:08 ` [PATCH 8/8] devfreq: mediatek: cci devfreq register " Andrew-sh.Cheng
2019-05-24 8:04 ` Hsin-Yi Wang
2019-05-16 9:23 ` [PATCH 0/8] Add cpufreq and cci devfreq for mt8183, and " Viresh Kumar
2019-05-16 12:23 ` andrew-sh.cheng
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=1564371555.18434.11.camel@mtksdaap41 \
--to=roger.lu@mediatek.com \
--cc=andrew-sh.cheng@mediatek.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=fan.chen@mediatek.com \
--cc=kyungmin.park@samsung.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=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=myungjoo.ham@samsung.com \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=sboyd@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=viresh.kumar@linaro.org \
--cc=yt.lee@mediatek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox