From: Matthias Kaehlcke <mka@chromium.org>
To: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Quentin Perret <quentin.perret@arm.com>,
Taniya Das <tdas@codeaurora.org>, CK Hu <ck.hu@mediatek.com>,
Eddie Huang <eddie.huang@mediatek.com>,
Nicolas Boichat <drinkcat@chromium.org>,
Douglas Anderson <dianders@chromium.org>,
Matthias Kaehlcke <mka@chromium.org>
Subject: [PATCH 2/2] cpufreq: mediatek: Register an Energy Model
Date: Tue, 5 Feb 2019 09:52:25 -0800 [thread overview]
Message-ID: <20190205175225.25923-2-mka@chromium.org> (raw)
In-Reply-To: <20190205175225.25923-1-mka@chromium.org>
Try and register an Energy Model from mediatek-cpufreq to allow
interested subsystems like the task scheduler to use the provided
information.
Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
---
drivers/cpufreq/mediatek-cpufreq.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/cpufreq/mediatek-cpufreq.c b/drivers/cpufreq/mediatek-cpufreq.c
index eb8920d398181..e6168ee582783 100644
--- a/drivers/cpufreq/mediatek-cpufreq.c
+++ b/drivers/cpufreq/mediatek-cpufreq.c
@@ -460,6 +460,8 @@ static int mtk_cpufreq_init(struct cpufreq_policy *policy)
return ret;
}
+ dev_pm_opp_of_register_em(policy->cpus);
+
cpumask_copy(policy->cpus, &info->cpus);
policy->freq_table = freq_table;
policy->driver_data = info;
--
2.20.1.611.gfbb209baf1-goog
next prev parent reply other threads:[~2019-02-05 17:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 17:52 [PATCH 1/2] cpufreq: qcom-hw: Register an Energy Model Matthias Kaehlcke
2019-02-05 17:52 ` Matthias Kaehlcke [this message]
2019-02-06 10:13 ` [PATCH 2/2] cpufreq: mediatek: " Quentin Perret
2019-02-06 18:16 ` Matthias Kaehlcke
2019-02-07 4:08 ` Viresh Kumar
2019-02-06 4:52 ` [PATCH 1/2] cpufreq: qcom-hw: " 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=20190205175225.25923-2-mka@chromium.org \
--to=mka@chromium.org \
--cc=ck.hu@mediatek.com \
--cc=dianders@chromium.org \
--cc=drinkcat@chromium.org \
--cc=eddie.huang@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=quentin.perret@arm.com \
--cc=rjw@rjwysocki.net \
--cc=tdas@codeaurora.org \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).