On Mon, Feb 08, 2010 at 11:17:01AM +0000, ANISH KUMAR wrote:
If the initial hardware state happens to result in LRCLK being where the lrsync() function is trying to get it then the driver will start up, but the misclocking of the configuration will result in ALSA detecting an error which will eventually result in a restart of the audio stream.
Mark in my case it is not restarting the audio stream(though it is trying to call trigger again for restarting) because in s3c_snd_lrsync function again i am getting time out(ETIMEDOUT).
...and the reason it is back in lrsync() is that it's trying to restart the audio stream.
This LRI register bit is not getting set properly causing timeout.How this situation is not coming always(4/10)?? And who should suppose to set it?
The LRI register reports the hardware state and so is updated autonomously by the hardware.
If my machine driver had a problem then this should have come always??
As I said in the e-mail to which you are replying:
| If the initial hardware state happens to result in LRCLK being where the | lrsync() function is trying to get it then the driver will start up, but | the misclocking of the configuration will result in ALSA detecting an | error which will eventually result in a restart of the audio stream.