From: Lars-Peter Clausen <lars@metafoo.de>
To: "Fernandes, Joel" <joelf@ti.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: Query on Audio DMA using DMAEngine
Date: Sun, 30 Jun 2013 14:06:09 +0200 [thread overview]
Message-ID: <51D01F31.3010602@metafoo.de> (raw)
In-Reply-To: <083BC63EECB6FD41B8E81CF7FD87CC0F2E4F1488@DLEE08.ent.ti.com>
Added alsa-devel to Cc.
On 06/28/2013 05:27 AM, Fernandes, Joel wrote:
> Hi Lars,
>
> Hope you are doing well.
>
> I am implementing Cyclic DMA support in the EDMA driver that is used by Davinci and now newer TI SoCs.
> I am thinking once I am done I can plug it into the snd_dmaengine framework.
>
> Currently however, the davinci-pcm code directly programs the EDMA. That is what I am working to replace with a single driver and adapt to the snd dmaengine framework. However, once the current code in davinci-pcm uses internal RAM as an intermediate step in the whole DMA process (First data is TX to IRAM from DRAM and then from DRAM to the audio device).
>
> Do you have any ideas on how we can adapt to the framework, such that we can till use the IRAM? Are there any existing implementations out there that do something similar?
Hm, I guess using the snd_dmaengine_pcm helper functions here shouldn't be too
hard. Using the generic snd_dmaengine_pcm driver will require some extensions
to it though. The mmp platform (pxa/mmp-pcm.c) is also using some kind of
on-chip memory, so having support for this in the generic driver certainly
makes sense. For the chaining you'd probably have to extend the dmaengine
framework, since this kind of interleaved mem-to-mem and mem-to-dev cyclic
transfer is currently not possible.
I'm wondering though why do you need to copy the data to RAM first, is it not
possible to map the IRAM to userspace?
- Lars
next parent reply other threads:[~2013-06-30 12:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <083BC63EECB6FD41B8E81CF7FD87CC0F2E4F1488@DLEE08.ent.ti.com>
2013-06-30 12:06 ` Lars-Peter Clausen [this message]
2013-07-01 6:10 ` Query on Audio DMA using DMAEngine Mike Looijmans
2013-07-02 1:28 ` Joel Fernandes
2013-07-02 6:02 ` Mike Looijmans
2013-07-02 12:16 ` Mark Brown
2013-07-02 13:30 ` Mike Looijmans
2013-07-02 14:58 ` Mark Brown
2013-07-04 11:00 ` Clemens Ladisch
2013-07-02 3:33 ` Joel Fernandes
2013-07-02 5:50 ` Mike Looijmans
2013-07-02 12:13 ` Mark Brown
2013-07-02 13:40 ` Mike Looijmans
2013-07-03 9:09 ` Lars-Peter Clausen
2013-07-03 9:43 ` Mark Brown
2013-07-03 13:17 ` Mike Looijmans
[not found] ` <51D4245F.8070307-Oq418RWZeHk@public.gmane.org>
2013-07-03 19:56 ` Joel Fernandes
[not found] ` <20130703094307.GE27646-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-07-03 17:55 ` [alsa-devel] " Joel Fernandes
[not found] ` <51D46598.6070005-l0cyMroinI0@public.gmane.org>
2013-07-03 18:12 ` Mark Brown
2013-07-04 5:56 ` Mike Looijmans
2013-07-04 10:49 ` Mark Brown
2013-07-03 18:18 ` [alsa-devel] " Joel Fernandes
2013-07-04 6:06 ` Mike Looijmans
2013-07-04 10:53 ` Mark Brown
[not found] ` <51D510EA.1030809-Oq418RWZeHk@public.gmane.org>
2013-07-04 10:59 ` [alsa-devel] " Sekhar Nori
2013-08-14 4:30 ` Joel Fernandes
2013-08-14 4:53 ` Joel Fernandes
2013-08-14 14:10 ` Mike Looijmans
2013-08-14 12:06 ` Mark Brown
2013-07-02 1:04 ` Joel Fernandes
2013-07-03 9:07 ` Lars-Peter Clausen
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=51D01F31.3010602@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=joelf@ti.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.