From: Cristian Marussi <cristian.marussi@arm.com>
To: Sibi Sankar <quic_sibis@quicinc.com>
Cc: sudeep.holla@arm.com, rafael@kernel.org, viresh.kumar@linaro.org,
morten.rasmussen@arm.com, dietmar.eggemann@arm.com,
lukasz.luba@arm.com, 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 V2 1/4] firmware: arm_scmi: Add perf_notify_support interface
Date: Mon, 29 Jan 2024 15:50:15 +0000 [thread overview]
Message-ID: <ZbfJN1c9viiLhO1L@pluto> (raw)
In-Reply-To: <20240117104116.2055349-2-quic_sibis@quicinc.com>
On Wed, Jan 17, 2024 at 04:11:13PM +0530, Sibi Sankar wrote:
> Add a new perf_notify_support interface to the existing perf_ops to export
> info regarding limit/level change notification support.
>
Hi Sibi,
as I mentioned previously, in order not to add a needless stream of SCMI
Perf accessors I posted this:
https://lore.kernel.org/linux-arm-kernel/20240129151002.1215333-1-cristian.marussi@arm.com/T/#u
to expose all the Perf domains infos via the usual info_get(), similarly
to how other SCMI protocols do already.
I think that reworking this series on that, you can certainly drop this patch and just
check the _notify booleans on the retrieved domain info.
Thanks,
Cristian
WARNING: multiple messages have this Message-ID (diff)
From: Cristian Marussi <cristian.marussi@arm.com>
To: Sibi Sankar <quic_sibis@quicinc.com>
Cc: sudeep.holla@arm.com, rafael@kernel.org, viresh.kumar@linaro.org,
morten.rasmussen@arm.com, dietmar.eggemann@arm.com,
lukasz.luba@arm.com, 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 V2 1/4] firmware: arm_scmi: Add perf_notify_support interface
Date: Mon, 29 Jan 2024 15:50:15 +0000 [thread overview]
Message-ID: <ZbfJN1c9viiLhO1L@pluto> (raw)
In-Reply-To: <20240117104116.2055349-2-quic_sibis@quicinc.com>
On Wed, Jan 17, 2024 at 04:11:13PM +0530, Sibi Sankar wrote:
> Add a new perf_notify_support interface to the existing perf_ops to export
> info regarding limit/level change notification support.
>
Hi Sibi,
as I mentioned previously, in order not to add a needless stream of SCMI
Perf accessors I posted this:
https://lore.kernel.org/linux-arm-kernel/20240129151002.1215333-1-cristian.marussi@arm.com/T/#u
to expose all the Perf domains infos via the usual info_get(), similarly
to how other SCMI protocols do already.
I think that reworking this series on that, you can certainly drop this patch and just
check the _notify booleans on the retrieved domain info.
Thanks,
Cristian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-29 15:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 10:41 [PATCH V2 0/4] firmware: arm_scmi: Register and handle limits change notification Sibi Sankar
2024-01-17 10:41 ` Sibi Sankar
2024-01-17 10:41 ` [PATCH V2 1/4] firmware: arm_scmi: Add perf_notify_support interface Sibi Sankar
2024-01-17 10:41 ` Sibi Sankar
2024-01-29 15:50 ` Cristian Marussi [this message]
2024-01-29 15:50 ` Cristian Marussi
2024-01-29 17:33 ` Cristian Marussi
2024-01-29 17:33 ` Cristian Marussi
2024-01-31 11:28 ` Sudeep Holla
2024-01-31 11:28 ` Sudeep Holla
2024-01-31 11:35 ` Cristian Marussi
2024-01-31 11:35 ` Cristian Marussi
2024-02-12 12:44 ` Cristian Marussi
2024-02-12 12:44 ` Cristian Marussi
2024-02-13 5:40 ` Sibi Sankar
2024-02-13 5:40 ` Sibi Sankar
2024-01-17 10:41 ` [PATCH V2 2/4] firmware: arm_scmi: Add perf_freq_xlate interface Sibi Sankar
2024-01-17 10:41 ` Sibi Sankar
2024-01-29 15:53 ` Cristian Marussi
2024-01-29 15:53 ` Cristian Marussi
2024-01-31 11:45 ` Cristian Marussi
2024-01-31 11:45 ` Cristian Marussi
2024-01-17 10:41 ` [PATCH V2 3/4] cpufreq: Export cpufreq_update_pressure Sibi Sankar
2024-01-17 10:41 ` Sibi Sankar
2024-01-17 10:41 ` [PATCH V2 4/4] cpufreq: scmi: Register for limit change notifications Sibi Sankar
2024-01-17 10:41 ` Sibi Sankar
2024-01-29 15:59 ` Cristian Marussi
2024-01-29 15:59 ` Cristian Marussi
2024-02-13 5:42 ` Sibi Sankar
2024-02-13 5:42 ` Sibi Sankar
2024-01-31 14:29 ` Pierre Gondois
2024-01-31 14:29 ` Pierre Gondois
2024-02-13 5:46 ` Sibi Sankar
2024-02-13 5:46 ` Sibi Sankar
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=ZbfJN1c9viiLhO1L@pluto \
--to=cristian.marussi@arm.com \
--cc=dietmar.eggemann@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=lukasz.luba@arm.com \
--cc=morten.rasmussen@arm.com \
--cc=quic_mdtipton@quicinc.com \
--cc=quic_sibis@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.