linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mpa@pengutronix.de (Markus Pargmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] dma: mxs-dma: Track number of irqs for callback
Date: Mon, 30 Sep 2013 14:43:33 +0200	[thread overview]
Message-ID: <20130930124333.GE4869@pengutronix.de> (raw)
In-Reply-To: <20130926192646.GR12758@n2100.arm.linux.org.uk>

On Thu, Sep 26, 2013 at 08:26:46PM +0100, Russell King - ARM Linux wrote:
> On Thu, Sep 26, 2013 at 05:06:35PM +0200, Markus Pargmann wrote:
> > Currently there is one tasklet scheduled for all interrupts between two
> > mxs_dma_tasklet calls for one channel. With more than one interrupts,
> > the tasklet is only called once.
> > 
> > Using low latency audio playback, can lead to problems. When using
> > sound/soc/soc-dmaengine-pcm.c, the dmaengine_pcm_dma_complete relies on
> > being called for each interrupt that occures. This function is the
> > callback which is called from the mxs-dma driver in mxs_dma_tasklet.
> > This can cause wrong position counters and can lead to a wrong DMA
> > buffer offset. In this situation the DMA engine and pcm lib may write
> > and read from the same buffer segment.
> 
> I've actually covered this before.  DMAengine drivers (or infact the
> entire system) makes no guarantees how many callbacks will happen for
> a cyclic DMA.  Think about what happens if you lose an interrupt because
> of USB taking a very long time to service your mouse (yes, that really
> happens.)
> 
> You will notice that the soc dmaengine layer has two pcm ops, one for
> implementations with residue reporting, which can cope with missed
> interrupts, and another for those which provide no residue.  I strongly
> recommend that you ensure that your DMAengine driver correctly reports
> the residue, and use the soc dmaengine driver in a mode which uses that
> rather than implementing these fragile schemes.
> 

Thanks, I didn't know about this before. I implemented correct residue
reporting for mxs-dma cyclic buffers and it works without this tasklet
callback loop now.

Regards,

Markus Pargmann


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2013-09-30 12:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-26 15:06 [PATCH 0/3] dma: mxs-dma bugfixes and cleanup Markus Pargmann
2013-09-26 15:06 ` [PATCH 1/3] dma: mxs-dma: Cleanup interrupt handler Markus Pargmann
2013-09-26 15:06 ` [PATCH 2/3] dma: mxs-dma: Track number of irqs for callback Markus Pargmann
2013-09-26 15:11   ` Marc Kleine-Budde
2013-09-26 19:26   ` Russell King - ARM Linux
2013-09-30 12:43     ` Markus Pargmann [this message]
2013-09-26 15:06 ` [PATCH 3/3] dma: mxs-dma: Pause channel while prep_dma_cyclic Markus Pargmann

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=20130930124333.GE4869@pengutronix.de \
    --to=mpa@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).