Re: [PATCH v2] cpufreq/cppc: Take policy->cur into judge when set target

[Viresh Kumar]

On 29-05-24, 14:53, Riwen Lu wrote:
> Yes, you are right， I didn't think it through. In this circumstance, the
> policy->cur is the highest frequency, desired_perf converted from
> target_freq is the same with cpu_data->perf_ctrls.desired_perf which
> shouldn't.

Please investigate more and see where the real problem is.

-- 
viresh