From: Stefano Panella <stefano.panella@citrix.com>
To: alsa-devel@alsa-project.org
Subject: paravirtualized alsa kernel driver for XEN
Date: Mon, 19 Mar 2012 17:15:21 +0000 [thread overview]
Message-ID: <4F6769A9.6090200@citrix.com> (raw)
Hi,
I am Stefano Panella, I am new to the list and I would like to take the
opportunity to ask some questions since I am trying to write a
paravirtualized alsa driver for XEN.
If all goes well I would also like to upstream it on linux.
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.
The description say:
"This callback is called when the PCM middle layer inquires the current
hardware position on the buffer."
My question are:
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?
2) What does the pointer mean in case of a capture stream? Is it the
position of the current frame on the ADC or is the latest frame written
into the alsa buffer?
3) in case it is the frame on the DAC/ADC, what happens if the callback
does not return the real DAC/ADC frame position but an approximate
value, let say rounded to 64 frames only?
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?
Thanks very much in advance,
Stefano
next reply other threads:[~2012-03-19 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 17:15 Stefano Panella [this message]
2012-03-20 9:52 ` paravirtualized alsa kernel driver for XEN David Henningsson
2012-03-21 10:11 ` Stefano Panella
2012-03-20 13:10 ` Clemens Ladisch
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=4F6769A9.6090200@citrix.com \
--to=stefano.panella@citrix.com \
--cc=alsa-devel@alsa-project.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 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.