From: "Swatisri Kantamsetti via groups.io" <swatisrik=nvidia.com@groups.io>
To: <devel@edk2.groups.io>, <Sami.Mujawar@arm.com>, <pierre.gondois@arm.com>
Cc: Swatisri Kantamsetti <swatisrik@nvidia.com>
Subject: [edk2-devel] [PATCH] DynamicTablesPkg: IORT generator updates for Rev E.e spec
Date: Fri, 22 Sep 2023 15:40:38 -0600 [thread overview]
Message-ID: <273efda2552363dd2ed5794b00b1b4e87b290909.1695418444.git.swatisrik@nvidia.com> (raw)
The IO Remapping Table, Platform Design Document, Revision E.e,
Sept 2022 (https://developer.arm.com/documentation/den0049/ee)
added flags in SMMUv3 node for validity of ID mappings for MSIs
related to control interrupts.
It makes one small addition to SMMUv3 nodes to
describe MSI support independently of wired GSIV support
Therefore, update the IORT generator to:
- increment IORT table revision to 6
- increment SMMUV3 node revision to 5
- for SMMUV3 node revision >=5 check the DeviceID mapping index
valid flag to populate DeviceIdMappingIndex field
Signed-off-by: Swatisri Kantamsetti <swatisrik@nvidia.com>
---
.../Acpi/Arm/AcpiIortLibArm/IortGenerator.c | 35 +++++++++++++++----
1 file changed, 28 insertions(+), 7 deletions(-)
diff --git a/DynamicTablesPkg/Library/Acpi/Arm/AcpiIortLibArm/IortGenerator.c b/DynamicTablesPkg/Library/Acpi/Arm/AcpiIortLibArm/IortGenerator.c
index f28973c1a8..a6e4b49cb1 100644
--- a/DynamicTablesPkg/Library/Acpi/Arm/AcpiIortLibArm/IortGenerator.c
+++ b/DynamicTablesPkg/Library/Acpi/Arm/AcpiIortLibArm/IortGenerator.c
@@ -5,7 +5,7 @@
SPDX-License-Identifier: BSD-2-Clause-Patent
@par Reference(s):
- - IO Remapping Table, Platform Design Document, Revision E.d, Feb 2022
+ - IO Remapping Table, Platform Design Document, Revision E.e, Sept 2022
(https://developer.arm.com/documentation/den0049/)
**/
@@ -1554,9 +1554,14 @@ AddSmmuV3Nodes (
{
SmmuV3Node->Node.Revision = 2;
SmmuV3Node->Node.Identifier = EFI_ACPI_RESERVED_DWORD;
- } else {
+ } else if (AcpiTableInfo->AcpiTableRevision <
+ EFI_ACPI_IO_REMAPPING_TABLE_REVISION_06)
+ {
SmmuV3Node->Node.Revision = 4;
SmmuV3Node->Node.Identifier = NodeList->Identifier;
+ } else {
+ SmmuV3Node->Node.Revision = 5;
+ SmmuV3Node->Node.Identifier = NodeList->Identifier;
}
// SMMUv3 specific data
@@ -1577,11 +1582,27 @@ AddSmmuV3Nodes (
SmmuV3Node->ProximityDomain = 0;
}
- if ((SmmuV3Node->Event != 0) && (SmmuV3Node->Pri != 0) &&
- (SmmuV3Node->Gerr != 0) && (SmmuV3Node->Sync != 0))
+ /* For older SMMUV3 nodes rev. < 5.
+ If all the SMMU control interrupts are GSIV based,
+ the DeviceID mapping index field is ignored.
+ DeviceID mapping valid flag was introduced in IORT rev E.e
+ for SMMUV3 nodes rev. > 5.
+ If the DeviceID mapping index valid flag is set to 0,
+ DeviceID mapping index field must be ignored.
+ Where the SMMU uses message signaled interrupts for
+ its control interrupts, DeviceId Mapping Index contains an
+ index into the array of ID mapping.
+ */
+ if (((SmmuV3Node->Node.Revision < 5) &&
+ (SmmuV3Node->Event != 0) &&
+ (SmmuV3Node->Pri != 0) &&
+ (SmmuV3Node->Gerr != 0) &&
+ (SmmuV3Node->Sync != 0)
+ ) ||
+ ((SmmuV3Node->Node.Revision >= 5) &&
+ ((SmmuV3Node->Flags & EFI_ACPI_IORT_SMMUv3_FLAG_DEVICEID_VALID) == 0))
+ )
{
- // If all the SMMU control interrupts are GSIV based,
- // the DeviceID mapping index field is ignored.
SmmuV3Node->DeviceIdMappingIndex = 0;
} else {
SmmuV3Node->DeviceIdMappingIndex = NodeList->DeviceIdMappingIndex;
@@ -2819,7 +2840,7 @@ ACPI_IORT_GENERATOR IortGenerator = {
// ACPI Table Signature
EFI_ACPI_6_4_IO_REMAPPING_TABLE_SIGNATURE,
// ACPI Table Revision supported by this Generator
- EFI_ACPI_IO_REMAPPING_TABLE_REVISION_05,
+ EFI_ACPI_IO_REMAPPING_TABLE_REVISION_06,
// Minimum supported ACPI Table Revision
EFI_ACPI_IO_REMAPPING_TABLE_REVISION_00,
// Creator ID
--
2.17.1
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#109023): https://edk2.groups.io/g/devel/message/109023
Mute This Topic: https://groups.io/mt/101535844/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next reply other threads:[~2023-09-23 6:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 21:40 Swatisri Kantamsetti via groups.io [this message]
2023-09-25 9:19 ` [edk2-devel] [PATCH] DynamicTablesPkg: IORT generator updates for Rev E.e spec Sami Mujawar
2023-09-25 9:40 ` Leif Lindholm
2023-09-25 9:47 ` 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=273efda2552363dd2ed5794b00b1b4e87b290909.1695418444.git.swatisrik@nvidia.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