[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKfTPtByDJxQEdBwYkpj1G=sgm8FOw4FS17yMbEbz=on95TP9g@mail.gmail.com>
Date: Wed, 31 Jan 2024 15:55:06 +0100
From: Vincent Guittot <vincent.guittot@...aro.org>
To: Erico Nunes <nunes.erico@...il.com>
Cc: mingo@...hat.com, peterz@...radead.org, juri.lelli@...hat.com,
dietmar.eggemann@....com, rostedt@...dmis.org, bsegall@...gle.com,
mgorman@...e.de, bristot@...hat.com, vschneid@...hat.com,
sudeep.holla@....com, gregkh@...uxfoundation.org, rafael@...nel.org,
linux-kernel@...r.kernel.org, lukasz.luba@....com, ionela.voinescu@....com
Subject: Re: [Resend PATCH] topology: Set capacity_freq_ref in all cases
On Wed, 31 Jan 2024 at 14:56, Erico Nunes <nunes.erico@...il.com> wrote:
>
> On Wed, Jan 17, 2024 at 8:06 PM Vincent Guittot
> <vincent.guittot@...aro.org> wrote:
> >
> > If "capacity-dmips-mhz" is not set, raw_capacity is null and we skip the
> > normalization step which includes setting per_cpu capacity_freq_ref.
> > Always register the notifier but skip the capacity normalization if
> > raw_capacity is null.
>
> I bisected an issue of cpufreq no longer working on v6.8-rc on a TI
> SK-AM62 board and it pointed me to b3edde44e5d4 ("cpufreq/schedutil:
> Use a fixed reference frequency").
> This commit does fix the issue but doesn't appear to be merged
> anywhere yet. It would be good to have this fixed before 6.8 release.
Greg has queued the patch which should show up in the next release of
the linux-next tree
>
> Tested-by: Erico Nunes <nunes.erico@...il.com>
Powered by blists - more mailing lists