From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] arm64: Wire up iommu_dma_{map, unmap}_resource()
Date: Sun, 13 Nov 2016 11:42:34 +0000 [thread overview]
Message-ID: <20161113114234.GB24837@MBP.local> (raw)
In-Reply-To: <706f6bc883775206d661f38d9c1cbaa4cc4d04b7.1478887214.git.robin.murphy@arm.com>
On Fri, Nov 11, 2016 at 06:27:35PM +0000, Robin Murphy wrote:
> With no coherency to worry about, just plug'em straight in.
>
> CC: Catalin Marinas <catalin.marinas@arm.com>
> CC: Will Deacon <will.deacon@arm.com>
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> ---
> arch/arm64/mm/dma-mapping.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm64/mm/dma-mapping.c b/arch/arm64/mm/dma-mapping.c
> index 3f74d0d98de6..5cd0a383b14b 100644
> --- a/arch/arm64/mm/dma-mapping.c
> +++ b/arch/arm64/mm/dma-mapping.c
> @@ -796,6 +796,8 @@ static struct dma_map_ops iommu_dma_ops = {
> .sync_single_for_device = __iommu_sync_single_for_device,
> .sync_sg_for_cpu = __iommu_sync_sg_for_cpu,
> .sync_sg_for_device = __iommu_sync_sg_for_device,
> + .map_resource = iommu_dma_map_resource,
> + .unmap_resource = iommu_dma_unmap_resource,
> .dma_supported = iommu_dma_supported,
> .mapping_error = iommu_dma_mapping_error,
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
I guess these two patches would go in via the iommu tree.
--
Catalin
next prev parent reply other threads:[~2016-11-13 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 18:27 [PATCH v3 1/2] iommu/dma: Implement dma_{map,unmap}_resource() Robin Murphy
2016-11-11 18:27 ` [PATCH v3 2/2] arm64: Wire up iommu_dma_{map, unmap}_resource() Robin Murphy
2016-11-13 11:42 ` Catalin Marinas [this message]
2016-11-13 11:41 ` [PATCH v3 1/2] iommu/dma: Implement dma_{map,unmap}_resource() 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=20161113114234.GB24837@MBP.local \
--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).