[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20260129121813.3874516-1-zhangpengjie2@huawei.com>
Date: Thu, 29 Jan 2026 20:18:13 +0800
From: Pengjie Zhang <zhangpengjie2@...wei.com>
To: <rafael@...nel.org>, <viresh.kumar@...aro.org>
CC: <linux-pm@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<zhanjie9@...ilicon.com>, <zhenglifeng1@...wei.com>, <lihuisong@...wei.com>,
<yubowen8@...wei.com>, <linhongye@...artners.com>, <linuxarm@...wei.com>,
<jonathan.cameron@...wei.com>, <zhangpengjie2@...wei.com>,
<wangzhi12@...wei.com>
Subject: [PATCH] cpufreq: Add debug print for current frequency in __cpufreq_driver_target()
Include policy->cur in the debug message to explicitly show the frequency
transition (from current to target).
Signed-off-by: Pengjie Zhang <zhangpengjie2@...wei.com>
---
drivers/cpufreq/cpufreq.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 4472bb1ec83c..b3d2d2e0c864 100644
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
@@ -2361,8 +2361,8 @@ int __cpufreq_driver_target(struct cpufreq_policy *policy,
target_freq = __resolve_freq(policy, target_freq, policy->min,
policy->max, relation);
- pr_debug("target for CPU %u: %u kHz, relation %u, requested %u kHz\n",
- policy->cpu, target_freq, relation, old_target_freq);
+ pr_debug("CPU %u: cur %u kHz -> target %u kHz (req %u kHz, rel %u)\n",
+ policy->cpu, policy->cur, target_freq, old_target_freq, relation);
/*
* This might look like a redundant call as we are checking it again
--
2.33.0
Powered by blists - more mailing lists