Thanks Hannu,
> No. The interrupt rate will be the same regardless of the number of open
> client engines.
I've since verified this is the case, same interrupt rate regardless of number
of open client engines.
> This is not possible. The interrupts are driven by the actual hardware.
> The driver level interrupt handler calls vmix which feeds audio to the
> device if any of the applications are running. It is not possible to
> change the interrupt rate (fragment size of the actual device) on fly.
In my ignorance of things OSS, audio codecs, etc, let me ask some dumb
questions.
Why are these (feeding silence) interrupts generated when using vmix but not
when vmix is disabled? Why does vmix need to feed silence when osscore
does not ? If I disable vmix and accept a single audio stream no interrupts
(well, one!) are generated while the audio device is open() but with no audio
playback or recording. This is my apps quiescent state.
> If no application has vmix opened then there will be no audio
> play/record interrupts. There will be unnecessary interrupts only when
> an application has the device opened but it has not started the actual
> play/record operation yet. This situation is very rare.
Unfortunately in my case the above situation is quite common, the embedded
client side app has the audio device open in anticipation of an audio
playback/record
request from the server. When the entire client app is quiescent (unused but
connected
to the server with audio device(s) open) I'd like to initiate power saving.
As there may be multiple audio streams I'm using vmix with multiple client
threads.
> If you are getting interrupts even when none of the vmix engines is open
> then this is caused by the other devices sharing the same interrupt
> line. The hdaudio device may also cause some other interrupts (than
> audio play/record). However I have not been able to see this in any of
> the hdaudio systems I have.
> Does the interrupt count reported by ossinfo -d keep increasing even
> when there are no applications using the device?
Sorry to have mislead you, hdaudio interrupts are only generated when the
device is open() and possibly in use.
When no app is using the device the hdaudio interrupt count remains static.
Thanks and regards.
_______________________________________________
oss-devel mailing list
oss-devel@mailman.opensound.com
http://mailman.opensound.com/mailman/listinfo/oss-devel
