From: Lukasz Luba <lukasz.luba@arm.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
dietmar.eggemann@arm.com
Subject: Re: [PATCH v2 1/1] PM: EM: Add min/max available performance state limits
Date: Wed, 30 Oct 2024 10:01:24 +0000 [thread overview]
Message-ID: <61afac10-b434-4e39-8c49-c220add4bd8e@arm.com> (raw)
In-Reply-To: <6cdb2f8b-62e0-455c-a3a5-ed5359a2e941@arm.com>
On 10/30/24 08:48, Lukasz Luba wrote:
> Hi Rafael,
>
> On 10/29/24 18:29, Rafael J. Wysocki wrote:
>> On Tue, Oct 29, 2024 at 10:43 AM Lukasz Luba <lukasz.luba@arm.com> wrote:
>>>
[snip]
>>> +EXPORT_SYMBOL_GPL(em_update_performance_limits);
>>
>> It would be good to have at least one caller of this function in the
>> tree.
>
> Yes, I know, but we had delays with the SCMI cpufreq to get the
> notifications support, which are sent from FW...
>
> The patch using this API was part of v1 but with assumption that
> those SCMI notifications are merged.
>
> The patch v1 for the SCMI cpufreq driver [1].
>
> In that v1 cover letter I mentioned that the 2nd patch depends
> on notifications [2].
>
> I will have to work with Cristian on that notification in SCMI
> then this API will be used. I can see that it stuck for a while
> in v5. Let me sort that out (probably not in this merge window
> though).
Just to link the effort which has been started into that direction:
https://lore.kernel.org/lkml/ab36709d-a181-4621-a8e5-0ef38b80186b@arm.com/
>
> Can we do it this way?
>
> Regards,
> Lukasz
>
> [1]
> https://lore.kernel.org/lkml/20240403162315.1458337-3-lukasz.luba@arm.com/
> [2]
> https://lore.kernel.org/lkml/20240403162315.1458337-1-lukasz.luba@arm.com/
> [3]
> https://lore.kernel.org/lkml/20240603192654.2167620-1-quic_sibis@quicinc.com/
>
next prev parent reply other threads:[~2024-10-30 10:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 9:43 [PATCH v2 0/1] Update Energy Model with performance limits Lukasz Luba
2024-10-29 9:43 ` [PATCH v2 1/1] PM: EM: Add min/max available performance state limits Lukasz Luba
2024-10-29 18:29 ` Rafael J. Wysocki
2024-10-30 8:48 ` Lukasz Luba
2024-10-30 10:01 ` Lukasz Luba [this message]
2024-10-30 11:23 ` Rafael J. Wysocki
2024-10-30 11:34 ` Lukasz Luba
2024-10-30 11:41 ` Rafael J. Wysocki
2024-10-30 11:40 ` Rafael J. Wysocki
2024-10-30 11:50 ` Lukasz Luba
2024-10-30 13:18 ` Rafael J. Wysocki
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=61afac10-b434-4e39-8c49-c220add4bd8e@arm.com \
--to=lukasz.luba@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
/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