From: Punit Agrawal <punit.agrawal@oss.qualcomm.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
arm-scmi@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/8] firmware: arm_scmi: Refactoring and enablement of ACPI PCC transport
Date: Wed, 05 Nov 2025 11:49:38 +0000 [thread overview]
Message-ID: <87wm44aect.fsf@stealth> (raw)
In-Reply-To: <20251017-acpi_scmi_pcc-v1-0-0adbab7709d9@arm.com> (Sudeep Holla's message of "Fri, 17 Oct 2025 14:23:43 +0100")
Hi Sudeep,
Sudeep Holla <sudeep.holla@arm.com> writes:
> The SCMI can be utilized in systems using either the FDT or ACPI specification.
> While FDT-based systems can natively use SCMI, ACPI-based systems often
> need to abstract the functionality provided by SCMI under ASL methods.
> So far, there has been no need to support SCMI natively on ACPI systems.
>
> However, with the addition of a few new protocols such as Powercap and Telemetry,
> which lack abstractions in the ACPI specification, there is now a need to
> run SCMI natively for those use cases.
>
> This patch series introduces ACPI PCC transport support for the Arm SCMI
> framework, alongside several foundational refactors and enhancements to
> achieve firmware-node neutrality between Device Tree (DT) and ACPI systems.
>
> The key changes include:
>
> 1. ACPI/DT abstraction and fwnode transition
>
> Converted the core SCMI code to use `fwnode_handle` instead of DT-specific
> structures, ensuring seamless operation across both ACPI and DT
> environments. All property lookups, child enumeration, and device
> association paths have been updated accordingly.
>
> 2. Unified transport registration for ACPI and DT
>
> Extended the SCMI transport driver macros to support ACPI match tables,
> enabling transports to probe using ACPI device IDs while maintaining
> backward compatibility with DT-only systems.
>
> 3. Protocol device initialization and refactoring
>
> Refactored the protocol device creation and validation logic into a new
> helper for improved readability and maintainability. Enhanced the
> initialization logic to handle ACPI-based SCMI devices without explicit
> child fwnodes.
>
> 4. Introduction of ACPI PCC transport
>
> Added a new SCMI transport driver leveraging ACPI PCCT (Platform
> Communications Channel Table) subspaces via the Linux PCC mailbox
> framework. This enables SCMI communication over PCC on ACPI-based
> platforms.
>
> Collectively, these changes lay the groundwork for robust SCMI operation on
> ACPI platforms, achieving near parity with DT systems where applicable,
> while enabling the new PCC transport path for firmware communication.
I was interested in taking a closer look at the patches here but they
have a dependency on support for the telemetry protocol patches. I get a
compile error.
I was wondering if you have a branch with the dependencies included. Are
the v1 telemetry support patches[0] the right version to be using?
Thanks,
Punit
[0] https://lore.kernel.org/all/20250925203554.482371-1-cristian.marussi@arm.com/
[...]
next prev parent reply other threads:[~2025-11-05 11:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 13:23 [PATCH 0/8] firmware: arm_scmi: Refactoring and enablement of ACPI PCC transport Sudeep Holla
2025-10-17 13:23 ` [PATCH 1/8] firmware: arm_scmi: Set fwnode for the genrated SCMI platform device Sudeep Holla
2025-10-20 17:07 ` Jonathan Cameron
2025-10-21 9:03 ` Sudeep Holla
2025-10-17 13:23 ` [PATCH 2/8] firmware: arm_scmi: Extend transport driver macro to support ACPI Sudeep Holla
2025-10-20 17:11 ` Jonathan Cameron
2025-10-21 9:06 ` Sudeep Holla
2025-10-17 13:23 ` [PATCH 3/8] firmware: arm_scmi: Convert OF-only paths to generic fwnode in SCMI core Sudeep Holla
2025-10-20 17:29 ` Jonathan Cameron
2025-10-21 9:26 ` Sudeep Holla
2025-10-17 13:23 ` [PATCH 4/8] firmware: arm_scmi: Fall back to ACPI HID when "compatible" is absent Sudeep Holla
2025-10-17 13:23 ` [PATCH 5/8] firmware: arm_scmi: Pass protocol ID to chan_available() transport callback Sudeep Holla
2025-10-17 13:23 ` [PATCH 6/8] firmware: arm_scmi: Refactor protocol device creation logic Sudeep Holla
2025-10-17 13:23 ` [PATCH 7/8] firmware: arm_scmi: transport: Add ACPI PCC transport Sudeep Holla
2025-10-20 8:20 ` Dan Carpenter
2025-10-20 8:47 ` Sudeep Holla
2025-10-20 17:37 ` Jonathan Cameron
2025-10-21 9:30 ` Sudeep Holla
2025-10-17 13:23 ` [PATCH 8/8] firmware: arm_scmi: Initialise all protocol devices and transport channels Sudeep Holla
2025-11-05 11:49 ` Punit Agrawal [this message]
2025-11-26 14:31 ` [PATCH 0/8] firmware: arm_scmi: Refactoring and enablement of ACPI PCC transport Sudeep Holla
2025-12-03 11:04 ` Punit Agrawal
2025-12-03 15:21 ` Sudeep Holla
2025-12-04 18:25 ` Punit Agrawal
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=87wm44aect.fsf@stealth \
--to=punit.agrawal@oss.qualcomm.com \
--cc=arm-scmi@vger.kernel.org \
--cc=cristian.marussi@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sudeep.holla@arm.com \
/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;
as well as URLs for NNTP newsgroup(s).