From: Lars-Peter Clausen <lars@metafoo.de>
To: Mark Brown <broonie@kernel.org>
Cc: Vinod Koul <vinod.koul@intel.com>,
alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH v2 1/2] ASoC: dmaengine-pcm: Add support for querying DMA capabilities
Date: Wed, 16 Oct 2013 20:28:30 +0200 [thread overview]
Message-ID: <525EDACE.4050006@metafoo.de> (raw)
In-Reply-To: <20131016181057.GX2443@sirena.org.uk>
On 10/16/2013 08:10 PM, Mark Brown wrote:
> On Tue, Oct 08, 2013 at 03:07:59PM +0200, Lars-Peter Clausen wrote:
>> Currently each platform making use the the generic dmaengine PCM driver still
>> needs to provide a custom snd_pcm_hardware struct which specifies the
>> capabilities of the DMA controller, e.g. the maximum period size that can be
>> supported. This patch adds code which uses the newly introduced
>
> There was some discussion on this but it didn't seem terribly
> conclusive. Are people happy with these?
>
Was about to ask the same. I'm still happy with it.
- Lars
next prev parent reply other threads:[~2013-10-16 18:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 13:07 [PATCH v2 1/2] ASoC: dmaengine-pcm: Add support for querying DMA capabilities Lars-Peter Clausen
2013-10-08 13:08 ` [PATCH v2 2/2] ASoC: dmaengine-pcm: Provide default config Lars-Peter Clausen
2013-10-08 15:06 ` [PATCH v2 1/2] ASoC: dmaengine-pcm: Add support for querying DMA capabilities Vinod Koul
2013-10-08 16:13 ` Lars-Peter Clausen
2013-10-08 15:30 ` Vinod Koul
2013-10-08 16:40 ` Lars-Peter Clausen
2013-10-08 16:46 ` Mark Brown
2013-10-08 15:49 ` Mark Brown
2013-10-08 14:59 ` Vinod Koul
2013-10-16 18:10 ` Mark Brown
2013-10-16 18:28 ` Lars-Peter Clausen [this message]
2013-11-13 9:09 ` Vinod Koul
2013-10-19 20:27 ` 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=525EDACE.4050006@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=vinod.koul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.