From: zhangfei <zhangfei.gao@linaro.org>
To: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>,
Will Deacon <will.deacon@arm.com>,
Hanjun Guo <hanjun.guo@linaro.org>,
Charles Garcia-Tobin <Charles.Garcia-Tobin@arm.com>,
kenneth-lee-2012 <kenneth-lee-2012@foxmail.com>,
Wangzhou <wangzhou1@hisilicon.com>,
guodong.xu@linaro.org, joro@8bytes.org,
Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH] ACPI/IORT: Let pci_fixup_final access iommu_fwnode
Date: Tue, 2 Apr 2019 18:20:05 +0700 [thread overview]
Message-ID: <6ed5e08c-d116-e3fc-3c35-04ebdd6a091f@linaro.org> (raw)
In-Reply-To: <1553693165-7105-1-git-send-email-zhangfei.gao@linaro.org>
On 2019/3/27 下午8:26, Zhangfei Gao wrote:
> Using quirks to access dev->iommu_fwnode is required for those
> devices appear as PCI but are actually on the AMBA bus.
> dev->iommu_fwnode is allocated in iommu_fwspec_init, while it
> is too late for pci_fixup_final in drivers/pci/quirks.c
> So iort call pci_fixup_final after iommu_fwspec_init.
>
> Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
> ---
> drivers/acpi/arm64/iort.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/arm64/iort.c
> index e48894e..39d7212 100644
> --- a/drivers/acpi/arm64/iort.c
> +++ b/drivers/acpi/arm64/iort.c
> @@ -1063,6 +1063,7 @@ const struct iommu_ops *iort_iommu_configure(struct device *dev)
> info.node = node;
> err = pci_for_each_dma_alias(to_pci_dev(dev),
> iort_pci_iommu_init, &info);
> + pci_fixup_device(pci_fixup_final, to_pci_dev(dev));
> } else {
> int i = 0;
>
Thanks for any suggestion.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-04-02 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 13:26 [RFC PATCH] ACPI/IORT: Let pci_fixup_final access iommu_fwnode Zhangfei Gao
2019-04-02 11:20 ` zhangfei [this message]
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=6ed5e08c-d116-e3fc-3c35-04ebdd6a091f@linaro.org \
--to=zhangfei.gao@linaro.org \
--cc=Charles.Garcia-Tobin@arm.com \
--cc=arnd@arndb.de \
--cc=guodong.xu@linaro.org \
--cc=hanjun.guo@linaro.org \
--cc=jean-philippe.brucker@arm.com \
--cc=joro@8bytes.org \
--cc=kenneth-lee-2012@foxmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=wangzhou1@hisilicon.com \
--cc=will.deacon@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).