From: Hanjun Guo <guohanjun@huawei.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Robin Murphy <robin.murphy@arm.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linuxarm@huawei.com, Hanjun Guo <hanjun.guo@linaro.org>
Subject: [PATCH v2 0/4] IORT SMMUv3 MSI support
Date: Fri, 13 Oct 2017 15:09:46 +0800 [thread overview]
Message-ID: <1507878590-51066-1-git-send-email-guohanjun@huawei.com> (raw)
From: Hanjun Guo <hanjun.guo@linaro.org>
IORT revision C introduced SMMUv3 MSI support for control interrupts,
which introduced a device ID mapping index to retrieve the dev ID
and ITS parent, adding its support in this patch set, please refer
to each patch for detail commit message.
This patch set is based on Lorenzo's v2 clearup/rework for iort:
https://www.spinics.net/lists/arm-kernel/msg611089.html
Tested on D05 without breakage, and SMMU msi function is OK
on hip08 platform, this version is intented for merge.
v1 -> v2:
- Rewrote commit message by Lorenzo to remove some wrong
message;
- Split patch 3/4 in v1 into two by Lorenzo to make the logic
clearer;
- Drop acpica patch but use the ACPICA version as a guard
for function iort_get_id_mapping_index() in case acpica for
linux kernel is not ready (patch for acpica iasl was merged
already).
RFC v2 -> v1:
- Drop RFC tag;
- return the index value directly from iort_get_id_mapping_index()
then make the logic simple in iort_node_map_id();
- To make sure ID mapping index is only ignored if all interrupts are
GSIV based
- Sqursh part of the patch 4 to patch 3
RFC v1 -> RFC v2:
- Introduce a new API iort_set_device_domain() to find the MSI domain
for an SMMUv3 (or any other IORT table node) to reduce the complex
of doing that via acpi_configure_pmsi_domain().
Hanjun Guo (3):
ACPI/IORT: Look up IORT node through struct fwnode_handle pointer
ACPI/IORT: Enable special index ITS group mappings for IORT nodes
ACPI/IORT: Add SMMUv3 specific special index mapping handling
Lorenzo Pieralisi (1):
ACPI/IORT: Enable SMMUv3/PMCG IORT MSI domain set-up
drivers/acpi/arm64/iort.c | 159 ++++++++++++++++++++++++++++++++++++++++++++--
1 file changed, 153 insertions(+), 6 deletions(-)
--
1.7.12.4
next reply other threads:[~2017-10-13 7:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 7:09 Hanjun Guo [this message]
2017-10-13 7:09 ` [PATCH v2 1/4] ACPI/IORT: Look up IORT node through struct fwnode_handle pointer Hanjun Guo
2017-10-13 7:09 ` [PATCH v2 2/4] ACPI/IORT: Enable special index ITS group mappings for IORT nodes Hanjun Guo
2017-10-13 7:09 ` [PATCH v2 3/4] ACPI/IORT: Add SMMUv3 specific special index mapping handling Hanjun Guo
2017-10-13 13:04 ` Lorenzo Pieralisi
2017-10-13 12:59 ` Rafael J. Wysocki
2017-10-13 7:09 ` [PATCH v2 4/4] ACPI/IORT: Enable SMMUv3/PMCG IORT MSI domain set-up Hanjun Guo
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=1507878590-51066-1-git-send-email-guohanjun@huawei.com \
--to=guohanjun@huawei.com \
--cc=hanjun.guo@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=marc.zyngier@arm.com \
--cc=rafael@kernel.org \
--cc=robin.murphy@arm.com \
/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).