From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: Dan Williams <dan.j.williams@intel.com>,
linux-fbdev-devel@lists.sourceforge.net,
linux-arm-kernel@lists.arm.linux.org.uk, adaplas@gmail.com
Subject: [PATCH 1/4 v5] dmaengine: add async_tx_clear_ack() macro
Date: Mon, 22 Dec 2008 19:31:48 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0812221927260.5241@axis700.grange> (raw)
In-Reply-To: <Pine.LNX.4.64.0812221922200.5241@axis700.grange>
From: Guennadi Liakhovetski <lg@denx.de>
To complete the DMA_CTRL_ACK handling API add a async_tx_clear_ack() macro.
Signed-off-by: Guennadi Liakhovetski <lg@denx.de>
---
No change since v2 or v3
include/linux/dmaengine.h | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h
index 64dea2a..c820a3f 100644
--- a/include/linux/dmaengine.h
+++ b/include/linux/dmaengine.h
@@ -287,6 +287,11 @@ static inline void async_tx_ack(struct dma_async_tx_descriptor *tx)
tx->flags |= DMA_CTRL_ACK;
}
+static inline void async_tx_clear_ack(struct dma_async_tx_descriptor *tx)
+{
+ tx->flags &= ~DMA_CTRL_ACK;
+}
+
static inline bool async_tx_test_ack(struct dma_async_tx_descriptor *tx)
{
return (tx->flags & DMA_CTRL_ACK) == DMA_CTRL_ACK;
--
1.5.4
------------------------------------------------------------------------------
next prev parent reply other threads:[~2008-12-22 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 18:31 [PATCH 0/4 v5] i.MX31: dmaengine and framebuffer drivers Guennadi Liakhovetski
2008-12-22 18:31 ` Guennadi Liakhovetski [this message]
2008-12-22 18:31 ` [PATCH 2/4 v5] i.MX31: Image Processing Unit DMA and IRQ drivers Guennadi Liakhovetski
2008-12-22 18:32 ` [PATCH 3/4 v5] i.MX31: framebuffer driver Guennadi Liakhovetski
2008-12-23 12:54 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2008-12-22 18:32 ` [PATCH 4/4 v5] 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.0812221927260.5241@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 \
/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