Hello Mark In the continuation of the last mail.I run alsa_aplay and the WAV file sounds. Then press ctrl-z - aplay will go to background(suspend state) and i2s is stopped. Then type fg and the audio restart. Is there any difference between these two suspend ctrl-z and echo mem > /sys/power/state. In both the cases trigger will call with cmd value '1 ' in case of resume and '0' in case of suspend.
While going through the alsa framework I found that suspend and resume functionality is handled by the framework itself.Please correct me if my understanding is not correct.
Best Regards Rajeev
On 8/18/2011 11:35 AM, Rajeev kumar wrote:
Hi Mark I am not sure about the behavior in case of audio suspend/resume.
I tested the audio driver with aplay and then suspended to ram (using echo mem > /sys/power/state). After pressing wake to resume, the audio does not play unless aplay is closed and re-run. Do we expect the audio suspend/resume to work?
In the platform trigger part I am doing nothing and in case of cpu(i2s) , just disabling the i2s.
Best Regards Rajeev