[alsa-devel] [RFC] Channel mapping API
Takashi Iwai
tiwai at suse.de
Tue Aug 21 15:14:06 CEST 2012
At Tue, 21 Aug 2012 14:35:57 +0200,
Takashi Iwai wrote:
>
> At Tue, 21 Aug 2012 14:31:55 +0200,
> Jaroslav Kysela wrote:
> >
> > Date 21.8.2012 14:15, Takashi Iwai wrote:
> > > For getting the channel map, the driver could send a notification once
> > > when routing is changed.
> >
> > This leads to this question: Why you define the map controls volatile?
> > I think that the channel map changes can be tracked nicely using the
> > standard control event notifications without any hidden changes.
> > Perhaps, the value change event may be invoked each time after prepare
> > and when the user space set the new values and also in above situation,
> > when the channel map is changed on an external request.
>
> What I had in my mind for the volatile flag was how to avoid the
> effect by "alsactl restore". But since the set op was changed only
> for the prepared state, the volatile flag can be removed, I think.
The VOLATILE flag is removed in the git tree now.
Takashi
More information about the Alsa-devel
mailing list