[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <086e7186-7c41-5e39-4f6a-e1b44f63b867@arm.com>
Date: Fri, 15 Oct 2021 13:13:06 +0100
From: Lukasz Luba <lukasz.luba@....com>
To: Thara Gopinath <thara.gopinath@...aro.org>
Cc: linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-arm-msm@...r.kernel.org, sudeep.holla@....com,
will@...nel.org, catalin.marinas@....com, linux@...linux.org.uk,
gregkh@...uxfoundation.org, rafael@...nel.org,
viresh.kumar@...aro.org, amitk@...nel.org,
daniel.lezcano@...aro.org, amit.kachhap@...il.com,
bjorn.andersson@...aro.org, agross@...nel.org
Subject: Re: [PATCH 1/5] arch_topology: Introduce thermal pressure update
function
Hi Thara,
Thank you having a look at these patches.
My apologies for the delay, I haven't felt well
recently.
On 10/11/21 10:15 PM, Thara Gopinath wrote:
>
>
> On 10/7/21 4:07 AM, Lukasz Luba wrote:
[snip]
>> +/**
>> + * topology_thermal_pressure_update() - Update thermal pressure for CPUs
>> + * @cpus : The related CPUs which capacity has been reduced
>
> The related CPUs "for" which
thanks
>
>> + * @capped_freq : The maximum allowed frequency that CPUs can run at
[snip]
>> +
>> + capacity = capped_freq * max_capacity;
>> + capacity /= per_cpu(freq_factor, cpu);
>
> use mult_frac as used in other implementations ?
>
Good point. Let me check that. In that arch_topology file we never
use such trick, but in this case it makes sense IMO.
Regards,
Lukasz
Powered by blists - more mailing lists