Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
	 linux-sound@vger.kernel.org, "Sheetal ." <sheetal@nvidia.com>
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	 jonathanh@nvidia.com, thierry.reding@gmail.com,
	mkumard@nvidia.com,  spujar@nvidia.com
Subject: Re: [PATCH] ASoC: soc-pcm: Fix hw_params() and DAPM widget sequence
Date: Mon, 14 Apr 2025 14:56:45 +0100	[thread overview]
Message-ID: <174463900542.86688.12975575965483573998.b4-ty@kernel.org> (raw)
In-Reply-To: <20250404105953.2784819-1-sheetal@nvidia.com>

On Fri, 04 Apr 2025 10:59:53 +0000, Sheetal . wrote:
> Issue:
>  When multiple audio streams share a common BE DAI, the BE DAI
>  widget can be powered up before its hardware parameters are configured.
>  This incorrect sequence leads to intermittent pcm_write errors.
> 
>  For example, the below Tegra use-case throws an error:
>   aplay(2 streams) -> AMX(mux) -> ADX(demux) -> arecord(2 streams),
>   here, 'AMX TX' and 'ADX RX' are common BE DAIs.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: soc-pcm: Fix hw_params() and DAPM widget sequence
      commit: 9aff2e8df240e84a36f2607f98a0a9924a24e65d

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


      reply	other threads:[~2025-04-14 13:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04 10:59 [PATCH] ASoC: soc-pcm: Fix hw_params() and DAPM widget sequence Sheetal .
2025-04-14 13:56 ` 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=174463900542.86688.12975575965483573998.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mkumard@nvidia.com \
    --cc=perex@perex.cz \
    --cc=sheetal@nvidia.com \
    --cc=spujar@nvidia.com \
    --cc=thierry.reding@gmail.com \
    --cc=tiwai@suse.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