Re: [RFC PATCH v2 2/3] arm64: add IOMMU dma_ops

2015-02-09 Thread Yingjoe Chen
On Fri, 2015-02-06 at 14:55 +, Robin Murphy wrote <...> > diff --git a/arch/arm64/include/asm/dma-mapping.h > b/arch/arm64/include/asm/dma-mapping.h > index 6932bb5..c1b271f 100644 > --- a/arch/arm64/include/asm/dma-mapping.h > +++ b/arch/arm64/include/asm/dma-mapping.h > @@ -62,13 +62,30 @@ s

RE: [PATCH v2 01/26] iommu/fsl: Sprinkle some __init* annotations

2015-02-09 Thread Varun Sethi
Hi Emil, > -Original Message- > From: Emil Medve [mailto:emilian.me...@freescale.com] > Sent: Tuesday, February 10, 2015 3:17 AM > To: iommu@lists.linux-foundation.org; j...@8bytes.org; jroe...@suse.de; > Sethi Varun-B16395 > Subject: Re: [PATCH v2 01/26] iommu/fsl: Sprinkle some __init*

Re: [PATCH v2 01/26] iommu/fsl: Sprinkle some __init* annotations

2015-02-09 Thread Emil Medve
Hello Joerg, On 01/28/2015 08:34 AM, Emil Medve wrote: > Signed-off-by: Emil Medve > --- > drivers/iommu/fsl_pamu.c| 12 ++-- > drivers/iommu/fsl_pamu_domain.c | 2 +- > 2 files changed, 7 insertions(+), 7 deletions(-) Please don't apply this patch as it's wrong. It's based on

Re: [PATCH/RFC 0/4] Probe deferral for IOMMU DT integration

2015-02-09 Thread Laura Abbott
On 2/7/2015 2:41 PM, a...@arndb.de wrote: Laura Abbott hat am 6. Februar 2015 um 01:31 geschrieben: The requirement for this is based on a previous patch to add clock support to the ARM SMMU driver[2]. Once we have clock support, it's possible that the driver itself may need to be defered whic

Re: [PATCH v6 0/7] PCI: get DMA configuration from parent device

2015-02-09 Thread Murali Karicheri
On 02/09/2015 12:23 AM, Suravee Suthikulpanit wrote: Sorry for delay response. I have also tested this on AMD Seattle platform w/ PCI Generic Host Controller, and I can see that the PCI endpoint devices are getting proper dma_map_ops as set in the host bridge. : Suravee Suthikulpanit Surave

Re: [PATCH] CHROMIUM: iommu: rockchip: Make sure that page table state is coherent

2015-02-09 Thread Tomasz Figa
On Mon, Feb 9, 2015 at 8:19 PM, Tomasz Figa wrote: > Even though the code uses the dt_lock spin lock to serialize mapping > operation from different threads, it does not protect from IOMMU > accesses that might be already taking place and thus altering state > of the IOTLB. This means that current

[PATCH] CHROMIUM: iommu: rockchip: Make sure that page table state is coherent

2015-02-09 Thread Tomasz Figa
Even though the code uses the dt_lock spin lock to serialize mapping operation from different threads, it does not protect from IOMMU accesses that might be already taking place and thus altering state of the IOTLB. This means that current mapping code which first zaps the page table and only then

Re: [PATCH v2 2/4] iommu/omap: Play nice in multi-platform builds

2015-02-09 Thread Laurent Pinchart
Hi Thierry, Thank you for the patch. On Friday 06 February 2015 11:44:06 Thierry Reding wrote: > From: Thierry Reding > > The OMAP IOMMU driver unconditionally executes code and registers a > struct iommu_ops with the platform bus irrespective of whether it runs > on an OMAP SoC or not. This ca