On Wed, 28 Nov 2001, Paul Davis wrote:
> ok, i added more printk's in the trident driver to track exactly what
> the interrupt sequence is.
>
> and what do you know ... if i add just one printk at the top, this
> doesn't stop things going wrong. if i add two printk's to tell me more
> about the nature of the interrupts, suddenly, everything works again.
>
> this stinks of a data race to me. with 0 or 1 interrupt printks -
> almost deterministic failure to wake up the capture stream reliably;
> add 1 more, and it works.
>
> is this likely to be a trident-specific issue? or can i assume that
> things look better on other hardware (i know it works right on the
> hammerfall) ?
It's true that the Trident IRQ acknowledge is probably broken at some
level. I found, with small periods, that Trident chip acknowledges
the IRQ more times, so it could be possible, that some interrupts are
lost, too. You can look for the spurious word in the Trident interrupt
handling routine for my hack against the multiple IRQ acknowledge.
Jaroslav
-----
Jaroslav Kysela <[EMAIL PROTECTED]>
SuSE Linux http://www.suse.com
ALSA Project http://www.alsa-project.org
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
