From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Hiroshi Doyu <hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: "will.deacon-5wv7dgnIgG8@public.gmane.org"
<will.deacon-5wv7dgnIgG8@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"Catalin.Marinas-5wv7dgnIgG8@public.gmane.org"
<Catalin.Marinas-5wv7dgnIgG8@public.gmane.org>,
"linaro-mm-sig-cunTk1MwBs8s++Sfvej+rw@public.gmane.org"
<linaro-mm-sig-cunTk1MwBs8s++Sfvej+rw@public.gmane.org>,
"iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
"m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org"
<m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: DMA mapping API(IOMMU) for ARM64?
Date: Tue, 18 Jun 2013 14:51:50 +0200 [thread overview]
Message-ID: <201306181451.50820.arnd@arndb.de> (raw)
In-Reply-To: <20130618.140137.1551430695673122122.hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On Tuesday 18 June 2013, Hiroshi Doyu wrote:
> I'm guessing that this kind of unification usually takes some time
> since we need to factor out the common code from the different
> ${ARCH}/mm/dma-mapping.c. Also some of ${ARCH} has IOMMU support in
> it. So if we want to develop our 64-bit ARM with working DMA mapping
> API during this transition, the step to take would be:
>
> 1, Copy arch/arm/mm/dma-mapping.c arch/arm64/mm/dma-mapping.c(+swiotlb)
Please don't.
> 2, Adapt arch/arm64/mm/dma-mapping.c(+swiotlb) to 64bit compatible.
> 3, Factor out the common code from them into mm/dma-mapping.c
I would suggest moving the ARM dma-mapping.c code to /mm or /lib
right away and then generalizing it there. Whoever wants to add
support for their architecture can modify the code to add whatever
changes they require.
Arnd
prev parent reply other threads:[~2013-06-18 12:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130618.053955.305832937374936961.hdoyu@nvidia.com>
[not found] ` <20130618101914.GB3539@mudshark.cambridge.arm.com>
[not found] ` <5159282.rrJMaZuYMv@wuerfel>
2013-06-18 11:01 ` DMA mapping API(IOMMU) for ARM64? Hiroshi Doyu
2013-06-18 12:50 ` Catalin Marinas
[not found] ` <20130618125054.GL9930-5wv7dgnIgG8@public.gmane.org>
2013-06-18 14:15 ` Arnd Bergmann
[not found] ` <201306181615.27341.arnd-r2nGTMty4D4@public.gmane.org>
2013-06-18 15:20 ` Hiroshi Doyu
2013-06-19 9:29 ` Marek Szyprowski
2013-06-18 22:08 ` Don Dutile
[not found] ` <51C0DA4F.1010405-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-06-19 11:11 ` Catalin Marinas
[not found] ` <20130618.140137.1551430695673122122.hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-06-18 12:51 ` Arnd Bergmann [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=201306181451.50820.arnd@arndb.de \
--to=arnd-r2ngtmty4d4@public.gmane.org \
--cc=Catalin.Marinas-5wv7dgnIgG8@public.gmane.org \
--cc=hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linaro-mm-sig-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@public.gmane.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