From: Sudeep Holla <sudeep.holla@kernel.org>
To: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
Cc: arm-scmi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kernel-team@meta.com, Cristian Marussi <cristian.marussi@arm.com>,
Sudeep Holla <sudeep.holla@kernel.org>,
Breno Leitao <leitao@debian.org>
Subject: Re: [PATCH v3 7/9] firmware: arm_scmi: Add ACPI PCC transport
Date: Thu, 3 Sep 2026 14:43:46 +0100 [thread overview]
Message-ID: <20260903-hairy-hospitable-sambar-7a3ea0@sudeepholla> (raw)
In-Reply-To: <20260824131709.00006712@oss.qualcomm.com>
On Mon, Aug 24, 2026 at 01:17:09PM -0700, Jonathan Cameron wrote:
> On Thu, 13 Aug 2026 12:33:02 +0100
> Sudeep Holla <sudeep.holla@kernel.org> wrote:
>
> > Introduce a new SCMI transport that uses ACPI PCCT (PCC) subspaces via
> > the Linux PCC mailbox layer. Parse ACPI _DSD data to map protocol
> > associations to PCC transport UIDs. Support common and
> > protocol-exclusive A2P channels, plus optional common or
> > protocol-exclusive P2A channels for notifications.
> >
> > Key points:
> > - new CONFIG_ARM_SCMI_TRANSPORT_PCC option
> > - integration with SCMI core via scmi_desc and transport ops
> > - response and notification fetch from PCC shared memory
> > - ACPI device matching and registration via the ACPI transport macro
> >
> > This enables SCMI to be exercised over PCC on ACPI platforms.
> >
> > Signed-off-by: Sudeep Holla <sudeep.holla@kernel.org>
> Hi Sudeep
>
> This is quite dense and ACPI parsing code is always 'interesting'
> Anyhow some comments inline
>
Indeed quite dense to even parse the comments. It could be my brain which
is still recovering from the flu, but I can't respond to them inline. I
think I have taken most of the suggestions(saying most as I might have
missed unintentionally). I might have gone overboard with some macros to
eliminate random magic offsets. I will post v4 soon.
Thanks again for all the review comments. I am still debating if I need
to break this into 2 patches(technically yes, motivationally not yet 😄)
--
Regards,
Sudeep
next prev parent reply other threads:[~2026-09-03 13:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 11:32 [PATCH v3 0/9] firmware: arm_scmi: Refactoring and enablement of ACPI PCC transport Sudeep Holla
2026-08-13 11:32 ` [PATCH v3 1/9] firmware: arm_scmi: Set fwnode for the generated SCMI platform device Sudeep Holla
2026-08-24 16:51 ` Jonathan Cameron
2026-09-02 7:51 ` Sudeep Holla
2026-09-02 23:26 ` Jonathan Cameron
2026-09-03 9:16 ` Bartosz Golaszewski
2026-08-13 11:32 ` [PATCH v3 2/9] firmware: arm_scmi: Extend transport driver macro to support ACPI Sudeep Holla
2026-08-24 17:04 ` Jonathan Cameron
2026-09-02 7:53 ` Sudeep Holla
2026-08-13 11:32 ` [PATCH v3 3/9] firmware: arm_scmi: Convert OF-only paths to generic fwnode in SCMI core Sudeep Holla
2026-08-24 17:39 ` Jonathan Cameron
2026-09-02 13:39 ` Sudeep Holla
2026-09-02 23:29 ` Jonathan Cameron
2026-09-03 6:36 ` Sudeep Holla
2026-08-13 11:32 ` [PATCH v3 4/9] firmware: arm_scmi: Fall back to ACPI HID when "compatible" is absent Sudeep Holla
2026-08-24 17:43 ` Jonathan Cameron
2026-09-02 8:03 ` Sudeep Holla
2026-09-02 8:09 ` Sudeep Holla
2026-08-13 11:33 ` [PATCH v3 5/9] firmware: arm_scmi: Pass protocol ID to chan_available() transport callback Sudeep Holla
2026-08-24 17:45 ` Jonathan Cameron
2026-08-13 11:33 ` [PATCH v3 6/9] firmware: arm_scmi: Refactor protocol device creation logic Sudeep Holla
2026-08-24 17:49 ` Jonathan Cameron
2026-09-02 13:52 ` Sudeep Holla
2026-08-13 11:33 ` [PATCH v3 7/9] firmware: arm_scmi: Add ACPI PCC transport Sudeep Holla
2026-08-24 20:17 ` Jonathan Cameron
2026-09-03 13:43 ` Sudeep Holla [this message]
2026-08-13 11:33 ` [PATCH v3 8/9] firmware: arm_scmi: Initialise known ACPI protocol devices and channels Sudeep Holla
2026-08-24 20:21 ` Jonathan Cameron
2026-08-13 11:33 ` [PATCH v3 9/9] firmware: arm_scmi: Validate PCC shared memory signature Sudeep Holla
2026-08-24 20:24 ` Jonathan Cameron
2026-09-02 8:25 ` Sudeep Holla
2026-09-02 23:31 ` Jonathan Cameron
2026-09-03 6:39 ` Sudeep Holla
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=20260903-hairy-hospitable-sambar-7a3ea0@sudeepholla \
--to=sudeep.holla@kernel.org \
--cc=arm-scmi@vger.kernel.org \
--cc=cristian.marussi@arm.com \
--cc=jonathan.cameron@oss.qualcomm.com \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).