linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: CMA on AArch64
Date: Thu, 21 Nov 2013 12:37:52 +0000	[thread overview]
Message-ID: <20131121123751.GD22663@arm.com> (raw)
In-Reply-To: <20131121121135.GW16735@n2100.arm.linux.org.uk>

On Thu, Nov 21, 2013 at 12:11:35PM +0000, Russell King - ARM Linux wrote:
> On Thu, Nov 21, 2013 at 12:06:00PM +0000, Catalin Marinas wrote:
> > On Wed, Nov 20, 2013 at 09:41:18PM +0000, Laura Abbott wrote:
> > > I noticed there is currently no CMA support for AArch64. Is this already 
> > > on someone's TODO list or is this still open?
> > 
> > It's more like a wish list but there were other things that took
> > priority. The arm64 DMA mapping code currently only supports swiotlb and
> > our next plan is for IOMMU mapping. But I would like parts of the DMA
> > IOMMU code under arch/arm to be made into a library (similar to the
> > lib/swiotlb.c) so that other architectures can easily make use of it.
> 
> If you're referring to dmabounce.c, that's a 100% no-way-ever-even-if-
> hell-freezes-over NACK.

Does dmabounce.c implement IOMMU support? I'm talking about functions
like __alloc_iova, __iommu_create_mapping etc.

The generic swiotlb code has enough bouncing capabilities for my needs.

-- 
Catalin

  reply	other threads:[~2013-11-21 12:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 21:41 CMA on AArch64 Laura Abbott
2013-11-21 12:06 ` Catalin Marinas
2013-11-21 12:11   ` Russell King - ARM Linux
2013-11-21 12:37     ` Catalin Marinas [this message]
2014-02-26  9:50   ` [Linaro-mm-sig] " Hwang Chih-Chyuan
2014-02-26 12:08     ` Catalin Marinas

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=20131121123751.GD22663@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).