Re: [PATCH v15 00/35] Introduce SCMI Telemetry support
From: Cristian Marussi
Date: Wed Nov 18 2026 - 04:15:07 EST
On Tue, Nov 17, 2026 at 05:07:09PM -0800, Jonathan Cameron wrote:
> On Mon, 9 Nov 2026 09:11:46 +0000
> Cristian Marussi <cristian.marussi@xxxxxxx> wrote:
>
> > Hi all,
Hi,
> >
> > [TLDR Summary]
> > [V15 highlights]
> > - general cleanup and hardening driven by reviews
> > - improved TDCF access routines to minimize lost samples under load
> > - completed ABI docs
> >
> > [V16 TODO]
> > - address any remaining V15 outstanding Sashiko/reviewers issues
> >
> > The upcoming SCMI v4.0 specification [0] introduces a new SCMI protocol
> > dedicated to System Telemetry.
>
> This is one from the family of issues you find when reviewing ones own
> (well LLM generated) emulation, realizing it doesn't match the spec,
> and yet works.
>
> This works fine without the required SCMI protocol property in ACPI.
> 2.2.2 of ACPI for System Control and Management Interface 1.0
> Platform Design Document. 111115A 1.0
>
> Now, in here is an informative statement...
>
> Protocols not listed using a property may not be enumerate by the operating system.
>
> But they are...
>
> So, obviously we can ignore informative spec lines but that is a pretty strong
> sentence. I can't immediately think of what would go wrong if we ignored it
> - maybe we'd not pick an exclusive PCC and fallback to a common one the firmware
> doesn't want us to use? But if it doesn't want us to use it why make Telemetry
> discoverable on it.
>
> Should that be wired through from the ACPI parsing code?
>
> Anyhow, not something I care that much about but thought I'd call it out
> as an oddity.
>
AFAICR, I think this is really down to some ambiguity elsewhere in the
ACPI/PCC spec for SCMI, so the implementation deviates a bit from the
behaviour we have on devicetree based SCMI systems where instead a non
DT listed protocol is NOT activated even if provided by FW.
Sudeep has more details on this.
Thanks,
Cristian