From: Hector Yuan <hector.yuan@mediatek.com>
To: Lukasz Luba <lukasz.luba@arm.com>
Cc: wsd_upstream@mediatek.com, linux-pm@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 1/1] cpufreq: mediatek-hw: Register EM power table
Date: Fri, 9 Oct 2020 12:31:26 +0800 [thread overview]
Message-ID: <1602217886.21446.48.camel@mtkswgap22> (raw)
In-Reply-To: <7e58516f-a6bf-eac4-9dfb-9a4d7efa7498@arm.com>
On Thu, 2020-10-08 at 13:55 +0100, Lukasz Luba wrote:
> Hi Hector,
>
> On 10/8/20 1:13 PM, Hector Yuan wrote:
> > From: "Hector.Yuan" <hector.yuan@mediatek.com>
> >
> > Register CPU power table to energy model framework
> >
> > Signed-off-by: Hector.Yuan <hector.yuan@mediatek.com>
> > ---
> > drivers/cpufreq/mediatek-cpufreq-hw.c | 50 +++++++++++++++++++++++++--------
> > 1 file changed, 38 insertions(+), 12 deletions(-)
> >
> > diff --git a/drivers/cpufreq/mediatek-cpufreq-hw.c b/drivers/cpufreq/mediatek-cpufreq-hw.c
> > index 8fa12e5..3808ea0 100644
> > --- a/drivers/cpufreq/mediatek-cpufreq-hw.c
> > +++ b/drivers/cpufreq/mediatek-cpufreq-hw.c
> > @@ -5,6 +5,7 @@
> >
> > #include <linux/bitfield.h>
> > #include <linux/cpufreq.h>
> > +#include <linux/energy_model.h>
> > #include <linux/init.h>
> > #include <linux/kernel.h>
> > #include <linux/module.h>
> > @@ -17,9 +18,10 @@
> > #define LUT_ROW_SIZE 0x4
> >
> > enum {
> > - REG_LUT_TABLE,
> > - REG_ENABLE,
> > - REG_PERF_STATE,
> > + REG_FREQ_LUT_TABLE,
> > + REG_FREQ_ENABLE,
> > + REG_FREQ_PERF_STATE,
> > + REG_EM_POWER_TBL,
> >
> > REG_ARRAY_SIZE,
> > };
> > @@ -27,23 +29,44 @@ enum {
> > struct cpufreq_mtk {
> > struct cpufreq_frequency_table *table;
> > void __iomem *reg_bases[REG_ARRAY_SIZE];
> > + int nr_opp;
> > cpumask_t related_cpus;
> > };
> >
> > static const u16 cpufreq_mtk_offsets[REG_ARRAY_SIZE] = {
> > - [REG_LUT_TABLE] = 0x0,
> > - [REG_ENABLE] = 0x84,
> > - [REG_PERF_STATE] = 0x88,
> > + [REG_FREQ_LUT_TABLE] = 0x0,
> > + [REG_FREQ_ENABLE] = 0x84,
> > + [REG_FREQ_PERF_STATE] = 0x88,
> > + [REG_EM_POWER_TBL] = 0x3D0,
> > };
> >
> > static struct cpufreq_mtk *mtk_freq_domain_map[NR_CPUS];
> >
> > +static int mtk_cpufreq_get_cpu_power(unsigned long *mW,
> > + unsigned long *KHz, int cpu)
> > +{
> > + struct cpufreq_mtk *c = mtk_freq_domain_map[cpu];
> > + int i;
> > +
> > + for (i = 0; i < c->nr_opp; i++) {
> > + if (c->table[i].frequency < *KHz)
> > + break;
> > + }
> > + i--;
> > +
> > + *KHz = c->table[i].frequency;
> > + *mW = readl_relaxed(c->reg_bases[REG_EM_POWER_TBL] +
> > + i * LUT_ROW_SIZE) / 1000;
> > +
> > + return 0;
> > +}
> > +
> > static int mtk_cpufreq_hw_target_index(struct cpufreq_policy *policy,
> > unsigned int index)
> > {
> > struct cpufreq_mtk *c = policy->driver_data;
> >
> > - writel_relaxed(index, c->reg_bases[REG_PERF_STATE]);
> > + writel_relaxed(index, c->reg_bases[REG_FREQ_PERF_STATE]);
> >
> > return 0;
> > }
> > @@ -55,7 +78,7 @@ static unsigned int mtk_cpufreq_hw_get(unsigned int cpu)
> >
> > c = mtk_freq_domain_map[cpu];
> >
> > - index = readl_relaxed(c->reg_bases[REG_PERF_STATE]);
> > + index = readl_relaxed(c->reg_bases[REG_FREQ_PERF_STATE]);
> > index = min(index, LUT_MAX_ENTRIES - 1);
> >
> > return c->table[index].frequency;
> > @@ -64,6 +87,7 @@ static unsigned int mtk_cpufreq_hw_get(unsigned int cpu)
> > static int mtk_cpufreq_hw_cpu_init(struct cpufreq_policy *policy)
> > {
> > struct cpufreq_mtk *c;
> > + struct em_data_callback em_cb = EM_DATA_CB(mtk_cpufreq_get_cpu_power);
> >
> > c = mtk_freq_domain_map[policy->cpu];
> > if (!c) {
> > @@ -77,7 +101,8 @@ static int mtk_cpufreq_hw_cpu_init(struct cpufreq_policy *policy)
> > policy->driver_data = c;
> >
> > /* HW should be in enabled state to proceed now */
> > - writel_relaxed(0x1, c->reg_bases[REG_ENABLE]);
> > + writel_relaxed(0x1, c->reg_bases[REG_FREQ_ENABLE]);
> > + em_register_perf_domain(policy->cpus, c->nr_opp, &em_cb);
>
>
> The function name has changed recently (v5.9-rc1) to:
> em_dev_register_perf_domain()
>
> Please check your base kernel tree and update.
>
> Regards,
> Lukasz
>
OK, will check my base kernel and update this.
Thank you.
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2020-10-09 4:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 12:13 [PATCH v1] cpufreq: mediatek-hw: Register EM power table Hector Yuan
2020-10-08 12:13 ` [PATCH v1 1/1] " Hector Yuan
2020-10-08 12:55 ` Lukasz Luba
2020-10-09 4:31 ` Hector Yuan [this message]
2020-10-09 4:19 ` Viresh Kumar
2020-10-09 4:42 ` Hector Yuan
2020-10-09 5:15 ` Viresh Kumar
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=1602217886.21446.48.camel@mtkswgap22 \
--to=hector.yuan@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=lukasz.luba@arm.com \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
--cc=wsd_upstream@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;
as well as URLs for NNTP newsgroup(s).