From: Hanjun Guo <hanjun.guo@linaro.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: iommu@lists.linux-foundation.org,
Will Deacon <will.deacon@arm.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Tomasz Nowicki <tn@semihalf.com>, Jon Masters <jcm@redhat.com>,
Sinan Kaya <okaya@codeaurora.org>,
linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linuxarm@huawei.com
Subject: Re: [RFC PATCH v2 00/15] ACPI IORT ARM SMMU v3 support
Date: Wed, 22 Jun 2016 10:45:05 +0800 [thread overview]
Message-ID: <e9d5d68a-3e1d-4517-7f67-b7941e74eddd@linaro.org> (raw)
In-Reply-To: <20160621142704.GA31593@red-moon>
On 2016/6/21 22:27, Lorenzo Pieralisi wrote:
> Hi Hanjun,
>
> On Tue, Jun 21, 2016 at 06:37:17PM +0800, Hanjun Guo wrote:
>> Hi Lorenzo,
>>
>> On 2016/6/7 21:30, Lorenzo Pieralisi wrote:
>>> This RFC patch series is v2 of a previous posting:
>>>
>>> https://lkml.org/lkml/2016/4/14/702
>>>
>>> v1 -> v2:
>>> - Rebased on top of dependencies series [1][2][3](v4.7-rc1)
>>> - Removed IOMMU fwnode generalization
>>> - Implemented ARM SMMU v3 ACPI probing instead of ARM SMMU v2
>>> owing to patch series dependencies [1]
>>> - Moved platform device creation logic to IORT code to
>>> generalize its usage for ARM SMMU v1-v2-v3 components
>>> - Removed reliance on ACPI early device probing
>>> - Created IORT specific iommu_xlate() translation hook leaving
>>> OF code unchanged according to v1 reviews
>>>
>>> The ACPI IORT table provides information that allows instantiating
>>> ARM SMMU devices and carrying out id mappings between components on
>>> ARM based systems (devices, IOMMUs, interrupt controllers).
>>>
>>> http://infocenter.arm.com/help/topic/com.arm.doc.den0049b/DEN0049B_IO_Remapping_Table.pdf
>>>
>>> Building on basic IORT support, available through [2]:
>>>
>>> this patchset enables ARM SMMU v3 support on ACPI systems.
>>
>> I'm trying to test your patches on D03 (SMMUv3 based) but ...
>
> What do you mean by "I am trying.." :), have you actually tested
> this series ?
I was rebasing this series on top of Tomasz's latest ITS patchset,
and found that patch 1~2,5 are not needed, and also have conflicts
(expected), so I think it's better to wait for the updated version
from you :)
>
>> [...]
>>> [1] R.Murphy "Generic DT bindings for PCI and ARM SMMU v3"
>>> http://marc.info/?l=linux-arm-kernel&m=146497432413816&w=2
>>
>> ...This patch set is still in discussion and seems not work
>> for non-PCI devices.
>
> Can you be more specific please ? Yes, both series are work
> in progress.
>
>>> [2] T.Nowicki "Introduce ACPI world to ITS irqchip" v5
>>> http://marc.info/?l=linux-acpi&m=146469369703684&w=2
>>
>> Tomasz sent out the v7 and included patches in your series.
>>
>> I think a updated version before the test makes sense, what
>> do you think? Let me know your thoughts.
>
> I am working with Robin so that the xlate() mechanism works
> properly and seamlessly for both DT and ACPI, given the
> dependencies I think it makes more sense to wait for Tomasz
> and Robin patches to get merged or at least stabilize before
> doing anything else, I am curently working on a v3.
OK.
Thanks
Hanjun
prev parent reply other threads:[~2016-06-22 2:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 13:30 [RFC PATCH v2 00/15] ACPI IORT ARM SMMU v3 support Lorenzo Pieralisi
2016-06-07 13:30 ` [RFC PATCH v2 01/15] drivers: acpi: iort: fix struct pci_dev compiler warnings Lorenzo Pieralisi
2016-06-07 13:30 ` [RFC PATCH v2 02/15] drivers: irqchip: its: fix its_acpi_probe() prototype Lorenzo Pieralisi
2016-06-07 13:30 ` [RFC PATCH v2 03/15] arm64: mm: change IOMMU notifier action to attach DMA ops Lorenzo Pieralisi
2016-06-17 9:27 ` Robin Murphy
2016-06-17 14:15 ` Lorenzo Pieralisi
2016-06-23 11:32 ` Robin Murphy
2016-06-21 7:53 ` Marek Szyprowski
2016-06-21 16:06 ` Lorenzo Pieralisi
2016-06-23 6:13 ` Marek Szyprowski
2016-06-07 13:30 ` [RFC PATCH v2 04/15] drivers: acpi: iort: add support for IOMMU registration Lorenzo Pieralisi
2016-06-07 13:31 ` [RFC PATCH v2 05/15] drivers: acpi: iort: add support for named component look-up Lorenzo Pieralisi
2016-06-07 13:31 ` [RFC PATCH v2 06/15] drivers: acpi: iort: enhance device identifiers mappings Lorenzo Pieralisi
2016-06-07 13:31 ` [RFC PATCH v2 07/15] drivers: acpi: iort: add node match function Lorenzo Pieralisi
2016-06-07 13:31 ` [RFC PATCH v2 08/15] drivers: acpi: iort: add support for ARM SMMU platform devices creation Lorenzo Pieralisi
2016-06-07 13:31 ` [RFC PATCH v2 09/15] drivers: iommu: arm-smmu-v3: split probe functions into DT/generic portions Lorenzo Pieralisi
2016-06-14 18:09 ` Will Deacon
2016-06-07 13:31 ` [RFC PATCH v2 10/15] drivers: iommu: arm-smmu-v3: enable ACPI driver initialization Lorenzo Pieralisi
2016-06-14 18:12 ` Will Deacon
2016-06-07 13:31 ` [RFC PATCH v2 11/15] drivers: iommu: arm-smmu-v3: add IORT iommu configuration Lorenzo Pieralisi
2016-06-14 18:39 ` Will Deacon
2016-06-15 8:52 ` Lorenzo Pieralisi
2016-06-07 13:31 ` [RFC PATCH v2 12/15] drivers: acpi: implement acpi_dma_configure Lorenzo Pieralisi
2016-06-10 16:25 ` Bjorn Helgaas
2016-06-07 13:31 ` [RFC PATCH v2 13/15] drivers: acpi: iort: introduce iort_iommu_configure Lorenzo Pieralisi
2016-06-10 12:46 ` Tomasz Nowicki
2016-06-07 13:31 ` [RFC PATCH v2 14/15] drivers: acpi: iort: add function to retrieve IOMMU platform devices Lorenzo Pieralisi
2016-06-07 13:31 ` [RFC PATCH v2 15/15] drivers: iommu: arm-smmu-v3: allow ACPI based streamid translation Lorenzo Pieralisi
2016-06-21 10:37 ` [RFC PATCH v2 00/15] ACPI IORT ARM SMMU v3 support Hanjun Guo
2016-06-21 14:27 ` Lorenzo Pieralisi
2016-06-22 2:45 ` Hanjun Guo [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=e9d5d68a-3e1d-4517-7f67-b7941e74eddd@linaro.org \
--to=hanjun.guo@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jcm@redhat.com \
--cc=joro@8bytes.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=linuxarm@huawei.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=marc.zyngier@arm.com \
--cc=okaya@codeaurora.org \
--cc=rjw@rjwysocki.net \
--cc=robin.murphy@arm.com \
--cc=tn@semihalf.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).