From: "zhangpengjie (A)" <zhangpengjie2@huawei.com>
To: <rafael@kernel.org>
Cc: <linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<zhanjie9@hisilicon.com>, <zhenglifeng1@huawei.com>,
<lihuisong@huawei.com>, <yubowen8@huawei.com>,
<linhongye@h-partners.com>, <linuxarm@huawei.com>,
<jonathan.cameron@huawei.com>, <wangzhi12@huawei.com>,
<viresh.kumar@linaro.org>
Subject: Re: [PATCH] cpufreq: Add debug print for current frequency in __cpufreq_driver_target()
Date: Tue, 3 Mar 2026 19:48:29 +0800 [thread overview]
Message-ID: <a169bf69-b72f-4a95-85e3-569da22a2837@huawei.com> (raw)
In-Reply-To: <20260129121813.3874516-1-zhangpengjie2@huawei.com>
Can it be applied, please?
Best Regards,
Pengjie Zhang
On 1/29/2026 8:18 PM, Pengjie Zhang wrote:
> Include policy->cur in the debug message to explicitly show the frequency
> transition (from current to target).
>
> Signed-off-by: Pengjie Zhang <zhangpengjie2@huawei.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
prev parent reply other threads:[~2026-03-03 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 12:18 Pengjie Zhang
2026-01-30 6:27 ` Viresh Kumar
2026-03-05 14:47 ` Rafael J. Wysocki
2026-03-03 11:48 ` zhangpengjie (A) [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=a169bf69-b72f-4a95-85e3-569da22a2837@huawei.com \
--to=zhangpengjie2@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=lihuisong@huawei.com \
--cc=linhongye@h-partners.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=wangzhi12@huawei.com \
--cc=yubowen8@huawei.com \
--cc=zhanjie9@hisilicon.com \
--cc=zhenglifeng1@huawei.com \
/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®