public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Vinod Koul <vinod.koul@linux.intel.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>, vinod.koul@intel.com
Subject: Re: [alsa-devel] [PATCH 1/2] dma: Add a PAUSE_RESUME capability
Date: Thu, 30 May 2013 21:10:46 +0200	[thread overview]
Message-ID: <51A7A436.5040208@metafoo.de> (raw)
In-Reply-To: <1369932575.3890.18.camel@vkoul-udesk3>

On 05/30/2013 06:49 PM, Vinod Koul wrote:
> On Wed, 2013-05-29 at 13:42 +0200, Lars-Peter Clausen wrote:
>> 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.
> - This mail-list is not correct for this patch
> - use get_maintainer.pl, if you dont know but you already know!
> - always CC maintainers

Hm, I have no idea what happened with the Cc list. I might have hit the up key
one time to many after --dry-run, since this is the Cc list of a different
patch series.

> 
> the enum dma_transaction_type reports what kind of transactions DMA
> controller is capable of. This is not for capabilities of a given
> transaction type, so this approach is not right.

hm, ok.
> 
> Unfortunately, this is not supported by dmaengine atm. We had discussed
> this in last plumbers, and discussion with Matt was to add capability
> API (at least for slave usages). The work from Matt had reached a good
> point but unfortunately didn't reach its conclusion. [1]
> 
> Let me resurrect those patches and add the pause, resume query to it in
> more generic way

I've pinged Matt about these patches yesterday or so. He has been rather quite
lately, maybe he's been sucked into the Linaro blackhole.

- Lars


           reply	other threads:[~2013-05-30 19:07 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1369932575.3890.18.camel@vkoul-udesk3>]

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=51A7A436.5040208@metafoo.de \
    --to=lars@metafoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vinod.koul@intel.com \
    --cc=vinod.koul@linux.intel.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