From: yong.wu@mediatek.com (Yong Wu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/3] arm64: IOMMU-backed DMA mapping
Date: Wed, 26 Aug 2015 14:19:26 +0800 [thread overview]
Message-ID: <1440569966.25782.3.camel@mhfsdcap03> (raw)
In-Reply-To: <cover.1438362603.git.robin.murphy@arm.com>
On Fri, 2015-07-31 at 18:18 +0100, Robin Murphy wrote:
> Hi all,
>
> Here's an update following Catalin's feedback on v4[1].
>
> Changes this round:
> - Rebased onto linux-next
> - IOVA alignment fix applied already
> - iommu_iova_cache_init() is now iova_cache_get()
> - Tidied up iommu_dma_alloc()
> - Simplified pgprot handling
> - Removed redundant memset
> - Skip coherent page-flushing in a simpler way
> - Spotted a bug in iommu_dma_init_domain() where the checks for
> reinitialising an existing domain were backwards.
>
> If it is going to be down to me to tackle all the driver fixes and
> conversion of arch/arm dma_ops, I'd still much rather have this
> code merged first as a stable base to work with (and un-block arm64
> in the meantime). Have we decided yet whether this should go via the
> IOMMU tree or the arm64 tree?
Hi Robin,
Sorry to disturb you. Is there any plan for the next version of arm64
DMA. If it's yes, when could we get it?
Thanks very much.
>
> Thanks,
> Robin.
>
> [1]:http://thread.gmane.org/gmane.linux.kernel.iommu/10181
>
> Robin Murphy (3):
> iommu: Implement common IOMMU ops for DMA mapping
> arm64: Add IOMMU dma_ops
> arm64: Hook up IOMMU dma_ops
>
> arch/arm64/Kconfig | 1 +
> arch/arm64/include/asm/dma-mapping.h | 15 +-
> arch/arm64/mm/dma-mapping.c | 449 +++++++++++++++++++++++++++++
> drivers/iommu/Kconfig | 7 +
> drivers/iommu/Makefile | 1 +
> drivers/iommu/dma-iommu.c | 534 +++++++++++++++++++++++++++++++++++
> include/linux/dma-iommu.h | 84 ++++++
> include/linux/iommu.h | 1 +
> 8 files changed, 1084 insertions(+), 8 deletions(-)
> create mode 100644 drivers/iommu/dma-iommu.c
> create mode 100644 include/linux/dma-iommu.h
>
prev parent reply other threads:[~2015-08-26 6:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 17:18 [PATCH v5 0/3] arm64: IOMMU-backed DMA mapping Robin Murphy
2015-07-31 17:18 ` [PATCH v5 1/3] iommu: Implement common IOMMU ops for " Robin Murphy
2015-08-03 17:40 ` Catalin Marinas
2015-08-06 15:23 ` Will Deacon
2015-08-06 17:54 ` joro at 8bytes.org
2015-08-07 8:42 ` Joerg Roedel
2015-08-07 13:38 ` Robin Murphy
2015-08-11 9:37 ` Joerg Roedel
2015-08-11 13:31 ` Robin Murphy
2015-07-31 17:18 ` [PATCH v5 2/3] arm64: Add IOMMU dma_ops Robin Murphy
2015-08-03 17:33 ` Catalin Marinas
2015-08-07 8:52 ` Joerg Roedel
2015-08-07 15:27 ` Robin Murphy
2015-08-11 9:49 ` Joerg Roedel
2015-08-11 20:15 ` Robin Murphy
2015-09-22 17:12 ` Daniel Kurtz
2015-09-22 18:11 ` Robin Murphy
2015-07-31 17:18 ` [PATCH v5 3/3] arm64: Hook up " Robin Murphy
2015-08-07 8:55 ` Joerg Roedel
2015-08-26 6:19 ` Yong Wu [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=1440569966.25782.3.camel@mhfsdcap03 \
--to=yong.wu@mediatek.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