linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Remi Machet <rmachet@slac.stanford.edu>
Cc: Linux PPC <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] dma: add new dma_mapping_ops API sync_page
Date: Mon, 06 Oct 2008 11:30:04 -0500	[thread overview]
Message-ID: <48EA3D0C.1050107@freescale.com> (raw)
In-Reply-To: <1223051594.4251.12.camel@pcds-ts102.slac.stanford.edu>

Remi Machet wrote:
> After continuing to work on the dma noncoherent code I realized that
> sync_page is not the best choice of API: 
> -The API should preferably take a dma_addr_t in my opinion

A virtual address will typically be needed to perform the flush; why 
pass the bus address?

-Scott

  reply	other threads:[~2008-10-06 16:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 22:03 [PATCH] dma: add new dma_mapping_ops API sync_page Remi Machet
2008-10-03 16:33 ` Remi Machet
2008-10-06 16:30   ` Scott Wood [this message]
2008-10-06 17:38     ` Remi Machet
2008-10-10  3:46       ` Benjamin Herrenschmidt
2008-10-10 16:16         ` Remi Machet

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=48EA3D0C.1050107@freescale.com \
    --to=scottwood@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rmachet@slac.stanford.edu \
    /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).