Re: [PATCH] cpufreq: Add debug print for current frequency in __cpufreq_driver_target()

[Rafael J. Wysocki]

On Fri, Jan 30, 2026 at 7:27 AM Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote:
>
> On 29-01-26, 20:18, 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@xxxxxxxxxx>
> > ---
> >  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
>
> Acked-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx>

Applied as 7.1 material, thanks!