From: Dan Williams <dan.j.williams@intel.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Li Yang <leoli@freescale.com>, Ira Snyder <iws@ovro.caltech.edu>
Subject: Re: [PATCH v3 2/2] fsldma: Add DMA_SLAVE support
Date: Wed, 24 Jun 2009 10:56:07 -0700 [thread overview]
Message-ID: <4A4268B7.8060106@intel.com> (raw)
In-Reply-To: <4A40FB26.8080301@intel.com>
Dan Williams wrote:
> Kumar Gala wrote:
>>>> Kumar, Leo,
>>>>
>>>> Can I get your acked-by's for the current state of async_tx.git/
>>>> next? I
>>>> just pushed out Ira's latest so it may take a moment to mirror out.
>>> Acked-by: Li Yang <leoli@freescale.com>
>>>
>>> However, the addition of arch/powerpc/include/asm/fsldma.h still needs
>>> the ack from Kumar. It doesn't seem to be a common practice though.
>> hmm, why are we moving fsldma.h?
>
> There are now two fsldma.h files.
>
> drivers/dma/fsldma.h: no changes, houses the private driver
> implementation details.
>
> arch/powerpc/include/asm/fsldma.h: adds some helper routines and
> definitions for the DMA_SLAVE capability of the driver. It defines an
> interface for other drivers to use fsldma to initiate device-to-memory
> dma. Any drivers that use the interface will depend on CONFIG_FSL_DMA
> hence placing this public header under arch/powerpc/include.
>
Kumar? Shall we push this decision off to 2.6.32, I would prefer not to
as Ira had his initial patches available before the merge window opened?
Ira, aside from the pci read multiple patch are there any others that
are suitable for 2.6.31 if the dma_slave implementation gets held back?
Thanks,
Dan
next prev parent reply other threads:[~2009-06-24 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 19:31 [PATCH v3 2/2] fsldma: Add DMA_SLAVE support Ira Snyder
2009-06-22 21:20 ` Dan Williams
2009-06-22 21:22 ` Dan Williams
2009-06-23 10:18 ` Li Yang
2009-06-23 12:56 ` Kumar Gala
2009-06-23 15:56 ` Dan Williams
2009-06-24 17:56 ` Dan Williams [this message]
2009-06-24 19:13 ` Kumar Gala
2009-06-24 21:08 ` Dan Williams
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=4A4268B7.8060106@intel.com \
--to=dan.j.williams@intel.com \
--cc=galak@kernel.crashing.org \
--cc=iws@ovro.caltech.edu \
--cc=leoli@freescale.com \
--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).