From: Dong Aisheng <aisheng.dong@freescale.com>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
Russell King <linux@arm.linux.org.uk>, Mallon <rmallon@gmail.com>,
Liam Girdwood <lrg@ti.com>, Sascha Hauer <s.hauer@pengutronix.de>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Vinod Koul <vinod.koul@linux.intel.com>,
Ryan@alsa-project.org, Wolfram Sang <w.sang@pengutronix.de>,
Mika Westerberg <mika.westerberg@iki.fi>
Subject: Re: [RFC 00/10] ASoC: Introduce dmaengine pcm helper functions
Date: Wed, 22 Feb 2012 16:46:41 +0800 [thread overview]
Message-ID: <20120222084640.GI11087@shlinux2.ap.freescale.net> (raw)
In-Reply-To: <20120222081908.GB21820@S2101-09.ap.freescale.net>
On Wed, Feb 22, 2012 at 04:19:10PM +0800, Shawn Guo wrote:
> Nice consolidation ...
>
> On Tue, Feb 21, 2012 at 05:47:54PM +0100, Lars-Peter Clausen wrote:
> > This patch series introduces a new set of helper functions for dmaengine based
> > PCM drivers. Currently we have 6 different dmaengine based PCM drivers which are
> > all more or less similar in structure, but all have also individual requirements
Correct.
> > which can't easily be generalized. So that's why this series does not introduce
> > a generic dmaengine PCM driver but rather a set of helper functions which can be
> > used to implement the common bits between such dmaengine based PCM drivers.
> >
I once had the same thinking about it...
> I did not notice this patch on any list yet, so am not sure about
> Russell's plan about it. But it seems this series does not reach
> alsa-devel list either. (forgot?)
>
I'm also interested in this patch series.
However, i can not see it in the alsa-dev list....
Regards
Dong Aisheng
next prev parent reply other threads:[~2012-02-22 8:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1329842884-9757-1-git-send-email-lars@metafoo.de>
2012-02-22 8:19 ` [RFC 00/10] ASoC: Introduce dmaengine pcm helper functions Shawn Guo
2012-02-22 8:46 ` Dong Aisheng [this message]
2012-02-22 9:03 ` Russell King - ARM Linux
2012-02-22 10:50 ` Mark Brown
2012-02-22 11:20 ` Russell King - ARM Linux
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=20120222084640.GI11087@shlinux2.ap.freescale.net \
--to=aisheng.dong@freescale.com \
--cc=Ryan@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lars@metafoo.de \
--cc=linux@arm.linux.org.uk \
--cc=lrg@ti.com \
--cc=mika.westerberg@iki.fi \
--cc=rmallon@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
--cc=vinod.koul@linux.intel.com \
--cc=w.sang@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 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.