From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <swatisrik@nvidia.com>,
"'Name'" <username@nvidia.com>, <Sami.Mujawar@arm.com>,
<Alexei.Fedorov@arm.com>, <pierre.gondois@arm.com>,
<michael.d.kinney@intel.com>, <zhiguang.liu@intel.com>
Subject: 回复: [edk2-devel] [PATCH 2/2] MdePkg:IORT header update for IORT Rev E.e spec
Date: Fri, 10 Feb 2023 13:26:35 +0800 [thread overview]
Message-ID: <022c01d93d10$3dfe0910$b9fa1b30$@byosoft.com.cn> (raw)
In-Reply-To: <BY5PR12MB55439A5ED98BD49867A50BDFD3D79@BY5PR12MB5543.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 7110 bytes --]
It has been merged at 5db84c85c3544b92fa236c4d169440d523712ae0 in Edk2.
Thanks
Liming
发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Swatisri
Kantamsetti via groups.io
发送时间: 2023年2月4日 2:48
收件人: gaoliming <gaoliming@byosoft.com.cn>; 'Name' <username@nvidia.com>;
devel@edk2.groups.io; Sami.Mujawar@arm.com; Alexei.Fedorov@arm.com;
pierre.gondois@arm.com; michael.d.kinney@intel.com; zhiguang.liu@intel.com
主题: Re: [edk2-devel] [PATCH 2/2] MdePkg:IORT header update for IORT Rev E.
e spec
Just checking to see when this patch could be merged?
Thanks,
Swati
_____
From: gaoliming <gaoliming@byosoft.com.cn <mailto:gaoliming@byosoft.com.cn>
>
Sent: Saturday, January 28, 2023 10:59 PM
To: 'Name' <username@nvidia.com <mailto:username@nvidia.com> >;
devel@edk2.groups.io <mailto:devel@edk2.groups.io> <devel@edk2.groups.io
<mailto:devel@edk2.groups.io> >; Sami.Mujawar@arm.com
<mailto:Sami.Mujawar@arm.com> <Sami.Mujawar@arm.com
<mailto:Sami.Mujawar@arm.com> >; Alexei.Fedorov@arm.com
<mailto:Alexei.Fedorov@arm.com> <Alexei.Fedorov@arm.com
<mailto:Alexei.Fedorov@arm.com> >; pierre.gondois@arm.com
<mailto:pierre.gondois@arm.com> <pierre.gondois@arm.com
<mailto:pierre.gondois@arm.com> >; michael.d.kinney@intel.com
<mailto:michael.d.kinney@intel.com> <michael.d.kinney@intel.com
<mailto:michael.d.kinney@intel.com> >; zhiguang.liu@intel.com
<mailto:zhiguang.liu@intel.com> <zhiguang.liu@intel.com
<mailto:zhiguang.liu@intel.com> >
Cc: Swatisri Kantamsetti <swatisrik@nvidia.com <mailto:swatisrik@nvidia.com>
>
Subject: 回复: [PATCH 2/2] MdePkg:IORT header update for IORT Rev E.e spec
External email: Use caution opening links or attachments
Reviewed-by: Liming Gao <gaoliming@byosoft.com.cn <mailto:gaoliming@byosoft.
com.cn> >
> -----邮件原件-----
> 发件人: Name <username@nvidia.com <mailto:username@nvidia.com> >
> 发送时间: 2023年1月26日 2:41
> 收件人: devel@edk2.groups.io <mailto:devel@edk2.groups.io> ;
Sami.Mujawar@arm.com <mailto:Sami.Mujawar@arm.com> ;
> Alexei.Fedorov@arm.com <mailto:Alexei.Fedorov@arm.com> ;
pierre.gondois@arm.com <mailto:pierre.gondois@arm.com> ;
> michael.d.kinney@intel.com <mailto:michael.d.kinney@intel.com> ;
gaoliming@byosoft.com.cn <mailto:gaoliming@byosoft.com.cn> ;
> zhiguang.liu@intel.com <mailto:zhiguang.liu@intel.com>
> 抄送: Swatisri Kantamsetti <swatisrik@nvidia.com <mailto:swatisrik@nvidia.
com> >
> 主题: [PATCH 2/2] MdePkg:IORT header update for IORT Rev E.e spec
>
> From: Swatisri Kantamsetti <swatisrik@nvidia.com <mailto:swatisrik@nvidia.
com> >
>
> The IO Remapping Table, Platform Design Document, Revision E.e,
> Sept 2022
(https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeveloper
.arm.com%2Fdocumentation%2Fden0049%2Fee <https://nam11.safelinks.protection.
outlook.com/?url=https%3A%2F%2Fdeveloper.arm.com%2Fdocumentation%2Fden0049%2
Fee&data=05%7C01%7Cswatisrik%40nvidia.com%7C39d6cc086d3b45e32ea908db01bdfd93
%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638105687766743781%7CUnknown%7
CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0
%3D%7C3000%7C%7C%7C&sdata=Yfn%2BzXkA2rKS4Y44XkU65gMLQy8OL3iqPF2AmyYmRNM%3D&r
eserved=0>
&data=05%7C01%7Cswatisrik%40nvidia.com%7C39d6cc086d3b45e32ea908db01bdfd93%7C
43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638105687766743781%7CUnknown%7CTW
FpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
%7C3000%7C%7C%7C&sdata=Yfn%2BzXkA2rKS4Y44XkU65gMLQy8OL3iqPF2AmyYmRNM%3D&rese
rved=0)
> added flags in SMMUv3 node for validity of ID mappings for MSIs
> related to control interrupts.
>
> Therefore, update the IORT header file to:
> - increment IORT table revision to 6
> - add support for DeviceId valid flag
>
> Signed-off-by: Swatisri Kantamsetti <swatisrik@nvidia.com
<mailto:swatisrik@nvidia.com> >
> ---
> MdePkg/Include/IndustryStandard/IoRemappingTable.h | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/MdePkg/Include/IndustryStandard/IoRemappingTable.h
> b/MdePkg/Include/IndustryStandard/IoRemappingTable.h
> index f48a4a95cd..544aa67a05 100644
> --- a/MdePkg/Include/IndustryStandard/IoRemappingTable.h
> +++ b/MdePkg/Include/IndustryStandard/IoRemappingTable.h
> @@ -9,6 +9,8 @@
> @par Reference(s):
> - IO Remapping Table, Platform Design Document, Revision E.d, Feb 2022
>
(https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeveloper
.arm.com%2Fdocumentation%2Fden0049%2F
<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeveloper
.arm.com%2Fdocumentation%2Fden0049%2F&data=05%7C01%7Cswatisrik%40nvidia.com%
7C39d6cc086d3b45e32ea908db01bdfd93%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C
0%7C638105687766743781%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV
2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Yb238OnzfBZR8f9a
d%2F5S0Ol3XetVptoMG24AO4Yj8To%3D&reserved=0>
&data=05%7C01%7Cswatisrik%40nvidia.com%7C39d6cc086d3b45e32ea908db01bdfd93%7C
43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638105687766743781%7CUnknown%7CTW
FpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
%7C3000%7C%7C%7C&sdata=Yb238OnzfBZR8f9ad%2F5S0Ol3XetVptoMG24AO4Yj8To%3D&rese
rved=0)
> + - IO Remapping Table, Platform Design Document, Revision E.e, Sept 2022
> +
(https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeveloper
.arm.com%2Fdocumentation%2Fden0049%2F
<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeveloper
.arm.com%2Fdocumentation%2Fden0049%2F&data=05%7C01%7Cswatisrik%40nvidia.com%
7C39d6cc086d3b45e32ea908db01bdfd93%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C
0%7C638105687766743781%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV
2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Yb238OnzfBZR8f9a
d%2F5S0Ol3XetVptoMG24AO4Yj8To%3D&reserved=0>
&data=05%7C01%7Cswatisrik%40nvidia.com%7C39d6cc086d3b45e32ea908db01bdfd93%7C
43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638105687766743781%7CUnknown%7CTW
FpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D
%7C3000%7C%7C%7C&sdata=Yb238OnzfBZR8f9ad%2F5S0Ol3XetVptoMG24AO4Yj8To%3D&rese
rved=0)
>
> @par Glossary:
> - Ref : Reference
> @@ -24,6 +26,7 @@
> #define EFI_ACPI_IO_REMAPPING_TABLE_REVISION_00 0x0
> #define EFI_ACPI_IO_REMAPPING_TABLE_REVISION_04 0x4 //
> Deprecated
> #define EFI_ACPI_IO_REMAPPING_TABLE_REVISION_05 0x5
> +#define EFI_ACPI_IO_REMAPPING_TABLE_REVISION_06 0x6
>
> #define EFI_ACPI_IORT_TYPE_ITS_GROUP 0x0
> #define EFI_ACPI_IORT_TYPE_NAMED_COMP 0x1
> @@ -59,6 +62,7 @@
> #define EFI_ACPI_IORT_SMMUv3_FLAG_COHAC_OVERRIDE BIT0
> #define EFI_ACPI_IORT_SMMUv3_FLAG_HTTU_OVERRIDE BIT1
> #define EFI_ACPI_IORT_SMMUv3_FLAG_PROXIMITY_DOMAIN BIT3
> +#define EFI_ACPI_IORT_SMMUv3_FLAG_DEVICEID_VALID BIT4
>
> #define EFI_ACPI_IORT_SMMUv3_MODEL_GENERIC 0x0
> #define EFI_ACPI_IORT_SMMUv3_MODEL_HISILICON_HI161X 0x1
> --
> 2.17.1
[-- Attachment #2: Type: text/html, Size: 13038 bytes --]
next prev parent reply other threads:[~2023-02-10 5:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 18:40 [PATCH 1/2] DynamicTablesPkg: IORT generator updates for Rev E.e spec Name
2023-01-25 18:40 ` [PATCH 2/2] MdePkg:IORT header update for IORT " Name
2023-01-29 5:59 ` 回复: " gaoliming
2023-02-03 18:47 ` Swatisri Kantamsetti
2023-02-10 5:26 ` gaoliming [this message]
2023-02-06 10:34 ` Sami Mujawar
2023-02-03 16:40 ` [PATCH 1/2] DynamicTablesPkg: IORT generator updates for " PierreGondois
2023-02-06 10:38 ` 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='022c01d93d10$3dfe0910$b9fa1b30$@byosoft.com.cn' \
--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