From: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>
To: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>
Cc: Takashi Iwai <tiwai@suse.com>, Mark Brown <broonie@kernel.org>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Linux-ALSA <alsa-devel@alsa-project.org>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
arun@asymptotic.io, wim.taymans@gmail.com
Subject: Re: (re)use and (re)definition of snd_pcm_hw_params->fifo_size for 'jumpy DMA'
Date: Thu, 23 Apr 2026 08:05:30 +0300 [thread overview]
Message-ID: <463d844b-ef44-471a-8749-6bb068833c4a@linux.intel.com> (raw)
In-Reply-To: <8af520bc-cb27-416a-b823-7a21f0784f89@linux.intel.com>
On 22/04/2026 17:19, Péter Ujfalusi wrote:
> Hrm, so this is a driver scoped refine, right? Based on the requested
> period size and a flag (SNDRV_PCM_HW_PARAMS_LATENCY_AWARE?) the driver
> refines the period size based on it's jumpyDMA capabilities?
>
> But in this example the application will have no knowledge still how the
> DMA will move, the DMA will initially move 30ms and after that, every
> 5ms it moves 5ms, so the driver should be refining to 5ms period size, 6
> initial periods and 1 period step, no.
>
> Or with my favorite examples:
> 4ms initial burst w/ 1ms steps will refine to 1ms periods, 4 init and 1
> step.
> 100ms initial burst w/ 96ms steps will refine to... I'm not sure
4ms period size, 25 init periods, 24 step periods?
and same for
> 40ms initial burst w/ 36ms steps.
4ms period size, 10 init periods, 9 step periods?
--
Péter
next prev parent reply other threads:[~2026-04-23 5:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 13:34 (re)use and (re)definition of snd_pcm_hw_params->fifo_size for 'jumpy DMA' Péter Ujfalusi
2026-03-23 14:54 ` Jaroslav Kysela
2026-03-23 16:16 ` Péter Ujfalusi
2026-03-24 8:58 ` Jaroslav Kysela
2026-03-24 10:51 ` Péter Ujfalusi
2026-03-24 13:25 ` Péter Ujfalusi
2026-03-24 15:48 ` Jaroslav Kysela
2026-03-25 13:28 ` Péter Ujfalusi
2026-03-25 14:08 ` Jaroslav Kysela
2026-03-26 12:04 ` Péter Ujfalusi
2026-03-24 7:12 ` Péter Ujfalusi
2026-03-30 14:27 ` Takashi Iwai
2026-03-30 15:15 ` Péter Ujfalusi
2026-03-30 16:39 ` Takashi Iwai
2026-03-31 6:00 ` Péter Ujfalusi
2026-03-31 6:36 ` Takashi Iwai
2026-03-31 9:29 ` Jaroslav Kysela
2026-03-31 10:42 ` Kai Vehmanen
2026-03-31 10:56 ` Péter Ujfalusi
2026-03-31 12:00 ` Jaroslav Kysela
2026-03-31 14:09 ` Péter Ujfalusi
2026-04-02 12:01 ` Jaroslav Kysela
2026-04-07 11:59 ` Péter Ujfalusi
2026-04-07 13:50 ` Jaroslav Kysela
2026-04-14 10:44 ` Péter Ujfalusi
2026-04-14 11:14 ` Jaroslav Kysela
2026-04-14 13:47 ` Péter Ujfalusi
2026-04-14 17:23 ` Jaroslav Kysela
2026-04-22 14:19 ` Péter Ujfalusi
2026-04-23 5:05 ` Péter Ujfalusi [this message]
2026-04-30 15:21 ` Jaroslav Kysela
2026-03-31 11:19 ` Péter 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=463d844b-ef44-471a-8749-6bb068833c4a@linux.intel.com \
--to=peter.ujfalusi@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=arun@asymptotic.io \
--cc=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
--cc=wim.taymans@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