[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200504051303.zvmvvjipdkjpo4yh@vireshk-i7>
Date: Mon, 4 May 2020 10:43:03 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Ansuel Smith <ansuelsmth@...il.com>
Cc: Ilia Lin <ilia.lin@...nel.org>, Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Sricharan R <sricharan@...eaurora.org>,
linux-pm@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] cpufreq: qcom: fix wrong compatible binding
On 01-05-20, 00:22, Ansuel Smith wrote:
> Binding in Documentation is still "operating-points-v2-kryo-cpu".
> Restore the old binding to fix the compatibility problem.
>
> Fixes: a8811ec764f9 ("cpufreq: qcom: Add support for krait based socs")
> Signed-off-by: Ansuel Smith <ansuelsmth@...il.com>
> ---
> drivers/cpufreq/qcom-cpufreq-nvmem.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/qcom-cpufreq-nvmem.c b/drivers/cpufreq/qcom-cpufreq-nvmem.c
> index a1b8238872a2..d06b37822c3d 100644
> --- a/drivers/cpufreq/qcom-cpufreq-nvmem.c
> +++ b/drivers/cpufreq/qcom-cpufreq-nvmem.c
> @@ -277,7 +277,7 @@ static int qcom_cpufreq_probe(struct platform_device *pdev)
> if (!np)
> return -ENOENT;
>
> - ret = of_device_is_compatible(np, "operating-points-v2-qcom-cpu");
> + ret = of_device_is_compatible(np, "operating-points-v2-kryo-cpu");
> if (!ret) {
> of_node_put(np);
> return -ENOENT;
Applied. Thanks.
--
viresh
Powered by blists - more mailing lists