[alsa-devel] [RFC] ALSA: add new alsa control byte extended

Takashi Iwai tiwai at suse.de
Fri Nov 29 12:31:37 CET 2013

At Fri, 29 Nov 2013 11:25:05 +0000,
Mark Brown wrote:
> On Fri, Nov 29, 2013 at 11:10:43AM +0100, Jaroslav Kysela wrote:
> > driver). But if these large data are static and they are not expected to
> > be saved (alsactl), the control API may be extended using a new ioctl or
> > the hwdep interface with some custom tools may be used.
> I'd expect them to be handleable with standard tools, from a user
> perspective these things are just another setting that gets applied when
> changing use case like volumes and routing so manipulating the settings
> in a separate place seems wrong - at the level where you're applying
> them it's all part of the same set of data.

Basically agreed, but OTOH, size matters, too.  What if there are a
few MB data for several different control elements?  I don't think
managing them in the same text alsa.state file is so sensible.


More information about the Alsa-devel mailing list