[alsa-devel] DMA interrupt not getting triggered(nailed the problem need solution)
Hi All,
This problem is due to ETIMEDOUT(timeout) happening in s3c_snd_lrsync function(called by trigger). As i understand this could be due I2S being broken. This basically happens because of improper initialization of CPU or CODEC.
But if that is the case then it would not have produced sound initially also but that is not the case(initially it is ringing i.e. interrupt coming for a short time then after i am getting time out problem)?? After this sound is not coming this happens when it does the initialisation again using open, prepare,enqueue and so on.
Please provide any pointers which can help me out.
Thanks & High Regards, anish
On Mon, Feb 08, 2010 at 02:34:29AM +0000, ANISH KUMAR wrote:
This problem is due to ETIMEDOUT(timeout) happening in s3c_snd_lrsync function(called by trigger).
Please don't start a new thread for each mail, please continue discussion in the existing thread. It makes it much easier to follow which problem you are talking about.
As i understand this could be due I2S being broken. This basically happens because of improper initialization of CPU or CODEC.
But if that is the case then it would not have produced sound initially also but that is not the case(initially it is ringing i.e. interrupt coming for a short time then after i am getting time out problem)??
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.
Please provide any pointers which can help me out.
You've probably got a problem with the machine driver for your system, check the way the clocks are set up in there.
On 8 February 2010 02:34, ANISH KUMAR anish.singh@samsung.com wrote:
Hi All,
This problem is due to ETIMEDOUT(timeout) happening in s3c_snd_lrsync function(called by trigger). As i understand this could be due I2S being broken. This basically happens because of improper initialization of CPU or CODEC.
But if that is the case then it would not have produced sound initially also but that is not the case(initially it is ringing i.e. interrupt coming for a short time then after i am getting time out problem)?? After this sound is not coming this happens when it does the initialisation again using open, prepare,enqueue and so on.
Please provide any pointers which can help me out.
Check the master/slave mode at each end of the CPU to CODEC link. If both are master or both are slave you could see issues similar to what you are seeing.
participants (3)
-
ANISH KUMAR -
James Courtier-Dutton -
Mark Brown