From: Lukasz Luba <lukasz.luba@arm.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
ye.zhang@rock-chips.com, d-gole@ti.com, rafael@kernel.org,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [STABLE 5.15][PATCH] thermal: devfreq_cooling: Fix perf state when calculate dfc res_util
Date: Fri, 5 Apr 2024 10:34:43 +0100 [thread overview]
Message-ID: <b7733517-4a7e-4314-9a36-3e3cab0df029@arm.com> (raw)
In-Reply-To: <2024040558-defection-shadily-1879@gregkh>
On 4/5/24 10:33, Greg KH wrote:
> On Thu, Apr 04, 2024 at 11:13:29AM +0100, Lukasz Luba wrote:
>> From: Ye Zhang <ye.zhang@rock-chips.com>
>>
>> The issue occurs when the devfreq cooling device uses the EM power model
>> and the get_real_power() callback is provided by the driver.
>>
>> The EM power table is sorted ascending,can't index the table by cooling
>> device state,so convert cooling state to performance state by
>> dfc->max_state - dfc->capped_state.
>>
>> Fixes: 615510fe13bd ("thermal: devfreq_cooling: remove old power model and use EM")
>> Cc: 5.11+ <stable@vger.kernel.org> # 5.11+
>> Signed-off-by: Ye Zhang <ye.zhang@rock-chips.com>
>> Reviewed-by: Dhruva Gole <d-gole@ti.com>
>> Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
>> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>> Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
>> ---
>>
>> Hi Greg,
>>
>> I have solved small backporting conflict to that v5.15.
>> The patch is based on tag v5.15.99 and it's for this
>> failing backport:
>> https://lore.kernel.org/stable/2024033050-imitation-unmixed-ef53@gregkh/
>
> Thanks, next time all that I need is the git id of this in Linus's tree,
> no need to point to a previous FAILED email.
OK, I will remember.
Regards,
Lukasz
prev parent reply other threads:[~2024-04-05 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 10:13 Lukasz Luba
2024-04-05 9:33 ` Greg KH
2024-04-05 9:34 ` Lukasz Luba [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=b7733517-4a7e-4314-9a36-3e3cab0df029@arm.com \
--to=lukasz.luba@arm.com \
--cc=d-gole@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=stable@vger.kernel.org \
--cc=ye.zhang@rock-chips.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®