From: m.szyprowski@samsung•com (Marek Szyprowski)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC PATCH v4 0/8] Introduce automatic DMA configuration for IOMMU masters
Date: Wed, 19 Nov 2014 12:21:26 +0100 [thread overview]
Message-ID: <546C7D36.7030400@samsung.com> (raw)
In-Reply-To: <1415991397-9618-1-git-send-email-will.deacon@arm.com>
Hello,
On 2014-11-14 19:56, Will Deacon wrote:
> Hello everybody,
>
> Here is the fourth iteration of the RFC I've previously posted here:
>
> RFCv1: http://lists.infradead.org/pipermail/linux-arm-kernel/2014-August/283023.html
> RFCv2: http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/283752.html
> RFCv3: http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/287031.html
>
> Changes since RFCv3 include:
>
> - Drastic simplification of the data structures, so that we no longer
> pass around lists of domains. Instead, dma-mapping is expected to
> allocate the domain (Joerg talked about adding a get_default_domain
> operation to iommu_ops).
>
> - iommu_ops is used to hold the per-instance IOMMU data
>
> - Configuration of DMA segments added to of_dma_configure
>
> All feedback welcome.
I've rebased my Exynos SYSMMU patches on top of this patchset and it
works fine,
You can find them in the "[PATCH v3 00/19] Exynos SYSMMU (IOMMU)
integration with DT
and DMA-mapping subsystem" thread.
You can add to all your patches:
Acked-by: Marek Szyprowski <m.szyprowski@samsung•com>
I'm also interested in adding get_default_domain() callback, but I
assume that this
can be done once the basic patchset get merged. Do you plan to work on
it, do you want
me to implement it?
> Cheers,
>
> Will
>
> --->8
>
> Will Deacon (8):
> iommu: provide early initialisation hook for IOMMU drivers
> dma-mapping: replace set_arch_dma_coherent_ops with arch_setup_dma_ops
> iommu: add new iommu_ops callback for adding an OF device
> iommu: provide helper function to configure an IOMMU for an of master
> dma-mapping: detect and configure IOMMU in of_dma_configure
> dma-mapping: set dma segment properties in of_dma_configure
> arm: call iommu_init before of_platform_populate
> arm: dma-mapping: plumb our iommu mapping ops into arch_setup_dma_ops
>
> arch/arm/include/asm/dma-mapping.h | 12 +++---
> arch/arm/kernel/setup.c | 2 +
> arch/arm/mm/dma-mapping.c | 80 ++++++++++++++++++++++++++++++++++----
> drivers/iommu/Kconfig | 2 +-
> drivers/iommu/of_iommu.c | 50 ++++++++++++++++++++++++
> drivers/of/platform.c | 54 +++++++++++++------------
> include/asm-generic/vmlinux.lds.h | 2 +
> include/linux/amba/bus.h | 1 +
> include/linux/dma-mapping.h | 13 ++++---
> include/linux/iommu.h | 8 ++++
> include/linux/of_iommu.h | 31 +++++++++++++++
> include/linux/platform_device.h | 2 +
> 12 files changed, 214 insertions(+), 43 deletions(-)
>
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
next prev parent reply other threads:[~2014-11-19 11:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 18:56 [RFC PATCH v4 0/8] Introduce automatic DMA configuration for IOMMU masters Will Deacon
2014-11-14 18:56 ` [RFC PATCH v4 1/8] iommu: provide early initialisation hook for IOMMU drivers Will Deacon
2014-11-18 12:28 ` Marek Szyprowski
2014-11-14 18:56 ` [RFC PATCH v4 2/8] dma-mapping: replace set_arch_dma_coherent_ops with arch_setup_dma_ops Will Deacon
2014-11-14 18:56 ` [RFC PATCH v4 3/8] iommu: add new iommu_ops callback for adding an OF device Will Deacon
2014-11-14 18:56 ` [RFC PATCH v4 4/8] iommu: provide helper function to configure an IOMMU for an of master Will Deacon
2014-11-14 18:56 ` [RFC PATCH v4 5/8] dma-mapping: detect and configure IOMMU in of_dma_configure Will Deacon
2014-11-14 18:56 ` [RFC PATCH v4 6/8] dma-mapping: set dma segment properties " Will Deacon
2014-11-25 13:05 ` Robin Murphy
2014-11-26 11:37 ` Will Deacon
2014-11-14 18:56 ` [RFC PATCH v4 7/8] arm: call iommu_init before of_platform_populate Will Deacon
2014-11-14 18:56 ` [RFC PATCH v4 8/8] arm: dma-mapping: plumb our iommu mapping ops into arch_setup_dma_ops Will Deacon
2014-11-17 11:29 ` Robin Murphy
2014-11-17 11:41 ` Will Deacon
2014-11-14 19:11 ` [RFC PATCH v4 0/8] Introduce automatic DMA configuration for IOMMU masters Arnd Bergmann
2014-11-14 19:27 ` Will Deacon
2014-11-14 20:01 ` Arnd Bergmann
2015-01-19 16:06 ` Will Deacon
2015-01-20 16:56 ` Laurent Pinchart
2015-01-21 14:48 ` Will Deacon
2015-01-21 15:02 ` Laurent Pinchart
2014-11-19 11:21 ` Marek Szyprowski [this message]
2014-11-19 11:41 ` Will Deacon
2014-11-25 7:35 ` Marek Szyprowski
2014-11-26 17:47 ` Will Deacon
2014-11-28 13:03 ` jroedel at suse.de
2014-11-28 13:19 ` Will Deacon
2014-12-15 17:21 ` Laurent Pinchart
2014-12-15 17:34 ` Will Deacon
2014-12-15 17:55 ` Laurent Pinchart
2014-11-25 13:15 ` Robin Murphy
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=546C7D36.7030400@samsung.com \
--to=m.szyprowski@samsung$(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