From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Ilia Lin <ilia.lin@kernel.org>, Viresh Kumar <vireshk@kernel.org>,
Nishanth Menon <nm@ti.com>, Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Georgi Djakov <djakov@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-pm@vger.kernel.org, linux-clk@vger.kernel.org,
Christian Marangi <ansuelsmth@gmail.com>,
Stephan Gerhold <stephan@gerhold.net>
Subject: [PATCH v3 12/28] cpufreq: qcom-nvmem: provide separate configuration data for apq8064
Date: Sun, 2 Jul 2023 20:42:30 +0300 [thread overview]
Message-ID: <20230702174246.121656-13-dmitry.baryshkov@linaro.org> (raw)
In-Reply-To: <20230702174246.121656-1-dmitry.baryshkov@linaro.org>
APQ8064 can scale core voltage according to the frequency needs. Rather
than reusing the A/B format multiplexer, use a simple fuse parsing
function and configure required regulator.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
---
drivers/cpufreq/qcom-cpufreq-nvmem.c | 49 ++++++++++++++++++++++++++--
1 file changed, 47 insertions(+), 2 deletions(-)
diff --git a/drivers/cpufreq/qcom-cpufreq-nvmem.c b/drivers/cpufreq/qcom-cpufreq-nvmem.c
index 792423590279..422fd8ca8a00 100644
--- a/drivers/cpufreq/qcom-cpufreq-nvmem.c
+++ b/drivers/cpufreq/qcom-cpufreq-nvmem.c
@@ -26,6 +26,7 @@
#include <linux/platform_device.h>
#include <linux/pm_domain.h>
#include <linux/pm_opp.h>
+#include <linux/regulator/consumer.h>
#include <linux/slab.h>
#include <linux/soc/qcom/smem.h>
@@ -39,6 +40,7 @@ struct qcom_cpufreq_match_data {
char **pvs_name,
struct qcom_cpufreq_drv *drv);
const char **genpd_names;
+ const char * const *regulator_names;
};
struct qcom_cpufreq_drv {
@@ -203,6 +205,34 @@ static int qcom_cpufreq_krait_name_version(struct device *cpu_dev,
return ret;
}
+static int qcom_cpufreq_apq8064_name_version(struct device *cpu_dev,
+ struct nvmem_cell *speedbin_nvmem,
+ char **pvs_name,
+ struct qcom_cpufreq_drv *drv)
+{
+ int speed = 0, pvs = 0;
+ u8 *speedbin;
+ size_t len;
+ int ret = 0;
+
+ speedbin = nvmem_cell_read(speedbin_nvmem, &len);
+ if (IS_ERR(speedbin))
+ return PTR_ERR(speedbin);
+
+ if (len != 4)
+ return -EINVAL;
+
+ get_krait_bin_format_a(cpu_dev, &speed, &pvs, speedbin);
+
+ snprintf(*pvs_name, sizeof("speedXX-pvsXX"), "speed%d-pvs%d",
+ speed, pvs);
+
+ drv->versions = (1 << speed);
+
+ kfree(speedbin);
+ return ret;
+}
+
static const struct qcom_cpufreq_match_data match_data_kryo = {
.get_version = qcom_cpufreq_kryo_name_version,
};
@@ -217,6 +247,16 @@ static const struct qcom_cpufreq_match_data match_data_qcs404 = {
.genpd_names = qcs404_genpd_names,
};
+static const char * apq8064_regulator_names[] = {
+ "vdd-core",
+ NULL
+};
+
+static const struct qcom_cpufreq_match_data match_data_apq8064 = {
+ .get_version = qcom_cpufreq_apq8064_name_version,
+ .regulator_names = apq8064_regulator_names,
+};
+
static int qcom_cpufreq_probe(struct platform_device *pdev)
{
struct qcom_cpufreq_drv *drv;
@@ -304,7 +344,12 @@ static int qcom_cpufreq_probe(struct platform_device *pdev)
config.virt_devs = NULL;
}
- if (config.supported_hw || config.genpd_names) {
+ if (drv->data->regulator_names)
+ config.regulator_names = drv->data->regulator_names;
+
+ if (config.supported_hw ||
+ config.genpd_names ||
+ config.regulator_names) {
drv->opp_tokens[cpu] = dev_pm_opp_set_config(cpu_dev, &config);
if (drv->opp_tokens[cpu] < 0) {
ret = drv->opp_tokens[cpu];
@@ -363,7 +408,7 @@ static const struct of_device_id qcom_cpufreq_match_list[] __initconst = {
{ .compatible = "qcom,msm8996", .data = &match_data_kryo },
{ .compatible = "qcom,qcs404", .data = &match_data_qcs404 },
{ .compatible = "qcom,ipq8064", .data = &match_data_krait },
- { .compatible = "qcom,apq8064", .data = &match_data_krait },
+ { .compatible = "qcom,apq8064", .data = &match_data_apq8064 },
{ .compatible = "qcom,msm8974", .data = &match_data_krait },
{ .compatible = "qcom,msm8960", .data = &match_data_krait },
{},
--
2.39.2
next prev parent reply other threads:[~2023-07-02 17:43 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 17:42 [PATCH v3 00/28] ARM: qcom: apq8064: support CPU frequency scaling Dmitry Baryshkov
2023-07-02 17:42 ` [PATCH v3 01/28] dt-bindings: opp: opp-v2-kryo-cpu: support Qualcomm Krait SoCs Dmitry Baryshkov
2023-07-02 17:42 ` [PATCH v3 02/28] dt-bindings: soc: qcom: merge qcom,saw2.txt into qcom,spm.yaml Dmitry Baryshkov
2023-07-02 17:42 ` [PATCH v3 03/28] dt-bindings: soc: qcom: qcom,saw2: define optional regulator node Dmitry Baryshkov
2023-07-02 17:42 ` [PATCH v3 04/28] dt-bindings: clock: qcom,krait-cc: Krait core clock controller Dmitry Baryshkov
2023-07-02 17:42 ` [PATCH v3 05/28] dt-bindings: cache: describe L2 cache on Qualcomm Krait platforms Dmitry Baryshkov
2023-07-02 18:48 ` Rob Herring
2023-07-02 20:09 ` Krzysztof Kozlowski
2023-07-02 20:46 ` Krzysztof Kozlowski
2023-07-02 17:42 ` [PATCH v3 06/28] interconnect: icc-clk: add support for scaling using OPP Dmitry Baryshkov
2023-07-03 11:17 ` Konrad Dybcio
2023-07-02 17:42 ` [PATCH v3 07/28] clk: qcom: krait-cc: rewrite driver to use clk_hw instead of clk Dmitry Baryshkov
2023-07-02 17:42 ` [PATCH v3 08/28] soc: qcom: spm: add support for voltage regulator Dmitry Baryshkov
2023-07-03 11:21 ` Konrad Dybcio
2023-07-02 17:42 ` [PATCH v3 09/28] cpufreq: qcom-nvmem: create L2 cache device Dmitry Baryshkov
2023-07-02 17:42 ` [PATCH v3 10/28] cpufreq: qcom-nvmem: also accept operating-points-v2-krait-cpu Dmitry Baryshkov
2023-07-02 17:42 ` [PATCH v3 11/28] cpufreq: qcom-nvmem: drop pvs_ver for format a fuses Dmitry Baryshkov
2023-07-02 17:42 ` Dmitry Baryshkov [this message]
2023-07-02 17:42 ` [PATCH v3 13/28] soc: qcom: Add driver for Qualcomm Krait L2 cache scaling Dmitry Baryshkov
2023-07-03 11:25 ` Konrad Dybcio
2023-07-02 17:42 ` [PATCH v3 14/28] ARM: dts: qcom: apq8064-asus-nexus7-flo: constraint cpufreq regulators Dmitry Baryshkov
2023-07-02 17:42 ` [PATCH v3 15/28] ARM: dts: qcom: apq8064-cm-qs600: " Dmitry Baryshkov
2023-07-03 11:26 ` Konrad Dybcio
2023-07-02 17:42 ` [PATCH v3 16/28] ARM: dts: qcom: apq8064-ifc6410: " Dmitry Baryshkov
2023-07-02 17:42 ` [PATCH v3 17/28] ARM: dts: qcom: apq8064-sony-xperia-lagan-yuga: " Dmitry Baryshkov
2023-07-03 11:26 ` Konrad Dybcio
2023-07-02 17:42 ` [PATCH v3 18/28] ARM: dts: qcom: apq8064: rename SAW nodes to power-manager Dmitry Baryshkov
2023-07-02 17:42 ` [PATCH v3 19/28] ARM: dts: qcom: apq8064: declare SAW2 regulators Dmitry Baryshkov
2023-07-02 17:42 ` [PATCH v3 20/28] ARM: dts: qcom: apq8064: add Krait clock controller Dmitry Baryshkov
2023-07-03 11:27 ` Konrad Dybcio
2023-07-02 17:42 ` [PATCH v3 21/28] ARM: dts: qcom: apq8064: add L2 cache scaling Dmitry Baryshkov
2023-07-02 20:09 ` Krzysztof Kozlowski
2023-07-02 17:42 ` [PATCH v3 22/28] ARM: dts: qcom: apq8064: add simple CPUFreq support Dmitry Baryshkov
2023-07-03 11:30 ` Konrad Dybcio
2023-07-02 17:42 ` [PATCH v3 23/28] ARM: dts: qcom: apq8064: enable passive CPU cooling Dmitry Baryshkov
2023-07-02 17:42 ` [PATCH v3 24/28] ARM: dts: qcom: msm8960: declare SAW2 regulators Dmitry Baryshkov
2023-07-02 17:42 ` [PATCH v3 25/28] ARM: dts: qcom: apq8084: drop 'regulator' property from SAW2 device Dmitry Baryshkov
2023-07-02 17:42 ` [PATCH v3 26/28] ARM: dts: qcom: msm8974: " Dmitry Baryshkov
2023-07-02 17:42 ` [PATCH v3 27/28] ARM: dts: qcom: ipq4019: drop 'regulator' property from SAW2 devices Dmitry Baryshkov
2023-07-02 17:42 ` [PATCH v3 28/28] ARM: dts: qcom: ipq8064: " Dmitry Baryshkov
2023-07-03 4:39 ` [PATCH v3 00/28] ARM: qcom: apq8064: support CPU frequency scaling Viresh Kumar
2023-07-07 9:34 ` Linus Walleij
2023-07-07 10:59 ` Dmitry Baryshkov
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=20230702174246.121656-13-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=ilia.lin@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=stephan@gerhold.net \
--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