From: Takashi Iwai <tiwai@suse.de>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: <broonie@kernel.org>, <lgirdwood@gmail.com>, <tiwai@suse.com>,
<perex@perex.cz>, <lars@metafoo.de>,
<alsa-devel@alsa-project.org>, <vkoul@kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ALSA: dmaengine_pcm: Consider DMA cache caused delay in pointer callback
Date: Mon, 10 Feb 2020 16:23:29 +0100 [thread overview]
Message-ID: <s5ha75qfoum.wl-tiwai@suse.de> (raw)
In-Reply-To: <20200210151402.29634-1-peter.ujfalusi@ti.com>
On Mon, 10 Feb 2020 16:14:02 +0100,
Peter Ujfalusi wrote:
>
> Some DMA engines can have big FIFOs which adds to the latency.
> The DMAengine framework can report the FIFO utilization in bytes. Use this
> information for the delay reporting.
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> ---
> Hi,
>
> Changes since v1:
> - use bytes_to_frames() for the DMA delay calculation
> - Drop changes to soc-pcm
>
> 5.6-rc1 now have support for reporting the DMA cached data.
> With this patch we can include it to the delay calculation.
> The first DMA driver which reports this is the TI K3 UDMA driver.
>
> Regards,
> Peter
>
> sound/core/pcm_dmaengine.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/sound/core/pcm_dmaengine.c b/sound/core/pcm_dmaengine.c
> index 5749a8a49784..d8be7b488162 100644
> --- a/sound/core/pcm_dmaengine.c
> +++ b/sound/core/pcm_dmaengine.c
> @@ -247,9 +247,14 @@ snd_pcm_uframes_t snd_dmaengine_pcm_pointer(struct snd_pcm_substream *substream)
>
> status = dmaengine_tx_status(prtd->dma_chan, prtd->cookie, &state);
> if (status == DMA_IN_PROGRESS || status == DMA_PAUSED) {
> + struct snd_pcm_runtime *runtime = substream->runtime;
> +
> buf_size = snd_pcm_lib_buffer_bytes(substream);
> if (state.residue > 0 && state.residue <= buf_size)
> pos = buf_size - state.residue;
> +
> + runtime->delay = bytes_to_frames(runtime,
> + state.in_flight_bytes);
Another call of bytes_to_frames() below...
> }
>
> return bytes_to_frames(substream->runtime, pos);
... refers to substream->runtime.
Better to align both places, either runtime or substream->runtime.
With that minor nitpick, the change looks good:
Reviewed-by: Takashi Iwai <tiwai@suse.de>
thanks,
Takashi
next prev parent reply other threads:[~2020-02-10 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 15:14 Peter Ujfalusi
2020-02-10 15:23 ` Takashi Iwai [this message]
2020-02-10 15:26 ` Peter Ujfalusi
2020-02-11 15:48 ` Applied "ALSA: dmaengine_pcm: Consider DMA cache caused delay in pointer callback" to the asoc tree Mark Brown
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=s5ha75qfoum.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@ti.com \
--cc=tiwai@suse.com \
--cc=vkoul@kernel.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
all inboxes | Powered by JetHome®