linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Peter Meerwald <pmeerw@pmeerw.net>,
	Daniel Mack <zonque@gmail.com>,
	Jarkko Nikula <jarkko.nikula@bitmer.com>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	alsa-devel@alsa-project.org, linux-omap@vger.kernel.org
Subject: Re: [alsa-devel] channel swapping issue on OMAP3/TWL4030 is back
Date: Mon, 25 Mar 2013 13:39:29 +0100	[thread overview]
Message-ID: <51504581.10400@ti.com> (raw)
In-Reply-To: <20130322163506.GL30923@n2100.arm.linux.org.uk>

On 03/22/2013 05:35 PM, Russell King - ARM Linux wrote:
> On Fri, Mar 22, 2013 at 02:04:42PM +0100, Peter Ujfalusi wrote:
>> Russell: can we remove the tasklet use from dma-omap and start the DMA right
>> away in omap_dma_issue_pending()? This is the only way to prevent channel
>> swap when starting audio.
> 
> What I fear is that we may run up against having too many DMA channels
> tied up to the peripherals.  I structured the driver in this way to
> allow us to move the physical DMA channel allocation to that tasklet
> when that becomes a problem.
> 
> Not only that but I was hoping to lift some more of this code out of
> DMA engine drivers, so DMA engine drivers had even less code in them.

Not sure what you mean by this. Move dmaengine core's issue_pending to a
tasklet or is only OMAP internal restructuring?

> I guess we could keep the tasklet, but mark the audio DMA channels as
> "pre-reserved" and arrange for pre-reserved channels to avoid the
> tasklet, rather than throwing the tasklet out completely.

Not sure if we really want to pre-reserve the DMA channels for audio:
on OMAP3 we have 5 McBSP -> 10 DMA channels
on OMAP4 we have 4 McBSP, one McPDM, one DMIC and one McASP + we have the
AESS/ABE -> 8 + 2 + 1 + 1 + 8 (AESS/ABE).
Do we really want to pre-allocate DMA channel for all of these?

We could look omap_chan.cyclic which gives good indication that the channel is
used for audio since only audio is using cyclic mode.

I have a patch which removes the tasklet from omap-dma.c and it is working
fine on my systems (OMAP3 Zoom2, BeagleBoard, OMAP4 PandBoard, OMAP4 Blaze).

I can modify it to not remove the taskelt, but when the omap_chan.cyclic is
true we would instead of starting the tasklet we just start the DMA right away.

-- 
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-03-25 12:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22  8:48 channel swapping issue on OMAP3/TWL4030 is back Peter Meerwald
2013-03-22  8:55 ` [alsa-devel] " Daniel Mack
2013-03-22  9:03   ` Peter Meerwald
2013-03-22  9:07     ` Daniel Mack
2013-03-22  9:56 ` Peter Meerwald
2013-03-22 10:11   ` Daniel Mack
2013-03-22 12:49     ` Peter Meerwald
2013-03-22 13:04       ` Peter Ujfalusi
2013-03-22 16:35         ` Russell King - ARM Linux
2013-03-25 12:39           ` Peter Ujfalusi [this message]
2013-03-25 17:15             ` Russell King - ARM Linux
2013-03-26  9:52               ` Peter Ujfalusi

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=51504581.10400@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jarkko.nikula@bitmer.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=pmeerw@pmeerw.net \
    --cc=zonque@gmail.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).