[alsa-devel] DPCM: skip DAPM_STREAM_STOP event to BE, if still used by other FE

[Mark Brown]

On Mon, Jul 04, 2016 at 10:26:54AM +0800, KaiChieh Chuang wrote:
> On Thu, 2016-06-30 at 03:08 +0800, Mark Brown wrote:
> > On Sun, Jun 05, 2016 at 02:58:59PM +0800, Kai Chieh Chuang wrote:

> > > The BE receiving SND_SOC_DAPM_STREAM_STOP event, while still used by a
> > > FE who is in STREAM_START state. The DAPM will just inactive BE related
> > > widget/dai without checking. This just doesn't seems right.

> > Why not?  The backend is still active and running, why would it expect
> > to be stopped unless it's supposed to actually stop?

> Yes, I don't expect it to stop.
> But at this situation, the BE change to state STREAM_STOP while
> still used by a FE in STREAM_START state.

> Shouldn't the BE stay in the STREAM_START state?

Yes, but that sounded like the situation you were describing?  It's
really hard to follow what you're trying to say here, perhaps just send
the fix you're proposing?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20160704/09048b94/attachment-0001.sig>