From: "Martijn Sipkema" <msipkema@sipkema-digital.com>
To: alsa-devel@alsa-project.org
Subject: Fw: writing audiowerk driver (philips saa7146a), some questions
Date: Fri, 31 May 2002 11:38:41 +0100 [thread overview]
Message-ID: <001801c2088f$71693120$0400a8c0@martijn> (raw)
below is a message i sent earlier, but with the wrong email address:
----
writing audiowerk driver (philips saa7146a), some questions
hi,
i have finally been able to get the information i need to be able
to write a driver for the emagic audiowerk8 audio interface.
now since i am not an experienced kernel programmer and have
not even done audio programming (apart from midi), i have
some questions.
- should i use the normal double buffered aproach or does having
more than 2 buffers have advantages?
- what is normally called the latency of an audio interface for output?
is this the total size of the buffers or (in the case of double buffered
io)
only one buffer? i'm thinking it is the total buffer size and this would
make using more than 2 buffers have a better latency/interrupt response
time ratio, right?
- should setting the buffer size and number be done on modules loading
or should it be possible to change it after that? the saa7146 doesn't need
contiguous memory since it has a mmu.
- where can i find documentation on writing alsa drivers? what would be
the best driver source to use for documentation?
- does alsa allow varipitch? i think the new rme cards are supposed to
have this feature and the audiowerk8 has it, i.e. it can change its
sampling
rate from about 37700 to 58200 hz while running in 1hz increments.
this allows for sync to video/tape/midi or whatever. or it allows for the
sample rate to be adjusted when receiving audio using rtp.
- the audiowerk8 uses three dma channels: one for input and two for output.
should i just wake a process that is blocking on a read() from the input
dma
interrupt or should i wait until all three dma channels are ready and then
unblock all read()/write() processes? should unblocking the processes be
done
from bottom half?
--martijn
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
next reply other threads:[~2002-05-31 9:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-31 10:38 Martijn Sipkema [this message]
2002-05-31 11:03 ` Fw: writing audiowerk driver (philips saa7146a), some questions tomasz motylewski
2002-05-31 12:22 ` Martijn Sipkema
2002-05-31 11:26 ` Takashi Iwai
2002-05-31 13:05 ` Martijn Sipkema
2002-05-31 13:15 ` Takashi Iwai
2002-05-31 14:36 ` Martijn Sipkema
[not found] ` <s5h7klkh1ba.wl@alsa2.suse.de>
2002-05-31 18:11 ` Martijn Sipkema
2002-06-03 11:26 ` Bob Ham
2002-06-03 12:49 ` Fw: writing audiowerk driver (philips saa7146a),some questions Martijn Sipkema
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='001801c2088f$71693120$0400a8c0@martijn' \
--to=msipkema@sipkema-digital.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.