From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
alsa-devel@alsa-project.org, Huang Shijie <b32955@freescale.com>,
Vinod Koul <vinod.koul@intel.com>,
Marek Vasut <marek.vasut@gmail.com>,
Shawn Guo <shawn.guo@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 09/12] ASoC: dmaengine_pcm: support use of generic DMA helper
Date: Fri, 1 Mar 2013 18:23:22 +0800 [thread overview]
Message-ID: <20130301102320.GV25302@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201302272102.40811.arnd@arndb.de>
[-- Attachment #1.1: Type: text/plain, Size: 408 bytes --]
On Wed, Feb 27, 2013 at 09:02:40PM +0000, Arnd Bergmann wrote:
> I would actually prefer having a new API in the soc-dmaengine-pcm
> module, like
> static int dmaengine_pcm_request_slave_channel(struct dmaengine_pcm_runtime_data *prtd,
> struct device *dev, const char *id);
> For sound drivers that are fully converted to using DT, it would be
> a more natural interface to use IMHO.
Yes, please.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2013-03-01 10:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1361978748-25281-1-git-send-email-shawn.guo@linaro.org>
2013-02-27 15:25 ` [PATCH 09/12] ASoC: dmaengine_pcm: support use of generic DMA helper Shawn Guo
2013-02-27 21:02 ` Arnd Bergmann
2013-02-28 8:09 ` Shawn Guo
2013-03-01 10:23 ` Mark Brown [this message]
2013-03-04 8:37 ` Shawn Guo
2013-02-27 15:25 ` [PATCH 10/12] ASoC: mxs: move to use " Shawn Guo
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=20130301102320.GV25302@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=b32955@freescale.com \
--cc=fabio.estevam@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=shawn.guo@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).