From: "PierreGondois" <pierre.gondois@arm.com>
To: "Ni, Ray" <ray.ni@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"Gao, Liming" <gaoliming@byosoft.com.cn>,
"Liu, Zhiguang" <zhiguang.liu@intel.com>,
Sami Mujawar <sami.mujawar@arm.com>,
Leif Lindholm <quic_llindhol@quicinc.com>
Subject: Re: [edk2-devel] [PATCH 1/1] MdePkg/IndustryStandard: Add _PSD/_CPC/Coord types definitions
Date: Fri, 1 Dec 2023 13:26:01 +0100 [thread overview]
Message-ID: <25653a17-23ba-4974-bb49-804a238cc90e@arm.com> (raw)
In-Reply-To: <MN6PR11MB82447EA80C59D644403E5CB98C81A@MN6PR11MB8244.namprd11.prod.outlook.com>
Hi Ray,
I followed the way revisions are defined for ACPI tables revisions,
like for the MADT:
EFI_ACPI_x_x_MULTIPLE_APIC_DESCRIPTION_TABLE_REVISION definition
For each ACPI spec. revision, there is a matching MADT revision number.
Sometimes the table has changed and the revision is upgraded, sometimes
not and the revision stays the same.
This also means having a macro definition for each ACPI spec. header
file. I think it should be ok do to the same thing for _PSD/_CPC
revisions,
Regards,
Pierre
On 12/1/23 11:22, Ni, Ray wrote:
>> --- a/MdePkg/Include/IndustryStandard/Acpi50.h
>> +++ b/MdePkg/Include/IndustryStandard/Acpi50.h
>
>> +#define EFI_ACPI_5_0_AML_PSD_REVISION 0
>> +#define EFI_ACPI_5_0_AML_CPC_REVISION 1
>
>
> Do you think it's better to define EFI_ACPI_AML_PSD_REVISION and
> EFI_ACPI_AML_CPC_REVISION in Acpi50.h?
>
> So that Acpi51.h doesn't have to redefine a different macro to
> the same value?
>
>>
>> diff --git a/MdePkg/Include/IndustryStandard/Acpi51.h
>> b/MdePkg/Include/IndustryStandard/Acpi51.h
>> index 01ef544c3a29..19dd7b4f864c 100644
>> --- a/MdePkg/Include/IndustryStandard/Acpi51.h
>> +++ b/MdePkg/Include/IndustryStandard/Acpi51.h
>
>> +#define EFI_ACPI_5_1_AML_PSD_REVISION 0
>> +#define EFI_ACPI_5_1_AML_CPC_REVISION 1
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#111982): https://edk2.groups.io/g/devel/message/111982
Mute This Topic: https://groups.io/mt/102891569/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2023-12-01 12:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 11:09 [edk2-devel] [PATCH 0/1] MdePkg/IndustryStandard: Add _PSD/_CPC/Coord types definitions PierreGondois
2023-11-30 11:09 ` [edk2-devel] [PATCH 1/1] " PierreGondois
2023-12-01 10:22 ` Ni, Ray
2023-12-01 12:26 ` PierreGondois [this message]
2023-12-06 9:42 ` PierreGondois
2023-12-12 0:36 ` 回复: " gaoliming via groups.io
2023-12-22 15:29 ` Sami Mujawar
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-list 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=25653a17-23ba-4974-bb49-804a238cc90e@arm.com \
--to=devel@edk2.groups.io \
/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