From: catalin.marinas@arm•com (Catalin Marinas)
To: linux-arm-kernel@lists•infradead.org
Subject: DMA mapping API(IOMMU) for ARM64?
Date: Tue, 18 Jun 2013 11:38:05 +0100 [thread overview]
Message-ID: <20130618103804.GI9930@arm.com> (raw)
In-Reply-To: <5159282.rrJMaZuYMv@wuerfel>
On Tue, Jun 18, 2013 at 11:32:44AM +0100, Arnd Bergmann wrote:
> On Tuesday 18 June 2013 11:19:14 Will Deacon wrote:
> > I've spoken briefly with Catalin about this and it seems like there might be
> > *some* scope for sharing common dma-mapping code between architectures.
> > There doesn't really need to be any architecture-specific details in
> > allocating iova space and the interface to the iommu drivers is
> > well-defined. The arch-specific stuff is bogged down in the non-coherent
> > buffer management, but that doesn't necessarily equate to lots of code.
> >
> > So, the best bet would be to figure out how to split up what we have under
> > arch/arm/ so that it can be re-used by arm64 and potentially other
> > architectures (powerpc has some simple stuff for coherent mappings and some
> > less-simple stuff for non-coherent buffers).
>
> I'm sure that other architectures are interested in sharing the code.
> Best move it into the global mm/ directory, at least the version for
> coherent mappings.
Or we could extend the lib/iommu-helper.c or add another file in there
(we already have lib/swiotlb.c).
--
Catalin
next prev parent reply other threads:[~2013-06-18 10:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 2:39 DMA mapping API(IOMMU) for ARM64? Hiroshi Doyu
2013-06-18 10:19 ` Will Deacon
2013-06-18 10:32 ` Arnd Bergmann
2013-06-18 10:38 ` Catalin Marinas [this message]
2013-06-18 11:01 ` Hiroshi Doyu
2013-06-18 12:50 ` Catalin Marinas
2013-06-18 14:15 ` Arnd Bergmann
2013-06-18 15:20 ` Hiroshi Doyu
2013-06-18 22:08 ` Don Dutile
2013-06-19 11:11 ` Catalin Marinas
2013-06-19 9:29 ` Marek Szyprowski
2013-06-18 12:51 ` Arnd Bergmann
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=20130618103804.GI9930@arm.com \
--to=catalin.marinas@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