From: AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org>
To: viresh.kumar@linaro.org
Cc: bjorn.andersson@linaro.org, agross@kernel.org, rjw@rjwysocki.net,
devicetree@vger.kernel.org, robh+dt@kernel.org,
amit.kucheria@linaro.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org,
konrad.dybcio@somainline.org, marijn.suijten@somainline.org,
martin.botka@somainline.org, jeffrey.l.hugo@gmail.com,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>
Subject: [PATCH v4 6/7] cpufreq: qcom-hw: Allow getting the maximum transition latency for OPPs
Date: Tue, 19 Jan 2021 18:45:56 +0100 [thread overview]
Message-ID: <20210119174557.227318-7-angelogioacchino.delregno@somainline.org> (raw)
In-Reply-To: <20210119174557.227318-1-angelogioacchino.delregno@somainline.org>
In order to fine-tune the frequency scaling from various governors,
allow to set a maximum transition latency from OPPs, which may be
different depending on the SoC.
Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org>
---
drivers/cpufreq/qcom-cpufreq-hw.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/cpufreq/qcom-cpufreq-hw.c b/drivers/cpufreq/qcom-cpufreq-hw.c
index a92959bb7b50..5f67da796f6c 100644
--- a/drivers/cpufreq/qcom-cpufreq-hw.c
+++ b/drivers/cpufreq/qcom-cpufreq-hw.c
@@ -1401,6 +1401,7 @@ static int qcom_cpufreq_hw_cpu_init(struct cpufreq_policy *policy)
void __iomem *base;
struct qcom_cpufreq_data *data;
const char *fdom_resname;
+ unsigned int transition_latency;
int cpu_count, index, ret;
cpu_dev = get_cpu_device(policy->cpu);
@@ -1478,6 +1479,12 @@ static int qcom_cpufreq_hw_cpu_init(struct cpufreq_policy *policy)
goto error;
}
+ transition_latency = dev_pm_opp_get_max_transition_latency(cpu_dev);
+ if (!transition_latency)
+ transition_latency = CPUFREQ_ETERNAL;
+
+ policy->cpuinfo.transition_latency = transition_latency;
+
dev_pm_opp_of_register_em(cpu_dev, policy->cpus);
if (policy_has_boost_freq(policy)) {
--
2.30.0
next prev parent reply other threads:[~2021-01-19 19:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 17:45 [PATCH v4 0/7] cpufreq-qcom-hw: Implement full OSM programming AngeloGioacchino Del Regno
2021-01-19 17:45 ` [PATCH v4 1/7] cpufreq: blacklist SDM630/636/660 in cpufreq-dt-platdev AngeloGioacchino Del Regno
2021-04-19 19:18 ` Bjorn Andersson
2021-01-19 17:45 ` [PATCH v4 2/7] cpufreq: blacklist MSM8998 " AngeloGioacchino Del Regno
2021-04-19 19:18 ` Bjorn Andersson
2021-01-19 17:45 ` [PATCH v4 3/7] dt-bindings: arm: cpus: Document 'qcom,freq-domain' property AngeloGioacchino Del Regno
2021-01-19 17:45 ` [PATCH v4 4/7] dt-bindings: cpufreq: cpufreq-qcom-hw: Convert to YAML bindings AngeloGioacchino Del Regno
2021-04-19 19:17 ` Bjorn Andersson
2021-01-19 17:45 ` [PATCH v4 5/7] cpufreq: qcom-hw: Implement CPRh aware OSM programming AngeloGioacchino Del Regno
2021-01-20 18:25 ` Taniya Das
2021-01-20 18:54 ` AngeloGioacchino Del Regno
2021-01-20 19:05 ` Bjorn Andersson
2021-02-10 5:13 ` Viresh Kumar
2021-04-12 9:31 ` Taniya Das
2021-04-13 3:49 ` Viresh Kumar
2021-04-15 1:31 ` Taniya Das
2021-04-19 19:06 ` Bjorn Andersson
2021-04-19 18:52 ` Bjorn Andersson
2021-04-19 20:59 ` AngeloGioacchino Del Regno
2021-04-19 23:22 ` Bjorn Andersson
2021-04-20 3:37 ` Viresh Kumar
2021-01-19 17:45 ` AngeloGioacchino Del Regno [this message]
2021-04-19 19:19 ` [PATCH v4 6/7] cpufreq: qcom-hw: Allow getting the maximum transition latency for OPPs Bjorn Andersson
2021-01-19 17:45 ` [PATCH v4 7/7] dt-bindings: cpufreq: qcom-hw: Add bindings for 8998 AngeloGioacchino Del Regno
2021-04-12 5:11 ` [PATCH v4 0/7] cpufreq-qcom-hw: Implement full OSM programming Viresh Kumar
2021-04-13 2:41 ` Bjorn Andersson
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=20210119174557.227318-7-angelogioacchino.delregno@somainline.org \
--to=angelogioacchino.delregno@somainline.org \
--cc=agross@kernel.org \
--cc=amit.kucheria@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jeffrey.l.hugo@gmail.com \
--cc=konrad.dybcio@somainline.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=martin.botka@somainline.org \
--cc=phone-devel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.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).