From: will.deacon@arm•com (Will Deacon)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v4 0/4] arm64: IOMMU-backed DMA mapping
Date: Tue, 28 Jul 2015 13:46:57 +0100 [thread overview]
Message-ID: <20150728124657.GK29209@arm.com> (raw)
In-Reply-To: <55AD2E97.1040901@arm.com>
Hi Joerg, Robin,
On Mon, Jul 20, 2015 at 06:23:35PM +0100, Robin Murphy wrote:
> On 20/07/15 16:26, Joerg Roedel wrote:
> > On Thu, Jul 16, 2015 at 07:40:11PM +0100, Robin Murphy wrote:
> >> arch/arm64/Kconfig | 1 +
> >> arch/arm64/include/asm/dma-mapping.h | 15 +-
> >> arch/arm64/mm/dma-mapping.c | 452 +++++++++++++++++++++++++++++
> >
> > What happened to the plan to merge this with the existing iommu-based
> > dma-api implementation for 32 bit ARM?
>
> The issue currently is that there are a bunch of drivers using the
> exported arm_iommu_* functions directly. From what I can tell, they seem
> like they could probably all be converted to using default domains
> and/or the new domain type abstractions via the core IOMMU API, which
> would then allow killing off dma_iommu_mapping and rewriting the
> arch/arm implementation to use the new shared code. I don't currently
> have any 32-bit platform to test with, so I'm a little dubious of taking
> that all on myself right now.
>
> In the meantime on arm64, DMA mapping ops are needed for SMMUv3 platform
> device support, the Mediatek M4U patches and my own SMMUv2 work, so it
> would be very useful to get the arm64 and common code in as a first
> step, then look at cleaning up arch/arm for 4.4 without dangling
> dependencies.
What's the plan with this? Do we need to port 32-bit ARM before it's a
candidate for merging, or can we push ahead with getting this up and
running for arm64 (which currently can't use an IOMMU for DMA)?
Will
prev parent reply other threads:[~2015-07-28 12:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 18:40 [PATCH v4 0/4] arm64: IOMMU-backed DMA mapping Robin Murphy
2015-07-16 18:40 ` [PATCH v4 1/4] iommu/iova: Avoid over-allocating when size-aligned Robin Murphy
2015-07-28 13:31 ` David Woodhouse
2015-07-16 18:40 ` [PATCH v4 2/4] iommu: Implement common IOMMU ops for DMA mapping Robin Murphy
2015-07-28 16:45 ` Catalin Marinas
2015-07-16 18:40 ` [PATCH v4 3/4] arm64: Add IOMMU dma_ops Robin Murphy
2015-07-28 17:27 ` Catalin Marinas
2015-07-16 18:40 ` [PATCH v4 4/4] arm64: Hook up " Robin Murphy
2015-07-28 17:30 ` Catalin Marinas
2015-07-20 15:26 ` [PATCH v4 0/4] arm64: IOMMU-backed DMA mapping Joerg Roedel
2015-07-20 17:23 ` Robin Murphy
2015-07-28 12:46 ` Will Deacon [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=20150728124657.GK29209@arm.com \
--to=will.deacon@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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