All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Christoph Hellwig <hch@infradead.org>,
	David Miller <davem@davemloft.net>,
	mroos@linux.ee, linux-kernel@vger.kernel.org
Subject: Re: libata & no PCI: dma_[un]map_single undefined
Date: Tue, 5 Jun 2007 09:56:08 -0400	[thread overview]
Message-ID: <20070605135608.GA31565@havoc.gtf.org> (raw)
In-Reply-To: <20070605122218.410d611b@the-village.bc.nu>

On Tue, Jun 05, 2007 at 12:22:18PM +0100, Alan Cox wrote:
> > NAK
> > 
> > We have generic devices and generic DMA mapping.  libata already uses
> > the generic stuff.  Now fix the platform...
> 
> Nice theory but your generic helpers rely on the map functions working
> even for generic hardware that doesn't need them, so at the very least
> there is some clean up required.

Sure there is some clean up needed -- on the arch side.

Even !PCI dma_xxx wrappers that do nothing more than return a dma
mapping error are a valid platform implementation.

Even !HAS_DMA (s/390?) arches should be using the aforementioned
return-error wrappers, mimicing the implementation of PCI functions
in linux/pci.h for the !PCI case.

libata core for DMA mapping is already generic enough such that, #ifdefs
are not needed in the code.


OTOH.....  further work in libata _is_ need for I/O accessors, to
isolate those from the core code.

	Jeff




  reply	other threads:[~2007-06-05 13:56 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-03 20:23 libata & no PCI: dma_[un]map_single undefined Meelis Roos
2007-06-04  0:40 ` David Miller
2007-06-04  7:47   ` Christoph Hellwig
2007-06-04 17:19     ` Jeff Garzik
2007-06-05 11:22       ` Alan Cox
2007-06-05 13:56         ` Jeff Garzik [this message]
2007-06-05 14:17           ` Russell King
2007-06-05 14:25             ` Jeff Garzik
2007-06-05 14:35             ` Jeff Garzik
2007-06-05 14:51               ` Russell King
2007-06-05 14:56                 ` Jeff Garzik
2007-06-05 14:59                   ` Russell King
2007-06-05 15:11                     ` Jeff Garzik
2007-06-05 15:18                       ` Russell King
2007-06-05 15:21                         ` Russell King
2007-06-05 19:27                           ` David Miller
2007-06-05 21:25                             ` Russell King
2007-06-05 21:38                               ` Russell King
2007-06-05 21:48                                 ` Jeff Garzik
2007-06-05 22:03                                   ` Russell King
2007-06-05 22:16                                     ` Jeff Garzik
2007-06-06  0:25                                       ` Valdis.Kletnieks
2007-06-05 15:41                         ` Jeff Garzik
2007-06-05 15:45                           ` Russell King
2007-06-05 19:27                         ` David Miller
2007-06-05 19:24                       ` David Miller
2007-06-05 21:10                         ` Chuck Ebbert
2007-06-05 19:23                     ` David Miller
2007-06-05 21:20                       ` Russell King
2007-06-05 15:50             ` Alan Cox
2007-06-05 15:52               ` Russell King
2007-06-04  7:54   ` Geert Uytterhoeven
2007-06-04 13:30   ` Alan Cox
2007-06-04 21:22     ` David Miller
2007-06-05  0:56       ` William Lee Irwin III
2007-06-05 11:12         ` Alan Cox

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=20070605135608.GA31565@havoc.gtf.org \
    --to=jeff@garzik.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@davemloft.net \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.