From: Sudeep Holla <sudeep.holla@arm.com>
To: Pawandeep Oza <poza@qti.qualcomm.com>
Cc: "Pawandeep Oza (QUIC)" <quic_poza@quicinc.com>,
"rafael@kernel.org" <rafael@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: ACPI binding with SCMI
Date: Wed, 30 Aug 2023 10:13:37 +0100 [thread overview]
Message-ID: <20230830091337.4rsik2tza6hqa22r@bogus> (raw)
In-Reply-To: <CH0PR02MB807367CCAD0D5938C4679E18F6E7A@CH0PR02MB8073.namprd02.prod.outlook.com>
On Tue, Aug 29, 2023 at 03:10:34PM +0000, Pawandeep Oza wrote:
> I am looking for scmi binding to ACPI. Basically, SCMI based perf control.
> We have ACPI based system, so I am looking for where I can describe (some
> way to describe doorbell and share memory in ACPI), and then scmi perf can
> bind to it via some sort of transport (perhaps fastchannels ? )
OK, the Section 5.2 ACPI-based Transport in the SCMI spec can be more clearer
IMO. It does state:
" SCMI FastChannels can be represented as ACPI System Memory and used
in the Continuous Performance Control (CPC) object when using ACPI
Collaborative Processor Performance Control (CPPC)."
It doesn't cover the fact that CPPC is compatible only with SCMI fastchannels
without doorbells. Just a plain MMIO register to set the perf.
The normal PCC mailbox works fine if the CPPC Desired Perf Register is
a PCC address space based GAS. However the command is not 1:1 compatible
with SCMI perf. This is one of the reason why the protocols 0x0-0xF was
reserved in SCMI to be compatible with the ACPI CPPC way of using PCC
for perf.
Hope this helps and I didn't make it more complicated for you.
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-08-30 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 15:48 [PATCH v2] cpuidle, ACPI: Evaluate LPI arch_flags for broadcast timer Oza Pawandeep
2023-08-17 17:49 ` Rafael J. Wysocki
2023-08-18 9:19 ` Sudeep Holla
[not found] ` <CH0PR02MB80732F4C4134B3EF2D80B4EDF6E3A@CH0PR02MB8073.namprd02.prod.outlook.com>
2023-08-29 9:19 ` ACPI binding with SCMI Sudeep Holla
2023-08-29 15:10 ` Pawandeep Oza
2023-08-30 9:13 ` Sudeep Holla [this message]
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=20230830091337.4rsik2tza6hqa22r@bogus \
--to=sudeep.holla@arm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=poza@qti.qualcomm.com \
--cc=quic_poza@quicinc.com \
--cc=rafael@kernel.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