LKML Archive on
help / color / mirror / Atom feed
From: Pierre-Louis Bossart <>
To: Mark Brown <>,
	Takashi Iwai <>,
	open list <>,
	Liam Girdwood <>,, Jaroslav Kysela <>,,
	Kuninori Morimoto <>,
Subject: Re: [RFC PATCH 1/2] ASoC: soc-pcm: protect BE dailink state changes in trigger
Date: Thu, 26 Aug 2021 14:24:19 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 8/26/21 1:30 PM, Mark Brown wrote:
> From: Mark Brown,,, <>
> On Tue, 17 Aug 2021 11:40:53 -0500, Pierre-Louis Bossart wrote:
>> When more than one FE is connected to a BE, e.g. in a mixing use case,
>> the BE can be triggered multiple times when the FE are opened/started
>> concurrently. This race condition is problematic in the case of
>> SoundWire BE dailinks, and this is not desirable in a general
>> case. The code carefully checks when the BE can be stopped or
>> hw_free'ed, but the trigger code does not use any mutual exclusion.
>> [...]
> Applied, thanks!
> [1/2] ASoC: soc-pcm: protect BE dailink state changes in trigger
>       commit: 0c75fc7193387776c10f7c7b440d93496e3d5e21
> [2/2] ASoC: soc-pcm: test refcount before triggering
>       commit: 6479f7588651cbc9c91e61c20ff39119cbc8feba

Ah sorry, there were still some issues in this RFC, we did more testing
and came up with a lot of improvements. The intent of the RFC status was
also to make sure it wasn't applied before the merge window.

Can this be reverted in your branch Mark?

  reply	other threads:[~2021-08-26 19:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2021-08-17 16:40 ` Pierre-Louis Bossart
2021-08-26 18:30   ` Mark Brown
2021-08-26 19:24     ` Pierre-Louis Bossart [this message]
2021-08-30 11:15       ` Mark Brown
2021-08-17 16:40 ` [RFC PATCH 2/2] ASoC: soc-pcm: test refcount before triggering Pierre-Louis Bossart

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [RFC PATCH 1/2] ASoC: soc-pcm: protect BE dailink state changes in trigger' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).