From: troy.kisky@boundarydevices.com
To: Troy Kisky <troy.kisky@boundarydevices.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Nori Sekhar <nsekhar@ti.com>
Cc: "davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
"broonie@sirena.org.uk" <broonie@sirena.org.uk>
Subject: Re: [PATCH 4/4] ASoC: DaVinci: pcm, fix underrun by using sram
Date: Tue, 13 Jul 2010 14:01:00 -0500 [thread overview]
Message-ID: <51883.1279047660@boundarydevices.com> (raw)
BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; }
On Tue 13/07/10 6:00 AM , "Nori, Sekhar" nsekhar@ti.com sent:
Hi Troy,
On Tue, Nov 17, 2009 at 05:22:34, Troy Kisky wrote:
> Fix underruns by using dma to copy 1st to sram
> in a ping/pong buffer style and then copying from
> the sram to the ASP. This also has the advantage
> of tolerating very long interrupt latency on dma
> completion.
>
> Signed-off-by: Troy Kisky
[...]
> +static int request_ping_pong(struct snd_pcm_substream *substream,
> + struct davinci_runtime_data *prtd,
> + struct snd_dma_buffer *iram_dma)
> +{
> + dma_addr_t asp_src_ping;
> + dma_addr_t asp_dst_ping;
> + int link;
> + struct davinci_pcm_dma_params *dma_data = prtd->params;
> +
> + /* Request ram master channel */
> + link = prtd->ram_channel = edma_alloc_channel(EDMA_CHANNEL_ANY,
> + davinci_pcm_dma_irq, substream,
> + EVENTQ_1);
What is the reason for choosing EVENTQ_1 for this channel? EVENTQ_0
is already being used for ASP channel.
I imagine it will be much easier to tune the queue usage in the
system
if all of audio data was using the same queue.
I am working on a patch which lets platform specify the event queues
for audio DMA. I am not sure if I really need to make a provision
for
two different queues to be specified - that's why I ask.
Thanks,
Sekhar
The reason is so that the IRAM data can be fetched and used while
EVENTQ_1 fetches the next buffer of data from sdram into IRAM.
Troy
next reply other threads:[~2010-07-13 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 19:01 troy.kisky [this message]
[not found] ` <51883.1279047660-Q5RJGjKts06CY9SHAMCTRUEOCMrvLtNR@public.gmane.org>
2010-07-14 13:05 ` RE: [PATCH 4/4] ASoC: DaVinci: pcm, fix underrun by using sram Nori, Sekhar
2010-07-14 17:46 ` Troy Kisky
-- strict thread matches above, loose matches on Subject: below --
2009-11-16 23:52 [PATCH 1/4] ASoC: DaVinci: remove requirement that dma_params is 1st in structure Troy Kisky
2009-11-16 23:52 ` [PATCH 2/4] ASoC: DaVinci: i2s, reduce underruns by combining into 1 element Troy Kisky
2009-11-16 23:52 ` [PATCH 3/4] ASoC: DaVinci: pcm, rename variables in prep for ping/pong Troy Kisky
2009-11-16 23:52 ` [PATCH 4/4] ASoC: DaVinci: pcm, fix underrun by using sram Troy Kisky
[not found] ` <1258415554-31069-4-git-send-email-troy.kisky-Q5RJGjKts06CY9SHAMCTRUEOCMrvLtNR@public.gmane.org>
2010-07-13 11:00 ` Nori, Sekhar
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=51883.1279047660@boundarydevices.com \
--to=troy.kisky@boundarydevices.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@sirena.org.uk \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=nsekhar@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.