From: Viresh Kumar <viresh.kumar@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Marijn Suijten <marijn.suijten@somainline.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: blocklist more Qualcomm platforms in cpufreq-dt-platdev
Date: Wed, 9 Aug 2023 10:57:43 +0530 [thread overview]
Message-ID: <20230809052743.hp2vvq2rr25hqine@vireshk-i7> (raw)
In-Reply-To: <20230809-topic-cpufreq_qcom_block-v1-1-624acbcefa5c@linaro.org>
On 09-08-23, 02:07, Konrad Dybcio wrote:
> All Qualcomm platforms utilizing the qcom-cpufreq-hw driver have no
> business in using cpufreq-dt. Prevent that from happening.
>
> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
> ---
> drivers/cpufreq/cpufreq-dt-platdev.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c
> index adb3579a1fee..fb2875ce1fdd 100644
> --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> @@ -144,14 +144,18 @@ static const struct of_device_id blocklist[] __initconst = {
> { .compatible = "qcom,apq8096", },
> { .compatible = "qcom,msm8996", },
> { .compatible = "qcom,msm8998", },
> + { .compatible = "qcom,qcm2290", },
> { .compatible = "qcom,qcs404", },
> + { .compatible = "qcom,qdu1000", },
> { .compatible = "qcom,sa8155p" },
> { .compatible = "qcom,sa8540p" },
> + { .compatible = "qcom,sa8775p" },
> { .compatible = "qcom,sc7180", },
> { .compatible = "qcom,sc7280", },
> { .compatible = "qcom,sc8180x", },
> { .compatible = "qcom,sc8280xp", },
> { .compatible = "qcom,sdm845", },
> + { .compatible = "qcom,sdx75", },
> { .compatible = "qcom,sm6115", },
> { .compatible = "qcom,sm6350", },
> { .compatible = "qcom,sm6375", },
> @@ -159,6 +163,8 @@ static const struct of_device_id blocklist[] __initconst = {
> { .compatible = "qcom,sm8150", },
> { .compatible = "qcom,sm8250", },
> { .compatible = "qcom,sm8350", },
> + { .compatible = "qcom,sm8450", },
> + { .compatible = "qcom,sm8550", },
>
> { .compatible = "st,stih407", },
> { .compatible = "st,stih410", },
Applied. Thanks.
--
viresh
next prev parent reply other threads:[~2023-08-09 5:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 0:07 [PATCH] cpufreq: blocklist more Qualcomm platforms in cpufreq-dt-platdev Konrad Dybcio
2023-08-09 5:27 ` Viresh Kumar [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-20 21:57 Bjorn Andersson
2021-08-23 3:17 ` 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=20230809052743.hp2vvq2rr25hqine@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=rafael@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;
as well as URLs for NNTP newsgroup(s).