From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
Robert Moore <robert.moore@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Hanjun Guo <guohanjun@huawei.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Marc Zyngier <maz@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-acpi@vger.kernel.org, acpica-devel@lists.linux.dev,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Jose Marinho <jose.marinho@arm.com>
Subject: [PATCH not for merging 2/7] ACPICA: Add Arm IORT IWB node definitions
Date: Tue, 28 Oct 2025 11:19:00 +0100 [thread overview]
Message-ID: <20251028-gicv5-host-acpi-v1-2-01a862feb5ca@kernel.org> (raw)
In-Reply-To: <20251028-gicv5-host-acpi-v1-0-01a862feb5ca@kernel.org>
From: Jose Marinho <jose.marinho@arm.com>
ACPICA commit d68693b24e5235a7da4d57e690d3c13380c14c16
The IORT IUWB node is defined in IORT issue E.g
See https://developer.arm.com/documentation/den0049/eg
Link: https://github.com/acpica/acpica/commit/d68693b2
Signed-off-by: Jose Marinho <jose.marinho@arm.com>
Signed-off-by: Lorenzo Pieralisi <lpieralisi@kernel.org>
---
include/acpi/actbl2.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/include/acpi/actbl2.h b/include/acpi/actbl2.h
index fdabc6c64a9c..ba1a36d23e32 100644
--- a/include/acpi/actbl2.h
+++ b/include/acpi/actbl2.h
@@ -680,6 +680,7 @@ enum acpi_iort_node_type {
ACPI_IORT_NODE_SMMU_V3 = 0x04,
ACPI_IORT_NODE_PMCG = 0x05,
ACPI_IORT_NODE_RMR = 0x06,
+ ACPI_IORT_NODE_IWB = 0x07,
};
struct acpi_iort_id_mapping {
@@ -858,6 +859,12 @@ struct acpi_iort_rmr_desc {
u32 reserved;
};
+struct acpi_iort_iwb {
+ u64 base_address;
+ u16 iwb_index; /* Unique IWB identifier matching with the IWB GSI namespace. */
+ char device_name[]; /* Path of the IWB namespace object */
+};
+
/*******************************************************************************
*
* IVRS - I/O Virtualization Reporting Structure
--
2.50.1
next prev parent reply other threads:[~2025-10-28 10:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 10:18 [PATCH not for merging 0/7] irqchip/gic-v5: Code first ACPI boot support Lorenzo Pieralisi
2025-10-28 10:18 ` [PATCH not for merging 1/7] ACPICA: Add GICv5 MADT structures Lorenzo Pieralisi
2025-10-28 10:19 ` Lorenzo Pieralisi [this message]
2025-10-28 10:19 ` [PATCH not for merging 3/7] irqdomain: Add parent field to irqchip_fwid Lorenzo Pieralisi
2025-10-28 10:19 ` [PATCH not for merging 4/7] PCI/MSI: Make the pci_msi_map_rid_ctlr_node() interface firmware agnostic Lorenzo Pieralisi
2025-10-28 10:19 ` [PATCH not for merging 5/7] irqchip/gic-v5: Add ACPI IRS probing Lorenzo Pieralisi
2025-10-28 10:19 ` [PATCH not for merging 6/7] irqchip/gic-v5: Add ACPI ITS probing Lorenzo Pieralisi
2025-10-28 10:19 ` [PATCH not for merging 7/7] irqchip/gic-v5: Add ACPI IWB probing Lorenzo Pieralisi
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=20251028-gicv5-host-acpi-v1-2-01a862feb5ca@kernel.org \
--to=lpieralisi@kernel.org \
--cc=acpica-devel@lists.linux.dev \
--cc=bhelgaas@google.com \
--cc=guohanjun@huawei.com \
--cc=jose.marinho@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=maz@kernel.org \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.com \
--cc=sudeep.holla@arm.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).