On Wed, Dec 19, 2018 at 10:26:36AM -0600, Pierre-Louis Bossart wrote: > 1. how do we download binary tables that are related to hardware interfaces > or firmware modules? > In that case the "coefficients" don't depend on use cases but are set in > stone either at build time or when the device is flashed. They never vary > once the boot starts. You absolutely do not want these coefficients in the > kernel, and I can think of two ways of dealing with this case > 1.a. request_firmware(). If you are using the topology framework, there may > be a way of adding tokens so that the file names for the coefficient doesn't > have to be a constant string in the kernel. This is probably the easiest one I guess. > In the notes from the last two or three ALSA miniconfs there are mentions of > looking into other directions such as hwdep:. I must admit I am not familiar > with this interface so there's some learning needed on my side. Patrick Lai > from Qualcomm also mentioned a number of times the need to support > 'calibration' files and I wonder what the need really is. Yeah, hwdep is where everyone is heading. Unfortunately it'll need work in all the userspace tooling for new interfaces. > I am also wondering if there is a need for reads of large binary data. I can > see cases where you could extract state information, but this could be I've not heard that one, indeed even in the cases where coefficients are very large my understanding has been that there's multiple coefficient sets in the blob and not all of the blob will actually be used at once.
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
