From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Suman Tripathi <stripathi@apm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Jon Masters <jcm@redhat.com>,
anton@enomsg.org, linux-mmc@vger.kernel.org, chris@printf.net,
patches@apm.com, Don Dutile <ddutile@redhat.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/2] mmc: host: arasan: Add addition of-arasan quirks and add IOMMU support.
Date: Tue, 06 Jan 2015 14:55:51 +0100 [thread overview]
Message-ID: <3924494.iNyoV2USme@wuerfel> (raw)
In-Reply-To: <CAOHikRCV7RaxJz-A_s6g++ueg3CDe9Jrqcog1Lc2_+KXR9QqnQ@mail.gmail.com>
On Tuesday 06 January 2015 17:10:29 Suman Tripathi wrote:
> Hi Arnd,
> > On Monday 15 December 2014 22:31:06 Suman Tripathi wrote:
> > > @@ -162,6 +206,16 @@ static int sdhci_arasan_probe(struct
> > > platform_device *pdev)> > >
> > > goto clk_dis_ahb;
> > >
> > > }
> > >
> > > +#if defined(CONFIG_IOMMU_SUPPORT)
> > > + sdhci_arasan->domain = iommu_domain_alloc(&amba_bustype);
> > > + if (!sdhci_arasan->domain) {
> > > + dev_err(&pdev->dev, "Unable to allocate iommu
> > > domain\n");
> > > + return PTR_ERR(sdhci_arasan->domain);
> > > + }
> > > +
> > > + iommu_attach_device(sdhci_arasan->domain, &pdev->dev);
> > > +#endif
> > > +
> >
> > Device drivers should never care about the implementation details
> > of the iommu. Please change the code to use the regular dma_map_*
> > interfaces that will work both with and without IOMMU.
>
> After refer to iommu binding , there is a service that allows "Remap
> address space to allow devices to access physical memory ranges that
> they otherwise wouldn't be capable of accessing." eg : 32-bit to 64
> bit DMA .
>
> So do we have any existing driver that uses this service ? Just asking
> for suggestions.
The interface is completely transparent to device drivers, it is
implemented as a separate 'struct dma_map_ops' that is normally
architecture independent, and that handles all sorts of DMA remapping
issues for the driver, including
- address space limits
- offsets between CPU and device addresses for the same memory
- cache flushes
- bus-level synchronization
On arm32, we currently support six sets of dma_map_ops including
two for IOMMU (coherent and noncoherent). On arm64, we currently
always use swiotlb, which solves your problem by copying memory to
bounce buffers. This is rather inefficient, and a new implementation
is being worked on, based on the arm32 implementation to support
IOMMUs in a generic way.
Arnd
next prev parent reply other threads:[~2015-01-06 13:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 17:01 [PATCH 0/2] Add SDHCI support for APM X-Gene SoC using ARASAN SDHCI controller Suman Tripathi
[not found] ` <1418662867-9210-1-git-send-email-stripathi-qTEPVZfXA3Y@public.gmane.org>
2014-12-15 17:01 ` [PATCH 1/2] mmc: host: arasan: Add addition of-arasan quirks and add IOMMU support Suman Tripathi
2014-12-15 21:27 ` Arnd Bergmann
2015-01-06 11:40 ` Suman Tripathi
2015-01-06 13:55 ` Arnd Bergmann [this message]
2014-12-15 17:01 ` [PATCH 2/2] arm64: dts: Add APM X-Gene SDHCI DTS node Suman Tripathi
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=3924494.iNyoV2USme@wuerfel \
--to=arnd@arndb.de \
--cc=anton@enomsg.org \
--cc=chris@printf.net \
--cc=ddutile@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=jcm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=patches@apm.com \
--cc=stripathi@apm.com \
/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).