From: jroedel@suse•de (Joerg Roedel)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH URGENT] arm: dma-mapping: Set DMA IOMMU ops in arm_iommu_attach_device()
Date: Mon, 26 Jan 2015 11:42:29 +0100 [thread overview]
Message-ID: <20150126104229.GB2312@suse.de> (raw)
In-Reply-To: <1422022909-31044-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
On Fri, Jan 23, 2015 at 04:21:49PM +0200, Laurent Pinchart wrote:
> Commit 4bb25789ed28228a ("arm: dma-mapping: plumb our iommu mapping ops
> into arch_setup_dma_ops") moved the setting of the DMA operations from
> arm_iommu_attach_device() to arch_setup_dma_ops() where the DMA
> operations to be used are selected based on whether the device is
> connected to an IOMMU. However, the IOMMU detection scheme requires the
> IOMMU driver to be ported to the new IOMMU of_xlate API. As no driver
> has been ported yet, this effectively breaks all IOMMU ARM users that
> depend on the IOMMU being handled transparently by the DMA mapping API.
>
> Fix this by restoring the setting of DMA IOMMU ops in
> arm_iommu_attach_device() and splitting the rest of the function into a
> new internal __arm_iommu_attach_device() function, called by
> arch_setup_dma_ops().
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard•com>
> ---
> arch/arm/mm/dma-mapping.c | 53 +++++++++++++++++++++++++++++++++--------------
> 1 file changed, 38 insertions(+), 15 deletions(-)
I guess this patch will be merged by one of the ARM trees?
Joerg
next prev parent reply other threads:[~2015-01-26 10:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 14:21 [PATCH URGENT] arm: dma-mapping: Set DMA IOMMU ops in arm_iommu_attach_device() Laurent Pinchart
2015-01-23 15:27 ` Arnd Bergmann
2015-01-23 15:55 ` Laurent Pinchart
2015-01-23 17:00 ` Arnd Bergmann
2015-01-23 17:04 ` Will Deacon
2015-01-26 0:34 ` Heiko Stübner
2015-01-26 10:42 ` Joerg Roedel [this message]
2015-01-28 0:25 ` Heiko Stübner
2015-01-29 18:57 ` Olof Johansson
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=20150126104229.GB2312@suse.de \
--to=jroedel@suse$(echo .)de \
--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