From: Vinod Koul <vinod.koul@intel.com>
To: Dan Williams <djbw@fb.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.jf.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Li Yang <leoli@freescale.com>,
Zhang Wei <zw@melbourneit.hotkeysparking.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Stephen Warren <swarren@wwwdotorg.org>,
linux-tegra@vger.kernel.org, Shawn Guo <shawn.guo@linaro.org>
Subject: Re: [PATCH 00/12] dma: various minor clean ups for slave drivers
Date: Mon, 15 Jul 2013 15:03:43 +0530 [thread overview]
Message-ID: <20130715093343.GN16653@intel.com> (raw)
In-Reply-To: <CAA9_cmdNiLfJjv-8Mh-Xb1ifZb4aw_9NGCVW6aWsfq6BN-DYyQ@mail.gmail.com>
On Fri, May 31, 2013 at 05:09:51PM -0700, Dan Williams wrote:
> On Thu, May 30, 2013 at 10:47 AM, Vinod Koul <vinod.koul@intel.com> wrote:
> > On Mon, May 27, 2013 at 03:14:30PM +0300, Andy Shevchenko wrote:
> >> Here is a set of small independent patches that clean up or fix minor things
> >> across DMA slave drivers.
> > The series looks fine. I am going to wait a day more and apply, pls speak up if
> > you disagree and ack if you agree
>
> Looks ok to me. Reminds we can probably take this one step further
> and provide a generic implementation for the common case. It's just a
> bit inconsistent though that some engines will poll the completion
> handler (try to advance the state of the last completed cookie)
> whereas others just assume things will be completed asynchronously.
agree with that. These are the inconsistencies some of which are based on
hardware and some are user iterpretations...
--
~Vinod
next prev parent reply other threads:[~2013-07-15 10:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 12:14 [PATCH 00/12] dma: various minor clean ups for slave drivers Andy Shevchenko
2013-05-27 12:14 ` [PATCH 01/12] imx-sdma: remove useless variable Andy Shevchenko
2013-05-27 12:14 ` [PATCH 02/12] mxs-dma: " Andy Shevchenko
2013-05-27 12:14 ` [PATCH 03/12] edma: no need to assign residue to 0 explicitly Andy Shevchenko
2013-05-27 12:14 ` [PATCH 04/12] ep93xx_dma: remove useless use of lock Andy Shevchenko
2013-05-27 12:14 ` [PATCH 05/12] fsldma: " Andy Shevchenko
2013-05-27 12:14 ` [PATCH 06/12] mmp_pdma: " Andy Shevchenko
2013-05-27 12:14 ` [PATCH 07/12] mpc512x_dma: " Andy Shevchenko
2013-05-27 12:14 ` [PATCH 08/12] pch_dma: " Andy Shevchenko
2013-05-27 12:14 ` [PATCH 09/12] tegra20-apb-dma: " Andy Shevchenko
2013-05-29 10:56 ` Laxman Dewangan
2013-05-29 13:42 ` Andy Shevchenko
2013-05-27 12:14 ` [PATCH 10/12] ipu_idmac: re-use dma_cookie_status() Andy Shevchenko
2013-05-29 2:19 ` Shawn Guo
2013-05-27 12:14 ` [PATCH 11/12] mmp_tdma: set cookies as well when asked for tx status Andy Shevchenko
2013-05-27 12:14 ` [PATCH 12/12] txx9dmac: return DMA_SUCCESS immediately from device_tx_status() Andy Shevchenko
2013-05-30 17:47 ` [PATCH 00/12] dma: various minor clean ups for slave drivers Vinod Koul
2013-05-30 18:32 ` Andy Shevchenko
2013-07-15 9:37 ` Vinod Koul
2013-07-15 10:21 ` Andy Shevchenko
2013-07-15 9:59 ` Vinod Koul
2013-06-01 0:09 ` Dan Williams
2013-07-15 9:33 ` Vinod Koul [this message]
2013-07-10 7:54 ` Andy Shevchenko
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=20130715093343.GN16653@intel.com \
--to=vinod.koul@intel.com \
--cc=andriy.shevchenko@linux.jf.intel.com \
--cc=djbw@fb.com \
--cc=leoli@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=shawn.guo@linaro.org \
--cc=swarren@wwwdotorg.org \
--cc=zw@melbourneit.hotkeysparking.com \
/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