From: Louis Chauvet <louis.chauvet@bootlin.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Mark Brown <broonie@kernel.org>,
linux-sound@vger.kernel.org, dmaengine@vger.kernel.org,
alsa-devel@alsa-project.org, miquel.raynal@bootlin.com,
perex@perex.cz, tiwai@suse.com, lars@metafoo.de,
lgirdwood@gmail.com
Subject: Re: DMA Transfer Synchronization Issue in Out-of-Tree Sound Card Driver
Date: Fri, 24 May 2024 18:13:16 +0200 [thread overview]
Message-ID: <ZlC8nG0Vzxg9HFT2@localhost.localdomain> (raw)
In-Reply-To: <87msoiz94h.wl-tiwai@suse.de>
Le 22/05/24 - 07:52, Takashi Iwai a écrit :
> On Tue, 21 May 2024 20:32:59 +0200,
> Mark Brown wrote:
> >
> > On Tue, May 21, 2024 at 10:31:12AM +0200, Louis Chauvet wrote:
> >
> > > To address this DMA issue, I have created a patch [1] that guarantees the
> > > completion of the DMA transfer upon the return of xdma_synchronize. This
> > > means xdma_synchronize now sleeps, but looking at other drivers around it
> > > appears expected to be able to do so.
> >
> > You need to set the nonatomic flag for the PCM to allow this, the
> > default is that triggers run in atomic context.
>
> Right, that's a most straightforward solution. It implies that the
> period updates must be in non-atomic, i.e. use a threaded irq handler
> in most cases.
>
> If the synchronization is needed for assuring the hardware stop, there
> is an alternative with PCM sync_stop callback, too. The callback is
> called at each time after a stream gets stopped before the next action
> (that is, either prepare, hw_params or close). It's only for
> stopping, and there is no similar way for sync of a stream start,
> though.
>
>
> thanks,
>
> Takashi
>
Hi!
Thank you for your prompt responses!
I have currently implemented the solution with sync_stop, as it is
precisely what I need to do, and it works perfectly.
As I may need to backport this driver up to 4.19, sync_stop was not yet
available, so I will look into the threaded IRQ solution, which sounds
promising.
Thank you both very much!
Best regards,
Louis Chauvet
--
Louis Chauvet, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2024-05-24 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 8:31 DMA Transfer Synchronization Issue in Out-of-Tree Sound Card Driver Louis Chauvet
2024-05-21 18:32 ` Mark Brown
2024-05-22 5:52 ` Takashi Iwai
2024-05-24 16:13 ` Louis Chauvet [this message]
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=ZlC8nG0Vzxg9HFT2@localhost.localdomain \
--to=louis.chauvet@bootlin.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
/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