From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Arnd Bergmann <arnd@arndb.de>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH] asm-generic: add dma-mapping-linear.h
Date: Mon, 1 Jun 2009 11:43:53 +0100 [thread overview]
Message-ID: <20090601104353.GA25391@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200906011128.10670.arnd@arndb.de>
On Mon, Jun 01, 2009 at 11:28:09AM +0100, Arnd Bergmann wrote:
> On Monday 01 June 2009, Russell King wrote:
> > On Mon, Jun 01, 2009 at 05:08:09PM +0900, FUJITA Tomonori wrote:
> > > This adds a version of the dma-mapping API to asm-generic that can be
> > > used by most architectures that only need a linear mapping.
> >
> > It depends what is meant by "linear mapping".
> >
> > If that's just a way of saying "all that needs to be done for the
> > DMA streaming APIs is to flush the cache" then the vast majority of
> > ARMs fall into that category.
>
> Right. You can probably split out the arm dma-mapping.h implementation
> into the dmabounce version and a version that falls back to my
> asm-generic code.
>
> One feature that the arm code currently has that I'm still missing is
> highmem support, which seems to be relatively complex in arm
> (three different implementations). Not sure how to best fit that in there.
Err - there's only one highmem implementation on ARM.
Anyway, as I hinted, things in this area will most likely become more
complex in the near future, so any unification of the ARM dma-mapping
will have to be undone.
Let's wait for the ARMv7 support to mature before trying to unify too
much.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2009-06-01 10:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 20:04 [PATCH] asm-generic: add dma-mapping-linear.h Arnd Bergmann
2009-06-01 4:02 ` FUJITA Tomonori
2009-06-01 7:51 ` Russell King
2009-06-01 8:08 ` FUJITA Tomonori
2009-06-01 8:29 ` Russell King
2009-06-01 8:29 ` Russell King
2009-06-01 9:16 ` FUJITA Tomonori
2009-06-01 9:22 ` Russell King
2009-06-01 9:32 ` FUJITA Tomonori
2009-06-01 10:14 ` Russell King
2009-06-01 10:41 ` Arnd Bergmann
2009-06-01 10:58 ` Russell King
2009-06-01 11:42 ` Arnd Bergmann
2009-06-01 10:28 ` Arnd Bergmann
2009-06-01 10:43 ` Russell King [this message]
2009-06-01 10:48 ` Arnd Bergmann
2009-06-01 10:11 ` Arnd Bergmann
2009-06-01 13:08 ` Michal Simek
2009-06-01 16:45 ` Arnd Bergmann
2009-06-02 11:11 ` Michal Simek
2009-06-04 7:57 ` FUJITA Tomonori
2009-06-04 12:35 ` Arnd Bergmann
2009-06-04 12:51 ` Russell King
2009-06-04 13:42 ` Arnd Bergmann
2009-06-04 14:38 ` Russell King
2009-06-04 14:49 ` Russell King
2009-06-04 16:29 ` Arnd Bergmann
2009-06-04 15:05 ` FUJITA Tomonori
2009-06-04 16:47 ` Arnd Bergmann
2009-06-04 20:11 ` Geert Uytterhoeven
2009-06-08 5:49 ` FUJITA Tomonori
2009-06-08 8:03 ` Arnd Bergmann
2009-06-08 8:23 ` FUJITA Tomonori
2009-06-08 8:49 ` Arnd Bergmann
2009-06-08 8:49 ` Arnd Bergmann
2009-06-04 12:45 ` Russell King
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=20090601104353.GA25391@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=arnd@arndb.de \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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