Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Eliot Blennerhassett <bigblen@icqmail.com>,
	alsa-devel@lists.sourceforge.net
Subject: Re: Atomic operators in alsa driver
Date: Mon, 16 Aug 2004 12:34:30 +0200	[thread overview]
Message-ID: <s5hacwvbccp.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0408111519070.1788@pnote.perex-int.cz>

At Wed, 11 Aug 2004 15:19:20 +0200 (CEST),
Jaroslav wrote:
> 
> On Tue, 10 Aug 2004, Eliot Blennerhassett wrote:
> 
> > A question to clarify which 'operators' are atomic i.e. inside spinlock.
> > 
> > As far as I can make out from Takashi's Writing an Alsa driver, Chapter 5,
> > section "Operators" (am I correct?)
> > 
> > Atomic:
> > trigger callback
> > pointer callback
> > 
> > Non-atomic:
> > open callback
> > close callback
> > ioctl callback
> > hw_params callback
> > hw_free callback
> > prepare callback
> > copy and silence callbacks
> > ack callback
> > page callback
> 
> It's correct.

In practice, ack callback is usually treated as atomic to get finer
processing of data transfer.  For example, ack is called in the
pointer callback in pcm-indirect.h.  But basically it can be
non-atomic, too.


Takashi


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285

      reply	other threads:[~2004-08-16 10:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11  4:51 Atomic operators in alsa driver Eliot Blennerhassett
2004-08-11 13:19 ` Jaroslav Kysela
2004-08-16 10:34   ` Takashi Iwai [this message]

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=s5hacwvbccp.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=bigblen@icqmail.com \
    --cc=perex@suse.cz \
    /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