1)
During power initialization the pstate cpufreq api is
not setting the initial curr_idx of pstate_power_info
to corresponding current frequency index.
Without this the idx is always 0, which is causing the
below check to pass and returns without setting the initial
min/max frequency to system ma
Hi Reshma,
I'm OK with the change. That's the missing part about init process.
Reviewed-by Liang Ma
Regards
Liang
On 29 Jul 14:58, Reshma Pattan wrote:
> 1)
> During power initialization the pstate cpufreq api is
> not setting the initial curr_idx of pstate_power_info
> to corresponding cu
31/07/2020 11:32, Liang, Ma:
> Hi Reshma,
>
>I'm OK with the change. That's the missing part about init process.
>
> Reviewed-by Liang Ma
Because of a missing colon, this review was not counted in patchwork.
I guess Dave is OK with this patch but he was not Cc'ed.
Please use --cc-cmd devt
3 matches
Mail list logo
