From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: alsa-devel@alsa-project.org,
Stephen Warren <swarren@wwwdotorg.org>,
Vinod Koul <vinod.koul@intel.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Sebastien Guiriec <s-guiriec@ti.com>,
Markus Pargmann <mpa@pengutronix.de>,
Shawn Guo <shawn.guo@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] ASoC: dmaengine_pcm: support generic DMA binding users
Date: Fri, 22 Mar 2013 11:30:56 +0000 [thread overview]
Message-ID: <20130322113056.GA4977@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <514B34AB.1080107@metafoo.de>
On Thu, Mar 21, 2013 at 05:26:19PM +0100, Lars-Peter Clausen wrote:
> The problem with the current library is that we don't know yet which
> dmaengine device is going to be used by the time we pre-allocate the
> audio buffers, since the DMA filter parameters often are provided by
> the DAI driver.
That's not really a problem. The CPU DAI can provide the data via
the playback_dma_data and capture_dma_data pointers, which the ASoC
DMA engine driver can pick up on when it initializes. This data can
contain everything that the ASoC DMA engine driver needs.
Where my driver falls down is if you need to reconfigure the DMA engine
later - it doesn't provide an API for that, but that's trivially easy
to augment the API.
If you want to look at what I did for sa11x0 Assabet platforms, it's
still all here:
http://ftp.arm.linux.org.uk/git/gitweb.cgi?p=linux-arm.git;a=shortlog;h=2f03d47
As you will see from the dates, it's over a year old now - the only
thing I do with it is occasionally rebase it to bring it up to a more
modern kernel.
next prev parent reply other threads:[~2013-03-22 11:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 3:36 [PATCH 0/2] ASoC: dmaengine_pcm: support generic DMA binding users Shawn Guo
2013-03-15 3:36 ` [PATCH 1/2] dmaengine: add const for name parameter Shawn Guo
2013-03-15 8:53 ` Markus Pargmann
2013-03-21 9:47 ` Vinod Koul
2013-03-21 13:10 ` Markus Pargmann
2013-03-21 12:54 ` Vinod Koul
2013-03-21 14:45 ` [PATCH] DMA: of: const name fixup Markus Pargmann
2013-03-21 14:57 ` [PATCH 1/2] dmaengine: add const for name parameter Shawn Guo
2013-04-02 17:51 ` Vinod Koul
2013-04-02 19:47 ` Mark Brown
2013-03-15 3:36 ` [PATCH 2/2] ASoC: dmaengine_pcm: add snd_dmaengine_generic_pcm_open() Shawn Guo
2013-03-15 10:00 ` Sebastien Guiriec
2013-03-21 9:57 ` Vinod Koul
2013-03-21 14:53 ` Shawn Guo
2013-03-22 8:07 ` Sebastien Guiriec
2013-03-22 8:39 ` Shawn Guo
2013-03-21 2:39 ` [PATCH 0/2] ASoC: dmaengine_pcm: support generic DMA binding users Shawn Guo
2013-03-21 15:06 ` Lars-Peter Clausen
2013-03-21 15:22 ` Mark Brown
2013-03-21 16:26 ` Lars-Peter Clausen
2013-03-21 16:47 ` Mark Brown
2013-03-22 11:30 ` Russell King - ARM Linux [this message]
2013-03-22 11:39 ` Lars-Peter Clausen
2013-03-22 11:17 ` Russell King - ARM Linux
2013-03-22 11:28 ` Mark Brown
2013-03-22 11:42 ` Lars-Peter Clausen
2013-03-22 11:48 ` 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=20130322113056.GA4977@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mpa@pengutronix.de \
--cc=s-guiriec@ti.com \
--cc=shawn.guo@linaro.org \
--cc=swarren@wwwdotorg.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).