All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Stefano Panella <stefano.panella@citrix.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: paravirtualized alsa kernel driver for XEN
Date: Tue, 20 Mar 2012 14:10:14 +0100	[thread overview]
Message-ID: <4F6881B6.2020903@ladisch.de> (raw)
In-Reply-To: <4F6769A9.6090200@citrix.com>

Stefano Panella wrote:
> I have been reading the documentation on "Writing an ALSA Driver" and I
> am still not completely clear on the meaning of the "pointer" callback
> in the pcm operations.
>
> 1) In case of a playback stream, is the pointer referring to wich sample
> is currently playing on the DAC or to which is it the last frame read by
> the HW from the alsa memory buffer?

It's the position of the first frame not yet read from the memory buffer.

The delay between the DMA and the DAC output would be reported by
adjusting runtime->delay, but drivers usually do not bother to do this,
except when this delay becomes rather large because of additional
queueing, e.g., in the USB driver.

> 4) is there any test I could run to check I have implemented correctly
> the "pointer" callback? Or any application which would need very high
> "pointer" precision like frame precision?

PulseAudio.
Or run mplayer and look at the A-V value in the status line.


Regards,
Clemens

  parent reply	other threads:[~2012-03-20 13:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 17:15 paravirtualized alsa kernel driver for XEN Stefano Panella
2012-03-20  9:52 ` David Henningsson
2012-03-21 10:11   ` Stefano Panella
2012-03-20 13:10 ` Clemens Ladisch [this message]
2012-03-21 10:16   ` Stefano Panella
2012-03-21 13:37     ` Clemens Ladisch
2012-03-22 11:22       ` Stefano Panella
2012-03-22 12:09         ` Clemens Ladisch
2012-04-11 17:08           ` Stefano Panella
2012-04-11 18:41             ` 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=4F6881B6.2020903@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=stefano.panella@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.