| Message ID | 20220708014419.2009018-5-bryan.odonoghue@linaro.org (mailing list archive) |
|---|---|
| State | Handled Elsewhere, archived |
| Headers | show |
| Series | msm8939 cpufreq preparatory work | expand |
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 >
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" },
msm8939 will use qcom-cpufreq-nvmem. Block it on the generic cpufreq-dt list. Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org> --- drivers/cpufreq/cpufreq-dt-platdev.c | 1 + 1 file changed, 1 insertion(+)