[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <cfc4914d-a8e7-49ba-a5d5-7ebfa62fd0a2@oss.qualcomm.com>
Date: Tue, 13 Jan 2026 11:54:36 +0100
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: Konrad Dybcio <konradybcio@...nel.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Viresh Kumar <viresh.kumar@...aro.org>
Cc: Bjorn Andersson <bjorn.andersson@....qualcomm.com>,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH] cpufreq: dt-platdev: Block the driver from probing on
more QC platforms
On 1/13/26 11:53 AM, Konrad Dybcio wrote:
> From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
>
> Add a number of QC platforms to the blocklist, they all use either the
> qcom-cpufreq-hw or scmi-cpufreq drivers.
>
> Signed-off-by: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
> ---
> Note: the "qcom,glymur" compatible is not in -next, but is already
> approved by krzk and should be merged shortly
Scratch that, immediately after pressing enter I realized the ones
using cpufreq-scmi won't even have an OPP table attached to the CPUs
I'll send a v2..
Konrad
Powered by blists - more mailing lists