-
Notifications
You must be signed in to change notification settings - Fork 140
Description
There might be wrong usage to pm_runtime_put_autosuspend() in SOF driver, previously I saw dmesg errors like "error: pcm close failed to idle -16" on UP2, and know another similar errors happens on CML platforms on every boots:
[ 5.651129] sof-audio-pci 0000:00:1f.3: firmware boot complete
[ 5.717502] sof-audio-pci 0000:00:1f.3: error: volume get failed to idle -16
[ 5.717659] sof-audio-pci 0000:00:1f.3: error: volume get failed to idle -16
[ 5.717847] sof-audio-pci 0000:00:1f.3: error: volume get failed to idle -16
[ 5.718040] sof-audio-pci 0000:00:1f.3: error: volume get failed to idle -16
[ 5.718223] sof-audio-pci 0000:00:1f.3: error: volume get failed to idle -16
[ 5.718405] sof-audio-pci 0000:00:1f.3: error: volume get failed to idle -16
[ 5.718594] sof-audio-pci 0000:00:1f.3: error: volume get failed to idle -16
[ 5.718794] sof-audio-pci 0000:00:1f.3: error: volume get failed to idle -16
[ 5.719013] sof-audio-pci 0000:00:1f.3: error: volume get failed to idle -16
This is not critical but there might be some PM issues hidden there, can anybody help to investigate and fix it?