[Sound-open-firmware] Questions about the pause-release flow

[Paul Olaru]

Here is the strace output, I don't understand why for release we still have SNDRV_PCM_IOCTL_PAUSE used. Is this a problem in the userspace or some other issue I don't understand?

-----Original Message-----
From: Sound-open-firmware <sound-open-firmware-bounces at alsa-project.org> On Behalf Of Paul Olaru
Sent: Monday, September 16, 2019 10:31 AM
To: sound-open-firmware at alsa-project.org
Cc: Jerome Laclavere <jerome.laclavere at nxp.com>; Daniel Baluta <daniel.baluta at nxp.com>; Guido Roncarolo <guido.roncarolo at nxp.com>
Subject: [Sound-open-firmware] Questions about the pause-release flow

Right now I have a working (but not yet cleaned up) set of drivers (host DMA,
DAI DMA and DAI itself) and I figured I could test for pause-release (even if the
rates seem incorrect; can't actually check for correctness until the codec driver
is also ready).

The issue I encountered is: I can pause, however whenever I press <SPACE> again
on aplay, I get "pause release error: Invalid argument" and the SOF log shows
"dai_comp_trigger(), PAUSE/STOP" immediately followed by a -22 (-EINVAL)
return code from pipeline_trigger.

Shouldn't unpausing actually send COMP_TRIGGER_RELEASE?

I am doing my own state checking but I suspect it may be wrong.

What should I look into, and is this actually correct behavior?
_______________________________________________
Sound-open-firmware mailing list
Sound-open-firmware at alsa-project.org
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.alsa-project.org%2Fmailman%2Flistinfo%2Fsound-open-firmware&data=02%7C01%7Cpaul.olaru%40nxp.com%7C4028d0b163df4aed313008d73a77effa%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637042159114048923&sdata=bQxaRY0DEIlU89lslPK49w5LDmD5pXgrF2L7y8%2FRU2s%3D&reserved=0