Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Clemens Ladisch" <cladisch@fastmail.net>
To: witzel.thomas@comcast.net
Cc: alsa-devel@lists.sf.net
Subject: Re: Intel ICH programming & ALSA driver
Date: Mon, 13 Nov 2006 17:40:18 +0100	[thread overview]
Message-ID: <1163436018.6764.275695992@webmail.messagingengine.com> (raw)
In-Reply-To: <200611131558.44643.witzel.thomas@comcast.net>

Thomas Witzel wrote:
> On Monday 13 November 2006 08:51, you wrote:
> > I don't think it's a good idea to reset the DMA when _any_ interrupt
> > occurs; this could be too early.  You could just wait for it to halt by
> > itself when the last buffer entry is reached, and reset the DMA when the
> > device is closed.
> 
> Without this it would get me about 100000 interrupts in just a few seconds 
> telling me that it has finished.

Apparently, the interrupt handler is supposed to either add more valid
buffers or to stop the DMA.

I think the appropriate thing to do is top stop (not reset) the DMA when
the end-of-list bit has been set, but not at the first interrupt (that
will occur after the first buffer has been fetched).


HTH
Clemens

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  parent reply	other threads:[~2006-11-13 16:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10 17:25 Intel ICH programming & ALSA driver Thomas Witzel
2006-11-13  8:51 ` Clemens Ladisch
     [not found]   ` <200611131558.44643.witzel.thomas@comcast.net>
2006-11-13 16:40     ` Clemens Ladisch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-08 14:52 witzel.thomas
2006-11-08  1:28 Thomas Witzel
2006-11-08 13:04 ` Clemens Ladisch

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=1163436018.6764.275695992@webmail.messagingengine.com \
    --to=cladisch@fastmail.net \
    --cc=alsa-devel@lists.sf.net \
    --cc=witzel.thomas@comcast.net \
    /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