-
Notifications
You must be signed in to change notification settings - Fork 314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] start/stop of SSP/nodec stream interferes with another stream #1526
Comments
Annotated bits from above log.
Then client 2 (start/stop in loop) is stopped and started and start fails
Xrun recovery fails for client 2, but that also brings down client 1:
|
@kv2019i are these two pipelines connected via the mixer ? or are they not connected. Just confused seeing HDMI and SSP then seeing MIXER in the logs. |
@lgirdwood wrote:
Good point, yes they are. This is the standard pipe of: Updated the title to reflect this related to two streams connected via mixer. |
@kv2019i Fail happens when you are stopping client 0 and client 1 is running. As long as you are stopping client 1 everything is working. It doesn't really matter, because it's still a bug, but just wanted to make sure you are aware of that. |
Describe the bug
This is a clone of Linux bug thesofproject/linux#854
The history is a bit complex to follow, but upon study of the bug today, the case is as follows:
Two PCM playback clients connected to SSP in nocodec mode. One client is kept stream, while other continuously starts and stops.
To Reproduce
Aplay instructions in
thesofproject/linux#854 (comment)
Reproduction Rate
1/10
Expected behavior
Starting and stopping one stream does not interfere with another stream.
Impact
End-product cases with multiple pipelines will show errors (e.g. a UI sound feedback may interfere with HDMI output).
Environment
APL UP2 pcm512x & APL UP2 nocodec
sof (master): 92fc706
kernel (topic/sof-dev): 80a2cb8
topology: sof-apl-pcm512x.tplg & sof-apl-nocodec.tplg
Screenshots or console output
See thesofproject/linux#854 (comment)
The text was updated successfully, but these errors were encountered: