From: Lars-Peter Clausen <lars@metafoo.de>
To: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Scott Jiang <scott.jiang.linux@gmail.com>,
Steven Miao <realmz6@gmail.com>
Cc: uclinux-dist-devel@blackfin.uclinux.org,
alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>
Subject: [PATCH 1/2] dma: Add a PAUSE_RESUME capability
Date: Wed, 29 May 2013 13:42:22 +0200 [thread overview]
Message-ID: <1369827743-5533-1-git-send-email-lars@metafoo.de> (raw)
Add a capability which allows dmaengine consumers to query whether a dmaengine
controller supports the DMA_PAUSE and DMA_RESUME commands. Sometimes a user of
the dmaengine API needs to know in advance if a channel will support
pause/resume. E.g. in ALSA the information whether it is possible to
pause/resume a audio stream or whether it is necessary to abort and restart the
stream is communicated to userspace so it can act accordingly.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
---
include/linux/dmaengine.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h
index 96d3e4a..ad98dfb 100644
--- a/include/linux/dmaengine.h
+++ b/include/linux/dmaengine.h
@@ -74,6 +74,7 @@ enum dma_transaction_type {
DMA_SLAVE,
DMA_CYCLIC,
DMA_INTERLEAVE,
+ DMA_PAUSE_RESUME,
/* last transaction type for creation of the capabilities mask */
DMA_TX_TYPE_END,
};
--
1.8.0
next reply other threads:[~2013-05-29 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 11:42 Lars-Peter Clausen [this message]
[not found] ` <1369827743-5533-1-git-send-email-lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>
2013-05-29 11:42 ` [PATCH 2/2] dma: Set PAUSE_RESUME capability for drivers which support it Lars-Peter Clausen
2013-05-30 16:49 ` [PATCH 1/2] dma: Add a PAUSE_RESUME capability Vinod Koul
2013-06-01 19:00 ` Mark Brown
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=1369827743-5533-1-git-send-email-lars@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=realmz6@gmail.com \
--cc=scott.jiang.linux@gmail.com \
--cc=uclinux-dist-devel@blackfin.uclinux.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