From: Sudeep Holla <sudeep.holla@arm.com>
To: "Pawandeep Oza (QUIC)" <quic_poza@quicinc.com>
Cc: "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: Tue, 29 Aug 2023 10:19:12 +0100 [thread overview]
Message-ID: <20230829091912.xefuenspdbazvqlh@bogus> (raw)
In-Reply-To: <CH0PR02MB80732F4C4134B3EF2D80B4EDF6E3A@CH0PR02MB8073.namprd02.prod.outlook.com>
On Fri, Aug 25, 2023 at 09:34:59PM +0000, Pawandeep Oza (QUIC) wrote:
[...]
>
> But I still fail to see how fastchannel doorbell and shared memory space
> could get bind to PCC space (type 3) ? I am on 6.3 kernel.
They simply don't bind to PCC, PCC can't be fast channel. What exactly are you
looking for here ? If you provide more details on that, I can see if I can
help or suggest or may be explore along with you if the solution doesn't
exists yet.
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-29 9:19 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 ` Sudeep Holla [this message]
2023-08-29 15:10 ` ACPI binding with SCMI Pawandeep Oza
2023-08-30 9:13 ` 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=20230829091912.xefuenspdbazvqlh@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=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