[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YLUpE6NK3WC+Nu2S@builder.lan>
Date: Mon, 31 May 2021 13:21:07 -0500
From: Bjorn Andersson <bjorn.andersson@...aro.org>
To: Sibi Sankar <sibis@...eaurora.org>
Cc: Viresh Kumar <viresh.kumar@...aro.org>, dianders@...omium.org,
mka@...omium.org, sboyd@...nel.org, agross@...nel.org,
robh+dt@...nel.org, rjw@...ysocki.net,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: [PATCH v3 1/2] cpufreq: blacklist SC7280 in cpufreq-dt-platdev
On Thu 20 May 02:20 CDT 2021, Sibi Sankar wrote:
> On 2021-05-20 09:26, Viresh Kumar wrote:
> > On 12-05-21, 13:41, Sibi Sankar wrote:
> > > Add SC7280 to cpufreq-dt-platdev blacklist since the actual scaling is
> > > handled by the 'qcom-cpufreq-hw' driver.
> > >
> > > Reviewed-by: Douglas Anderson <dianders@...omium.org>
> > > Signed-off-by: Sibi Sankar <sibis@...eaurora.org>
> > > ---
> > > 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 5e07065ec22f..345418b8250e 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 blacklist[]
> > > __initconst = {
> > > { .compatible = "qcom,msm8996", },
> > > { .compatible = "qcom,qcs404", },
> > > { .compatible = "qcom,sc7180", },
> > > + { .compatible = "qcom,sc7280", },
> > > { .compatible = "qcom,sdm845", },
> > >
> > > { .compatible = "st,stih407", },
> >
> > Applied 1/2. Thanks.
> >
> > What do you want to do for 2/2 ? Go through my tree? need an update ?
>
> Lets skip pulling in 2/2 for now.
In particular it's ripe for merge conflicts, so I'd prefer to take it
through my tree.
> It depends on a few other changes to land first and the cpufreq node
> for sc7280 needs a re-spin.
What other dependencies do we have?
I dropped the reg-names from the cpufreq node and merged that change.
Regards,
Bjorn
Powered by blists - more mailing lists