Linux Documentation
 help / color / mirror / Atom feed
From: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
To: Cristian Marussi <cristian.marussi@arm.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, arm-scmi@vger.kernel.org,
	linux-doc@vger.kernel.org, sudeep.holla@kernel.org,
	james.quinlan@broadcom.com, f.fainelli@gmail.com,
	vincent.guittot@linaro.org, etienne.carriere@st.com,
	peng.fan@oss.nxp.com, michal.simek@amd.com, d-gole@ti.com,
	jic23@kernel.org, elif.topuz@arm.com, lukasz.luba@arm.com,
	philip.radford@arm.com, david@kernel.org,
	souvik.chakravarty@arm.com, leitao@kernel.org, kas@kernel.org,
	puranjay@kernel.org, usama.arif@linux.dev, kernel-team@meta.com
Subject: Re: [PATCH v10 03/24] firmware: arm_scmi: Introduce protocol instance notifiers
Date: Mon, 24 Aug 2026 13:35:06 -0700	[thread overview]
Message-ID: <20260824133506.000053ed@oss.qualcomm.com> (raw)
In-Reply-To: <20260815232604.3730754-4-cristian.marussi@arm.com>

On Sun, 16 Aug 2026 00:25:43 +0100
Cristian Marussi <cristian.marussi@arm.com> wrote:

> SCMI Protocol notifications are typically used by SCMI drivers to detect
> and react to particular conditions: this was the assumption and the classic
> usage scenario upon which the SCMI notification framework was built.
> 
> Some protocols like Telemetry, though, could be interested in enabling and
> registering for such notifications: in such a scenario each initialized
> protocol instance could want to register a common protocol notifier.
> 
> In order to reuse the existing SCMI Notifications machinery, allow
> protocols themselves to register for their own notifications and provide
> their own notifier callbacks.
> 
> Each protocol, at the end of its initialization phase, can now provide one
> unique per-protocol-instance notifier block, which will be registered, by
> the core SCMI stack, on the related notification chain: such notifier will
> be automatically removed during the protocol de-initialization phase.
> 
> Signed-off-by: Cristian Marussi <cristian.marussi@arm.com>
I skipped a few versions but what you have now looks good to me.
Reviewed-by: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>

  reply	other threads:[~2026-08-24 20:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-15 23:25 [PATCH v10 00/24] Introduce SCMI Telemetry support Cristian Marussi
2026-08-15 23:25 ` [PATCH v10 01/24] firmware: arm_scmi: Add new SCMIv4.0 error codes definitions Cristian Marussi
2026-08-15 23:25 ` [PATCH v10 02/24] firmware: arm_scmi: Allow registration of unknown-size events/reports Cristian Marussi
2026-08-15 23:25 ` [PATCH v10 03/24] firmware: arm_scmi: Introduce protocol instance notifiers Cristian Marussi
2026-08-24 20:35   ` Jonathan Cameron [this message]
2026-08-15 23:25 ` [PATCH v10 04/24] dt-bindings: firmware: arm,scmi: Add support for telemetry protocol Cristian Marussi
2026-08-15 23:25 ` [PATCH v10 05/24] include: trace: Add Telemetry trace events Cristian Marussi
2026-08-15 23:25 ` [PATCH v10 06/24] firmware: arm_scmi: Add basic Telemetry support Cristian Marussi
2026-08-24 21:04   ` Jonathan Cameron
2026-08-15 23:25 ` [PATCH v10 07/24] firmware: arm_scmi: Add support to parse SHMTIs areas Cristian Marussi
2026-08-15 23:25 ` [PATCH v10 08/24] firmware: arm_scmi: Add Telemetry configuration operations Cristian Marussi
2026-08-15 23:25 ` [PATCH v10 09/24] firmware: arm_scmi: Add Telemetry DataEvent read capabilities Cristian Marussi
2026-08-15 23:25 ` [PATCH v10 10/24] firmware: arm_scmi: Add support for Telemetry reset Cristian Marussi
2026-08-15 23:25 ` [PATCH v10 11/24] firmware: arm_scmi: Add Telemetry notification support Cristian Marussi
2026-08-15 23:25 ` [PATCH v10 12/24] firmware: arm_scmi: Add support for boot-on Telemetry Cristian Marussi
2026-08-15 23:25 ` [PATCH v10 13/24] firmware: arm-scmi: Add telemetry generic event support Cristian Marussi
2026-08-15 23:25 ` [PATCH v10 14/24] firmware: arm_scmi: Add Telemetry generation counter event Cristian Marussi
2026-08-15 23:25 ` [PATCH v10 15/24] firmware: arm_scmi: Add common per-protocol debugfs support Cristian Marussi
2026-08-15 23:25 ` [PATCH v10 16/24] firmware: arm_scmi: Add Telemetry debugfs SHMTI dump support Cristian Marussi
2026-08-15 23:25 ` [PATCH v10 17/24] firmware: arm_scmi: Add Telemetry debugfs ABI documentation Cristian Marussi
2026-08-15 23:25 ` [PATCH v10 18/24] firmware: arm_scmi: Expose per-instance identifier Cristian Marussi
2026-08-15 23:25 ` [PATCH v10 19/24] firmware: arm_scmi: Add un-managed methods to get/put protocols operations Cristian Marussi
2026-08-15 23:26 ` [PATCH v10 20/24] uapi: Add ARM SCMI Telemetry definitions Cristian Marussi
2026-08-15 23:26 ` [PATCH v10 21/24] firmware: arm_scmi: Add System Telemetry driver Cristian Marussi
2026-08-15 23:26 ` [PATCH v10 22/24] docs: ioctl-number: Add SCMI Ioctls Cristian Marussi
2026-08-15 23:26 ` [PATCH v10 23/24] [RFC] Documentation: Add SCMI System Telemetry documentation Cristian Marussi
2026-08-15 23:26 ` [PATCH v10 24/24] [RFC] tools/scmi: Add SCMI Telemetry testing tool Cristian Marussi

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=20260824133506.000053ed@oss.qualcomm.com \
    --to=jonathan.cameron@oss.qualcomm.com \
    --cc=arm-scmi@vger.kernel.org \
    --cc=cristian.marussi@arm.com \
    --cc=d-gole@ti.com \
    --cc=david@kernel.org \
    --cc=elif.topuz@arm.com \
    --cc=etienne.carriere@st.com \
    --cc=f.fainelli@gmail.com \
    --cc=james.quinlan@broadcom.com \
    --cc=jic23@kernel.org \
    --cc=kas@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=leitao@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=michal.simek@amd.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=philip.radford@arm.com \
    --cc=puranjay@kernel.org \
    --cc=souvik.chakravarty@arm.com \
    --cc=sudeep.holla@kernel.org \
    --cc=usama.arif@linux.dev \
    --cc=vincent.guittot@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