diff options
| author |  Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
| 2023-10-19 12:50:09 +0200 |
|---|---|---|
| committer |  Viresh Kumar <viresh.kumar@linaro.org>
| 2023-10-25 15:50:53 +0530 |
| commit | ff63282ed2271d242baaa2026cd8acb0c0b990ff (patch) | |
| tree | a900208773d4ce663d69f2228ffdc201ca12352f /drivers/cpufreq/qcom-cpufreq-nvmem.c | |
| parent | cpufreq: qcom-nvmem: drop pvs_ver for format a fuses (diff) | |
| download | linux-ff63282ed2271d242baaa2026cd8acb0c0b990ff.tar.gz linux-ff63282ed2271d242baaa2026cd8acb0c0b990ff.tar.bz2 linux-ff63282ed2271d242baaa2026cd8acb0c0b990ff.zip | |
cpufreq: qcom-nvmem: also accept operating-points-v2-krait-cpu
the qcom-cpufreq-nvmem driver attempts to support both Qualcomm Kryo
(newer 64-bit ARMv8 cores) and Krait (older 32-bit ARMv7 cores). It
makes no sense to use 'operating-points-v2-kryo-cpu' compatibility node
for the Krait cores. Add support for 'operating-points-v2-krait-cpu'
compatibility string.
Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Diffstat (limited to 'drivers/cpufreq/qcom-cpufreq-nvmem.c')
| -rw-r--r-- | drivers/cpufreq/qcom-cpufreq-nvmem.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/drivers/cpufreq/qcom-cpufreq-nvmem.c b/drivers/cpufreq/qcom-cpufreq-nvmem.c index ac8c36dc6a1f..ba6720351a4c 100644 --- a/drivers/cpufreq/qcom-cpufreq-nvmem.c +++ b/drivers/cpufreq/qcom-cpufreq-nvmem.c @@ -322,7 +322,8 @@ static int qcom_cpufreq_probe(struct platform_device *pdev) if (!np) return -ENOENT; - ret = of_device_is_compatible(np, "operating-points-v2-kryo-cpu"); + ret = of_device_is_compatible(np, "operating-points-v2-kryo-cpu") || + of_device_is_compatible(np, "operating-points-v2-krait-cpu"); if (!ret) { of_node_put(np); return -ENOENT; |