public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH] asm-generic: add dma-mapping-linear.h
Date: Mon, 8 Jun 2009 10:03:58 +0200	[thread overview]
Message-ID: <200906081003.59171.arnd@arndb.de> (raw)
In-Reply-To: <20090608144921R.fujita.tomonori@lab.ntt.co.jp>

On Monday 08 June 2009, FUJITA Tomonori wrote:
> 
> > However, I don't think I have the energy to fix this problem, but
> > I agree that it should be fixed eventually. I can leave out
> > the declarations of dma_{free,alloc}_coherent from dma-mapping-linear.h
> > so that the broken code remains in the architecture specific
> > files, and change all references to dma_cache_sync to something
> > else. The best I can think of is __dma_cache_sync() with the same
> > calling conventions as dma_cache_sync(). Does that make sense?
> 
> Sorry, but it doesn't make sense to me because __dma_cache_sync() hack
> is against the goal of dma-mapping-linear.h, having a clean, ideal,
> unified header file.

Do you have any other suggestion? The operation that an architecture
performs to synchronize the DMA buffer after a DMA is just not generic
and needs to have some name that we can call from the generic file.
Right now we use one of dma_cache_sync, frv_cache_wback_inv,
mn10300_dcache_flush_inv or consistent_sync for this and I was just
looking for a new internal name for this operation.

	Arnd <><

  reply	other threads:[~2009-06-08  8:04 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
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 [this message]
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=200906081003.59171.arnd@arndb.de \
    --to=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