Alsa state chooser

[TL Mieszkowski]

Al Johnson wrote:
> 
> The FSO API can list and change the alsa scenarios with stack based 
> management. It will also send a signal on scenario change so that
> interested 
> apps are aware of it. See:
> 
> http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Device.Audio.html;hb=HEAD
> 

I can see how having the sound info in a stack might be useful (marginally,
really), but I can't see it justifying the use of D-bus.  I wouldn't say
never, but I really can't think of any pressing reasons to want to know when
the state changes.  Maybe it's just lack of imagination.  And as for playing
sounds off the message bus, why? Am I wrong for instinctively hating D-bus,
and finding any reason to not use it? Or at least only using it for things
that must be asynchronous?

 Something I could see as useful is a signal when headphones are plugged in.
I remember reading in the Wolfson Codec manual that it is possible, by
monitoring voltages or some such, I imagine that would have to be done in
the alsa plugin or maybe in the driver though.
-- 
View this message in context: http://n2.nabble.com/Alsa-state-chooser-tp2222224p2228688.html
Sent from the Openmoko Community mailing list archive at Nabble.com.