summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGeert Uytterhoeven <geert+renesas@glider.be>2026-01-15 09:51:45 +0100
committerWill Deacon <will@kernel.org>2026-01-22 11:18:41 +0000
commit747d5b6735caa0178b3f1c922cfa9c285b093f22 (patch)
treed7ee73b7fa8738993c9ee5199390c550f2517d5a
parent6fd9be0b7b2e957d24b0490b989658c4d18d92c7 (diff)
arm64: topology: Do not warn on missing AMU in cpuhp_topology_online()
When CONFIG_CPUMASK_OFFSTACK is not enabled, and resuming from s2ram on Renesas R-Car H3 (big.LITTLE 4x Cortex-A57 + 4x Cortex-A53), during enabling of the first little core, a warning message is printed: AMU: CPU[4] doesn't support AMU counters This confuses users, as during boot amu_fie_setup() does not print such a message, unless debugging is enabled (freq_counters_valid() prints "CPU%d: counters are not supported.\n" at debug level in that case). Hence drop the warning, freq_counters_valid() has already printed a debug message anyway. Fixes: 6fd9be0b7b2e ("arm64: topology: Handle AMU FIE setup on CPU hotplug") Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> Reviewed-by: Lifeng Zheng <zhenglifeng1@huawei.com> Signed-off-by: Will Deacon <will@kernel.org>
-rw-r--r--arch/arm64/kernel/topology.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/arch/arm64/kernel/topology.c b/arch/arm64/kernel/topology.c
index 539b38935182..3fe1faab0362 100644
--- a/arch/arm64/kernel/topology.c
+++ b/arch/arm64/kernel/topology.c
@@ -332,7 +332,6 @@ static int cpuhp_topology_online(unsigned int cpu)
* may use different source of the freq scale.
*/
if (!freq_counters_valid(cpu)) {
- pr_warn("CPU[%u] doesn't support AMU counters\n", cpu);
topology_clear_scale_freq_source(SCALE_FREQ_SOURCE_ARCH,
policy->related_cpus);
cpumask_andnot(amu_fie_cpus, amu_fie_cpus, policy->related_cpus);