From: Oleg Keri <okerixx@gmail.com>
To: Dietmar Eggemann <dietmar.eggemann@arm.com>
Cc: Ananthu C V <ananthu.cv@oss.qualcomm.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Beata Michalska <beata.michalska@arm.com>,
Sudeep Holla <sudeep.holla@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] arch_topology: use the boost frequencies for capacity_freq_ref
Date: Thu, 17 Sep 2026 17:38:47 +0200 [thread overview]
Message-ID: <178965952769.2757.5034972953349001664@gmail.com> (raw)
In-Reply-To: <bddc9273-fe02-4984-bfe9-5078e9e6e111@arm.com>
Hi Dietmar,
On Thu, Sep 17, 2026, Dietmar Eggemann wrote:
> Ah, you want to fix this for 'frequency table' drivers.
>
> IMHO,
> https://lore.kernel.org/r/20260908-schedutil-boost-frequency-handling-v2-0-25312a713699@oss.qualcomm.com
> is trying the same at the moment.
Thanks, I had missed that series. Please drop my 2/2 in favour of it.
Patch 1/2 here is still needed, and becomes a prerequisite for his series
on this SoC: with the reference at 4723200 kHz from boot,
arch_freq_get_on_cpu() wraps and cpuinfo_avg_freq reads about 524283 kHz
unless the multiply stays in 64 bits.
I will test his series on the Yoga Slim 7x Gen 11 and reply there.
Thanks,
Oleg
prev parent reply other threads:[~2026-09-17 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 12:51 [PATCH v4 0/2] arm64/cpufreq: report and track frequencies above 4.19 GHz Oleg Keri
2026-09-17 12:51 ` [PATCH v4 1/2] arm64: topology: fix arch_freq_get_on_cpu() overflow " Oleg Keri
2026-09-17 15:32 ` Peter Zijlstra
2026-09-17 15:55 ` Dietmar Eggemann
2026-09-17 16:24 ` Peter Zijlstra
2026-09-17 12:51 ` [PATCH v4 2/2] arch_topology: use the boost frequencies for capacity_freq_ref Oleg Keri
2026-09-17 14:34 ` Dietmar Eggemann
2026-09-17 15:38 ` Oleg Keri [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=178965952769.2757.5034972953349001664@gmail.com \
--to=okerixx@gmail.com \
--cc=ananthu.cv@oss.qualcomm.com \
--cc=beata.michalska@arm.com \
--cc=catalin.marinas@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=will@kernel.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
all inboxes | Powered by JetHome®