Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Cc: linux-sound@vger.kernel.org, kai.vehmanen@linux.intel.com,
	 ranjani.sridharan@linux.intel.com,
	yung-chuan.liao@linux.intel.com,  pierre-louis.bossart@linux.dev,
	stable@vger.kernel.org
Subject: Re: (subset) [PATCH 0/5] ASoC: SOF: ipc4: Fixes for delay reporting
Date: Fri, 03 Oct 2025 15:33:29 +0100	[thread overview]
Message-ID: <175950200983.87242.15474178381084349453.b4-ty@kernel.org> (raw)
In-Reply-To: <20251002074719.2084-1-peter.ujfalusi@linux.intel.com>

On Thu, 02 Oct 2025 10:47:14 +0300, Peter Ujfalusi wrote:
> With SRC in the firmware processing pipeline the FE and BE rate
> can be different, the sample counters on the two side of the DSP
> counts in different rate domain and they will drift apart.
> The counters should be moved to the same rate domain to be
> usable for delay calculation.
> 
> The ChainDMA offset value was incorrect since the host buffer size
> and the trigger to start the chain is misunderstood initially.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[3/5] ASoC: SOF: sof-audio: add dev_dbg_ratelimited wrapper
      commit: 18dbff48a1ea58100f9fa6886cfef286a96a5fb0
[4/5] ASoC: SOF: ipc4-pcm: do not report invalid delay values
      commit: a4b8152c09a832b089864e5e209a479bb0fb5cc9
[5/5] ASoC: SOF: Intel: Read the LLP via the associated Link DMA channel
      commit: aaab61de1f1e44a2ab527e935474e2e03a0f6b08

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark


      parent reply	other threads:[~2025-10-03 14:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02  7:47 [PATCH 0/5] ASoC: SOF: ipc4: Fixes for delay reporting Peter Ujfalusi
2025-10-02  7:47 ` [PATCH 1/5] ASoC: SOF: ipc4-pcm: fix delay calculation when DSP resamples Peter Ujfalusi
2025-10-02  7:47 ` [PATCH 2/5] ASoC: SOF: ipc4-pcm: fix start offset calculation for chain DMA Peter Ujfalusi
2025-10-02  7:47 ` [PATCH 3/5] ASoC: SOF: sof-audio: add dev_dbg_ratelimited wrapper Peter Ujfalusi
2025-10-02  7:47 ` [PATCH 4/5] ASoC: SOF: ipc4-pcm: do not report invalid delay values Peter Ujfalusi
2025-10-02  7:47 ` [PATCH 5/5] ASoC: SOF: Intel: Read the LLP via the associated Link DMA channel Peter Ujfalusi
2025-10-02 17:06 ` (subset) [PATCH 0/5] ASoC: SOF: ipc4: Fixes for delay reporting Mark Brown
2025-10-03 14:33 ` Mark Brown [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=175950200983.87242.15474178381084349453.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=stable@vger.kernel.org \
    --cc=yung-chuan.liao@linux.intel.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