Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Assaf Hoffman <hoffman@marvell.com>
Cc: Rita Shtern <rita@marvell.com>, alsa-devel@lists.sourceforge.net
Subject: Re: ALSA HW buffer managment
Date: Tue, 07 Nov 2006 02:08:29 -0500	[thread overview]
Message-ID: <1162883310.22849.107.camel@mindpipe> (raw)
In-Reply-To: <B9FFC3F97441D04093A504CEA31B7C41F2677C@msilexch01.marvell.com>

On Tue, 2006-11-07 at 08:48 +0200, Assaf Hoffman wrote:
> Hi,
> As I understood, ALSA buffer management uses the 'periods' notion to
> control the latency between SW stack and HW DMA.
> My HW is not capable of interrupting the SW on a period basis. The only
> interrupt HW generates is on half or quarter of the DMA buffer (for
> example, in capture, after each half of the buffer is filled with
> samples the HW will signal interrupt).

"Period" just refers to the interval between interrupts. So your
hardware supports either 2 or 4 periods per buffer.

Did you read "Writing an ALSA driver"?

Lee


-------------------------------------------------------------------------
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

  reply	other threads:[~2006-11-07  7:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-07  6:48 ALSA HW buffer managment Assaf Hoffman
2006-11-07  7:08 ` Lee Revell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-07  7:15 Assaf Hoffman
2006-11-07 12:15 ` Takashi Iwai
2006-11-07 13:11 Assaf Hoffman

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=1162883310.22849.107.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=hoffman@marvell.com \
    --cc=rita@marvell.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