From: ANISH KUMAR <anish.singh@samsung.com>
To: Ben Dooks <ben-linux@fluff.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: DMA interrupt not getting triggered
Date: Fri, 05 Feb 2010 08:44:05 +0000 (GMT) [thread overview]
Message-ID: <24512548.721341265359445661.JavaMail.weblogic@epml09> (raw)
>Which board are you trying this on?
S3C6410
>There may be some improvements with the DMA code in newer kernels, it would
>be worth trying 2.6.33 and seeing if that has the same problem. There was
>a problem with the circular DMA code failing to be fully merged which caused
>problems including a resource exhaustion.
Ben it would be very difficult to take the entire change.There are lot of efforts already gone into to make it stable.
Can you please tell me which all changes exactly is required to get rid of this problem?As to what all the files
that needs merging as i am not a kernel expert.
or
Can you give me some patch that would solve this problem?
next reply other threads:[~2010-02-05 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 8:44 ANISH KUMAR [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-05 8:22 DMA interrupt not getting triggered ANISH KUMAR
2010-02-05 8:17 ANISH KUMAR
2010-02-05 8:27 ` Ben Dooks
2010-02-05 8:35 ` jassi brar
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=24512548.721341265359445661.JavaMail.weblogic@epml09 \
--to=anish.singh@samsung.com \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
/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).