mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: linux-fbdev-devel@lists.sourceforge.net, adaplas@gmail.com,
	Sascha Hauer <s.hauer@pengutronix.de>,
	linux-arm-kernel@lists.arm.linux.org.uk,
	Dan Williams <dan.j.williams@intel.com>
Subject: [PATCH 1/4 v2] dmaengine: add a tx_free method to struct dma_async_tx_descriptor
Date: Wed, 10 Dec 2008 11:36:03 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0812101129340.4578@axis700.grange> (raw)
In-Reply-To: <Pine.LNX.4.64.0812101122250.4578@axis700.grange>

From: Guennadi Liakhovetski <lg@denx.de>

Some users reuse DMA transaction descriptors multiple times and need an
explicit call to release them. An example of such a user is Video4Linux, which
has to be able to release descriptors on ioctl(VIDIOC_DQBUF).

Signed-off-by: Guennadi Liakhovetski <lg@denx.de>
---
 include/linux/dmaengine.h |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h
index 64dea2a..58b2268 100644
--- a/include/linux/dmaengine.h
+++ b/include/linux/dmaengine.h
@@ -183,6 +183,7 @@ typedef void (*dma_async_tx_callback)(void *dma_async_param);
  *	descriptors
  * @chan: target channel for this operation
  * @tx_submit: set the prepared descriptor(s) to be executed by the engine
+ * @tx_free: release a transaction descriptor
  * @callback: routine to call after this operation is complete
  * @callback_param: general parameter to pass to the callback routine
  * ---async_tx api specific fields---
@@ -197,6 +198,7 @@ struct dma_async_tx_descriptor {
 	struct list_head tx_list;
 	struct dma_chan *chan;
 	dma_cookie_t (*tx_submit)(struct dma_async_tx_descriptor *tx);
+	void (*tx_free)(struct dma_async_tx_descriptor *tx);
 	dma_async_tx_callback callback;
 	void *callback_param;
 	struct dma_async_tx_descriptor *next;
-- 
1.5.4


  reply	other threads:[~2008-12-10 10:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 10:35 [PATCH 0/4 v2] i.MX31: dmaengine and framebuffer drivers Guennadi Liakhovetski
2008-12-10 10:36 ` Guennadi Liakhovetski [this message]
2008-12-10 19:58   ` [PATCH 1/4 v2] dmaengine: add a tx_free method to struct dma_async_tx_descriptor Dan Williams
2008-12-11  0:30     ` Guennadi Liakhovetski
2008-12-11  2:01       ` Dan Williams
2008-12-11 15:55         ` Guennadi Liakhovetski
2008-12-11 16:43           ` Dan Williams
2008-12-11 16:56             ` Guennadi Liakhovetski
2008-12-10 10:36 ` [PATCH 2/4 v2] i.MX31: Image Processing Unit DMA and IRQ drivers Guennadi Liakhovetski
2008-12-10 13:26   ` Dmitry Krivoschekov
2008-12-10 13:49     ` Guennadi Liakhovetski
2008-12-10 10:36 ` [PATCH 3/4 v2] i.MX31: framebuffer driver Guennadi Liakhovetski
2008-12-10 16:23   ` Herring Robert
2008-12-10 16:47     ` Guennadi Liakhovetski
2008-12-11  1:32       ` Herring Robert
2008-12-10 10:36 ` [PATCH 4/4 v2] i.MX31: platform bindings and initialisation for IPU and framebuffer drivers Guennadi Liakhovetski

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=Pine.LNX.4.64.0812101129340.4578@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --cc=adaplas@gmail.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    /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

all inboxes | Powered by JetHome®