From: Lee Revell <rlrevell@joe-job.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: [PATCH] emu10k1: various (mostly trivial) small cleanups
Date: Mon, 14 Mar 2005 18:56:18 -0500 [thread overview]
Message-ID: <1110844578.15588.12.camel@mindpipe> (raw)
In-Reply-To: <Pine.HPX.4.33n.0503140920520.15356-100000@studcom.urz.uni-halle.de>
On Mon, 2005-03-14 at 09:23 +0100, Clemens Ladisch wrote:
> Lee Revell wrote:
> > timer.c ... I just copied and pasted from the ymfpci driver &
> > changed the registers.
>
> BTW: Does the Emu10k1 have some sample/tick counter that runs even if
> no PCMs are running? If so, it would be possible to detect lost timer
> interrupts.
In practice I have found that interrupts are basically never lost. The
only time I ever saw this happen was when the VIA Unichrome XAA (yep,
userspace!) driver had a FIFO related bug where it would temporarily
stall the PCI bus.
I guess I am wondering whether this would be worth implementing. Do
you think the overhead of reading the wall clock register on every timer
interrupt is worth it?
Lee
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-14 23:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 21:04 [PATCH] emu10k1: various (mostly trivial) small cleanups Lee Revell
2005-03-13 8:44 ` Jaroslav Kysela
2005-03-14 8:23 ` Clemens Ladisch
2005-03-14 16:25 ` Lee Revell
2005-03-14 23:56 ` Lee Revell [this message]
2005-03-15 8:07 ` 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=1110844578.15588.12.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
/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.