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@alsa-project.org On Behalf Of Paul Olaru Sent: Monday, September 16, 2019 10:31 AM To: sound-open-firmware@alsa-project.org Cc: Jerome Laclavere jerome.laclavere@nxp.com; Daniel Baluta daniel.baluta@nxp.com; Guido Roncarolo guido.roncarolo@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@alsa-project.org https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.al...