Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Stephan Gerhold <stephan@gerhold.net>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: ilia.lin@kernel.org, agross@kernel.org, rafael@kernel.org,
	viresh.kumar@linaro.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, linux-pm@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 4/4] cpufreq: blocklist Qualcomm msm8939 in cpufreq-dt-platdev
Date: Fri, 8 Jul 2022 11:43:49 +0200	[thread overview]
Message-ID: <Ysf8VRaXdGg+8Ev3@gerhold.net> (raw)
In-Reply-To: <20220708014419.2009018-5-bryan.odonoghue@linaro.org>

On Fri, Jul 08, 2022 at 02:44:19AM +0100, Bryan O'Donoghue wrote:
> msm8939 will use qcom-cpufreq-nvmem. Block it on the generic cpufreq-dt
> list.
> 
> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>

Personally I would defer this patch as well until cpufreq is properly
enabled on msm8939 together with the qcom-cpufreq-nvmem changes and CPR.

I'm not strictly opposed to get this in now, but it also does not really
make any functional difference, or does it?

> ---
>  drivers/cpufreq/cpufreq-dt-platdev.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c
> index 2c96de3f2d83c..26c97ab778974 100644
> --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> @@ -137,6 +137,7 @@ static const struct of_device_id blocklist[] __initconst = {
>  	{ .compatible = "nvidia,tegra210", },
>  
>  	{ .compatible = "qcom,apq8096", },
> +	{ .compatible = "qcom,msm8939", },
>  	{ .compatible = "qcom,msm8996", },
>  	{ .compatible = "qcom,qcs404", },
>  	{ .compatible = "qcom,sa8155p" },
> -- 
> 2.36.1
> 

      reply	other threads:[~2022-07-08  9:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08  1:44 [PATCH v2 0/4] msm8939 cpufreq preparatory work Bryan O'Donoghue
2022-07-08  1:44 ` [PATCH v2 1/4] dt-bindings: opp: opp-v2-kryo-cpu: Fix example binding checks Bryan O'Donoghue
2022-07-08  1:44 ` [PATCH v2 2/4] dt-bindings: opp: Add missing compat devices Bryan O'Donoghue
2022-07-08  1:44 ` [PATCH v2 3/4] dt-bindings: opp: Add msm8939 to the compatible list Bryan O'Donoghue
2022-07-08  1:44 ` [PATCH v2 4/4] cpufreq: blocklist Qualcomm msm8939 in cpufreq-dt-platdev Bryan O'Donoghue
2022-07-08  9:43   ` Stephan Gerhold [this message]

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=Ysf8VRaXdGg+8Ev3@gerhold.net \
    --to=stephan@gerhold.net \
    --cc=agross@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ilia.lin@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --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