On Fri, Oct 09, 2009 at 08:09:27AM +0300, Eero Nurkkala wrote: > On Thu, 2009-10-08 at 15:17 +0200, ext Mark Brown wrote: > > This stuff, particularly the enable, probably wants to be pushed out via > > an ALSA API rather than via random sysfs stuff. It'd be better to > > publish a control API here and then use that from within ALSA. > Hmm. What would be the way to transfer 128 x s16 words; is there an ALSA > control for something like that already ? IIRC correctly, the max > bytesize per control is (or used to be) something like 256 bytes or so. > So that gets right at it. (that's the sidetone 128 tap FIR in question) For things like the FIR you probably don't want to expose the entire table directly to user space. Depending on the typical usage it may be that platform data is the appropriate mechanism, with some simpler thing presented to applications allowing switching between a limited set of settings. sysfs may end up being the best option for the FIR setup. My main concern here is that the control goes into the ALSA domain so that the audio drivers know what's going on with these sidetone paths, particular in terms of the routing. -- To unsubscribe from this list: send the line "unsubscribe alsa-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
