public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sibi Sankar <quic_sibis@quicinc.com>
To: Cristian Marussi <cristian.marussi@arm.com>
Cc: <sudeep.holla@arm.com>, <rafael@kernel.org>,
	<viresh.kumar@linaro.org>, <linux-arm-kernel@lists.infradead.org>,
	<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<quic_mdtipton@quicinc.com>, <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH 0/3] firmware: arm_scmi: Register and handle limits change notification
Date: Wed, 17 Jan 2024 17:36:52 +0530	[thread overview]
Message-ID: <674d8057-94b1-2e8a-a3ce-d8719e978298@quicinc.com> (raw)
In-Reply-To: <Zaeg1H9G5jOeOXh2@pluto>



On 1/17/24 15:11, Cristian Marussi wrote:
> On Mon, Jan 08, 2024 at 07:31:15PM +0530, Sibi Sankar wrote:
>> This series registers for scmi limits change notifications and adds
>> perf_notify_support/perf_opp_xlate interfaces which are used by the
>> scmi cpufreq driver to determine the throttled frequency and apply HW
>> pressure.
>>
> 
> Hi,
> 
> a few initial remarks from the mere SCMI standpoint.
> 
> Unlinke most SCMI protocols that expose domains info bits via an
> *info_get protocol operation, PERF does no do this since (till now) there
> wasn't a compelling reason (i.e. users)
> 
> Ulf recently in his GenPD/SCMI series recently started exposing something
> and now you need to expose even more, adding also a new xlate ops.
> 
> For the sake of simplicity, I think that we could now expose straight
> away the whole perf_domain_info and embedded structs via the usual *info_get.
> 
> After having done that, you can just drop your patch 1 and 2 since you
> can access the needed info from the cpufreq_driver right away.
> 
> Having said, I have already such patch ready (for my internal testing), I
> wll post it by the end of week after a minor cleanup, if you can bear with me.
> 
> Thoughts ?

Ack, just from the naming I initially thought info_get would include
everything but it just exposed minimal info. We certainly don't want to
keep adding very similar ops just to expose more such info. I'll re-send
the remainder of the series after you are done with your patches.
Thanks.

-Sibi

> 
> Thanks,
> Cristian

      reply	other threads:[~2024-01-17 12:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 14:01 [PATCH 0/3] firmware: arm_scmi: Register and handle limits change notification Sibi Sankar
2024-01-08 14:01 ` [PATCH 1/3] firmware: arm_scmi: Add perf_notify_support interface Sibi Sankar
2024-01-08 14:01 ` [PATCH 2/3] firmware: arm_scmi: Add perf_opp_xlate interface Sibi Sankar
2024-01-10  7:29   ` Viresh Kumar
2024-01-17  2:59     ` Sibi Sankar
2024-01-08 14:01 ` [PATCH 3/3] cpufreq: scmi: Register for limit change notifications Sibi Sankar
2024-01-10  8:26   ` Lukasz Luba
2024-01-17  2:58     ` Sibi Sankar
2024-01-17  8:03       ` Lukasz Luba
2024-01-17  9:41 ` [PATCH 0/3] firmware: arm_scmi: Register and handle limits change notification Cristian Marussi
2024-01-17 12:06   ` Sibi Sankar [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=674d8057-94b1-2e8a-a3ce-d8719e978298@quicinc.com \
    --to=quic_sibis@quicinc.com \
    --cc=cristian.marussi@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=quic_mdtipton@quicinc.com \
    --cc=rafael@kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=viresh.kumar@linaro.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