linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Documentation: dmaengine: Add a documentation for the dma controller API
Date: Tue, 19 Aug 2014 20:27:34 +0530	[thread overview]
Message-ID: <20140819145734.GN13288@intel.com> (raw)
In-Reply-To: <20140819144423.GE30401@n2100.arm.linux.org.uk>

On Tue, Aug 19, 2014 at 03:44:23PM +0100, Russell King - ARM Linux wrote:
> On Tue, Aug 19, 2014 at 07:15:07PM +0530, Vinod Koul wrote:
> > On Thu, Aug 14, 2014 at 09:57:53AM +0100, Russell King - ARM Linux wrote:
> > > It's got something to do with the async engine API, and seems to be
> > > something to do with whether a descriptor can have other transactions
> > > added to it, and whether a descriptor can be re-used (async-tx engines
> > > typically allocate a fixed set of descriptors and recycle them.)
> > Yes this is my understanding too. Async API IIUC can reuse descriptors and
> > if engine doesnt support this is a way to tell them please do use that.
> > 
> > For slave dmanegine API we need to ignore it.
> 
> We shouldn't ignore it - ignoring it makes it harder to implement a DMA
> engine driver which supports both the slave and async APIs, because
> we then need to know the reason for the channel being requested.
Do you have such usage coming up near future :)
> 
> Ignoring it until it can be understood and documented is an approach I
> would agree with though.
Certainly, I am asking Dan to add more clarity on these bits to help
improve.

-- 
~Vinod

      reply	other threads:[~2014-08-19 14:57 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30 16:03 [PATCH] Documentation: dmaengine: Add a documentation for the dma controller API Maxime Ripard
2014-07-30 16:06 ` Vinod Koul
2014-07-31  7:44   ` Maxime Ripard
2014-07-31 11:56     ` Vinod Koul
2014-07-31 16:23       ` Maxime Ripard
2014-08-01 17:13         ` Vinod Koul
2014-08-02 14:49           ` Maxime Ripard
2014-08-02 15:17             ` Russell King - ARM Linux
2014-08-02 19:06               ` Maxime Ripard
2014-08-05 16:25             ` Vinod Koul
2014-07-31 12:44     ` Lars-Peter Clausen
2014-07-31 16:13       ` Maxime Ripard
2014-07-31 16:54         ` Lars-Peter Clausen
2014-07-31 17:37           ` Maxime Ripard
2014-08-01  8:00             ` Lars-Peter Clausen
2014-08-01  8:57               ` Maxime Ripard
2014-08-01 17:15                 ` Vinod Koul
2014-08-01 18:09                   ` Lars-Peter Clausen
2014-08-02 15:13                     ` Maxime Ripard
2014-08-04  7:16                       ` Lars-Peter Clausen
2014-07-31 13:22     ` Russell King - ARM Linux
2014-07-31 16:41       ` Maxime Ripard
2014-08-01 14:53         ` Russell King - ARM Linux
2014-08-02 15:11           ` Maxime Ripard
2014-08-02 15:29             ` Russell King - ARM Linux
2014-08-02 19:05               ` Maxime Ripard
2014-08-01 17:22       ` Vinod Koul
2014-08-05  8:16 ` Geert Uytterhoeven
2014-08-14  8:53 ` Ludovic Desroches
2014-08-14  8:57   ` Russell King - ARM Linux
2014-08-19 13:45     ` Vinod Koul
2014-08-19 14:44       ` Russell King - ARM Linux
2014-08-19 14:57         ` Vinod Koul [this message]

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=20140819145734.GN13288@intel.com \
    --to=vinod.koul@intel.com \
    --cc=linux-arm-kernel@lists.infradead.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).