From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Jarkko Nikula <jarkko.nikula@bitmer.com>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH 1/2] ASoC: omap-mcbsp: Use DMA packet mode for non mono streams on OMAP3+
Date: Fri, 16 Mar 2012 14:06:34 +0200 [thread overview]
Message-ID: <4F632CCA.5010407@ti.com> (raw)
In-Reply-To: <4F62E4FC.1020303@bitmer.com>
Hi Jarkko,
On 03/16/2012 09:00 AM, Jarkko Nikula wrote:
> Out of curiosity, I guess this will decrease a memory bus or DMA
> controller load a bit.
Yes it will slightly decrease the load on those. It will also decrease
the number of DMA requests going from McBSP to the sDMA controller.
> Can you see any difference with the SW tools
> (top, etc) under some system load or do you need some on-chip
> observability to be able to measure effect of this transfer pattern change?
I can not see difference between the old
element/packet-element/threshold mode from user space point of view.
I think the effect can be seen in an optimized system more.
The decreased load on SDRAM/sDMA should help with the performance, less
DMA request means less frequent activity, which should decrease power
consumption.
Other good thing might be is that now the DMA moves in sample steps, and
not in words.
--
Péter
next prev parent reply other threads:[~2012-03-16 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 10:37 [PATCH 0/2] ASoC: omap-mcbsp: dma_op_mode changes Peter Ujfalusi
2012-03-15 10:37 ` [PATCH 1/2] ASoC: omap-mcbsp: Use DMA packet mode for non mono streams on OMAP3+ Peter Ujfalusi
2012-03-16 7:00 ` Jarkko Nikula
2012-03-16 12:06 ` Peter Ujfalusi [this message]
2012-03-15 10:37 ` [PATCH 2/2] ASoC: omap-mcbsp: Remove unused FRAME dma_op_mode Peter Ujfalusi
2012-03-15 12:22 ` [PATCH 0/2] ASoC: omap-mcbsp: dma_op_mode changes Mark Brown
2012-03-16 6:29 ` Jarkko Nikula
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=4F632CCA.5010407@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jarkko.nikula@bitmer.com \
--cc=lrg@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.