From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: pl330: Add IOMMU support to slave tranfers
Date: Tue, 30 May 2017 11:48:02 +0530 [thread overview]
Message-ID: <20170530061757.GK15061@localhost> (raw)
In-Reply-To: <c10016eb9d96d80afcacf547b8a9ec47c6a4cb21.1495202642.git.robin.murphy@arm.com>
On Fri, May 19, 2017 at 03:06:44PM +0100, Robin Murphy wrote:
> Wire up dma_map_resource() for slave transfers, so that we can let the
> PL330 use IOMMU-backed DMA mapping ops on systems with an appropriate
> IOMMU and RAM above 4GB, to avoid CPU bounce buffering.
Applied, thanks
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: dan.j.williams@intel.com, dmaengine@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: pl330: Add IOMMU support to slave tranfers
Date: Tue, 30 May 2017 11:48:02 +0530 [thread overview]
Message-ID: <20170530061757.GK15061@localhost> (raw)
In-Reply-To: <c10016eb9d96d80afcacf547b8a9ec47c6a4cb21.1495202642.git.robin.murphy@arm.com>
On Fri, May 19, 2017 at 03:06:44PM +0100, Robin Murphy wrote:
> Wire up dma_map_resource() for slave transfers, so that we can let the
> PL330 use IOMMU-backed DMA mapping ops on systems with an appropriate
> IOMMU and RAM above 4GB, to avoid CPU bounce buffering.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2017-05-30 6:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 14:06 [PATCH] dmaengine: pl330: Add IOMMU support to slave tranfers Robin Murphy
2017-05-19 14:06 ` Robin Murphy
2017-05-30 6:18 ` Vinod Koul [this message]
2017-05-30 6:18 ` Vinod Koul
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=20170530061757.GK15061@localhost \
--to=vinod.koul@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.