From: Remi Machet <rmachet@slac.stanford.edu>
To: Linux PPC <linuxppc-dev@ozlabs.org>
Subject: [PATCH 0/3] powerpc: dma code cleanup
Date: Tue, 07 Oct 2008 14:03:53 -0700 [thread overview]
Message-ID: <1223413433.17585.26.camel@pcds-ts102.slac.stanford.edu> (raw)
Hi,
Following is the whole DMA code cleanup on top of the work
already done by Becky Bruce. It includes removing __dma_sync
and __dma_sync_page that got replaced by dma_mapping_ops->sync,
getting rid of the old dma-noncoherent code which is now another
type of dma_mapping_ops and cleaning up the dma non-coherent
code by removing the virtual address pool it was using.
This code was tested on a 32bits PowerPC C2K board (noncoherent
cache) and I verified it builds on pmac32 (coherent cache, 32bits)
and pseries (64bits).
If anyone would be willing to test this code on other platforms
(mainly ones with non-coherent DMA architectures), I would
greatly appreciate!
Thanks,
Remi
next reply other threads:[~2008-10-07 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 21:03 Remi Machet [this message]
2008-10-08 6:30 ` [PATCH 0/3] powerpc: dma code cleanup Kumar Gala
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=1223413433.17585.26.camel@pcds-ts102.slac.stanford.edu \
--to=rmachet@slac.stanford.edu \
--cc=linuxppc-dev@ozlabs.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).