From: Roland Dreier <roland@topspin.com>
To: "Curtis, Allen" <Allen.Curtis@Thales-IFS.com>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: pci_unmap_single() and CONFIG_NOT_COHERENT_CACHE
Date: 09 May 2003 11:28:12 -0700 [thread overview]
Message-ID: <52el38km9v.fsf@topspin.com> (raw)
In-Reply-To: <FA06AA2C99BCD511951200005A99441001E3F16E@irvexch1.sextantifs.com>
Allen> I noticed in pci.h that pci_unmap_single() is a null
Allen> function. (essentially does nothing) Shouldn't is call
Allen> consistent_sync() so that flush_dcache_range() is called?
No, the cache invalidate or flush has to happen when pci_map_single()
is used. There's nothing to do after the DMA is done (which is when
pci_unmap_single() gets called).
- Roland
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-05-09 18:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 18:07 pci_unmap_single() and CONFIG_NOT_COHERENT_CACHE Curtis, Allen
2003-05-09 18:28 ` Roland Dreier [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-09 19:54 Curtis, Allen
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=52el38km9v.fsf@topspin.com \
--to=roland@topspin.com \
--cc=Allen.Curtis@Thales-IFS.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).