alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: ANISH KUMAR <anish.singh@samsung.com>
To: jassi brar <jassisinghbrar@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	ben-linux@fluff.org,
	"JaroslavKyselaperex@perex.cz" <JaroslavKyselaperex@perex.cz>
Subject: DMA interrupt not getting triggered(nailed the problem need solution)
Date: Mon, 08 Feb 2010 02:34:29 +0000 (GMT)	[thread overview]
Message-ID: <15824817.821301265596468706.JavaMail.weblogic@epml09> (raw)


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

             reply	other threads:[~2010-02-08  2:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08  2:34 ANISH KUMAR [this message]
2010-02-08 11:05 ` DMA interrupt not getting triggered(nailed the problem need solution) Mark Brown
2010-02-08 16:06 ` James Courtier-Dutton
  -- strict thread matches above, loose matches on Subject: below --
2010-02-08 11:17 ANISH KUMAR
2010-02-08 11:27 ` Mark Brown
2010-02-08 12:15 ANISH KUMAR
2010-02-08 14:42 ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15824817.821301265596468706.JavaMail.weblogic@epml09 \
    --to=anish.singh@samsung.com \
    --cc=JaroslavKyselaperex@perex.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=ben-linux@fluff.org \
    --cc=jassisinghbrar@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).