From: "lihuisong (C)" <lihuisong@huawei.com>
To: Sudeep Holla <sudeep.holla@kernel.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
<linux-acpi@vger.kernel.org>, <lihuisong@huawei.com>
Subject: Re: [PATCH 4/6] devfreq: hisi_uncore: Preserve PCC shared memory signature
Date: Mon, 6 Jul 2026 17:15:15 +0800 [thread overview]
Message-ID: <42b67228-ccbd-4272-8ffb-af5fbf6c2083@huawei.com> (raw)
In-Reply-To: <20260702-nondescript-scrupulous-dalmatian-da23be@sudeepholla>
On 7/2/2026 6:25 PM, Sudeep Holla wrote:
> On Sat, Jun 27, 2026 at 05:37:32PM +0100, Sudeep Holla wrote:
>> ACPI specification defines the generic PCC shared memory signature as
>> the PCC base signature ORed with the subspace ID.
>>
>> ACPI 6.6 added clarification that the signature is populated by the
>> platform and verified by OSPM.
>>
>> The PCC mailbox controller now validates the signature when the channel
>> is requested. Stop copying a complete local PCC header into shared
>> memory and write only the command, status and payload fields, leaving
>> the platform-populated signature intact.
>>
> Based on the discussions in 1/6, I assume 4/6 and 5/6 doesn't work well
> for Hisilicon platforms. So I will drop them. I will just post 1/6 reducing
> it to a warning.
Thanks for reducing error level.
We will test them to make sure if these driver work well after removing
the signature filling.
Then will update these code in driver if it's ok.
>
next prev parent reply other threads:[~2026-07-06 9:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-27 16:37 [PATCH 0/6] ACPI/PCC: Preserve platform-populated PCC signatures Sudeep Holla
2026-06-27 16:37 ` [PATCH 1/6] mailbox: pcc: Validate shared memory signature on request Sudeep Holla
2026-06-30 9:02 ` lihuisong (C)
2026-06-30 9:18 ` lihuisong (C)
2026-06-30 10:17 ` Sudeep Holla
2026-06-27 16:37 ` [PATCH 2/6] hwmon: xgene: Stop writing PCC shared memory signature Sudeep Holla
2026-06-29 21:11 ` Guenter Roeck
2026-06-27 16:37 ` [PATCH 3/6] i2c: xgene-slimpro: " Sudeep Holla
2026-06-27 16:37 ` [PATCH 4/6] devfreq: hisi_uncore: Preserve " Sudeep Holla
2026-07-02 10:25 ` Sudeep Holla
2026-07-06 9:15 ` lihuisong (C) [this message]
2026-06-27 16:37 ` [PATCH 5/6] soc: hisilicon: kunpeng_hccs: Preserve PCC signatures Sudeep Holla
2026-06-27 16:37 ` [PATCH 6/6] ACPI: PCC: Preserve shared memory signature in OpRegion handler Sudeep Holla
2026-06-30 12:33 ` Rafael J. Wysocki (Intel)
2026-06-30 17:00 ` Sudeep Holla
2026-07-01 10:44 ` Rafael J. Wysocki (Intel)
2026-07-01 13:34 ` Sudeep Holla
2026-07-01 14:13 ` Sudeep Holla
2026-07-01 14:39 ` Rafael J. Wysocki (Intel)
2026-07-02 12:19 ` Sudeep Holla
2026-06-30 9:25 ` [PATCH 0/6] ACPI/PCC: Preserve platform-populated PCC signatures lihuisong (C)
2026-06-30 10:49 ` Sudeep Holla
2026-07-01 7:38 ` lihuisong (C)
2026-07-02 10:21 ` Sudeep Holla
2026-07-06 9:02 ` lihuisong (C)
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=42b67228-ccbd-4272-8ffb-af5fbf6c2083@huawei.com \
--to=lihuisong@huawei.com \
--cc=cw00.choi@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-acpi@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@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