On Wed, Nov 21, 2012 at 11:16:18AM +0000, Liam Girdwood wrote:
On 21/11/12 10:37, Mark Brown wrote:
Right, but the decision we took at the ASoC conference and have been implementing was to move away from that to just letting applications set the binary blob to change the enumeration value instead and then putting the management of multiple names for the blobs into userspace.
Ok, this is fine and works well for larger or multiple blobs that will be frequently changed at runtime depending on use case. However, the ABE coefficients here (around 400 bytes per EQU) are only loaded once at boot (where the number and graph positions of the EQUs is tightly coupled to the FW) and are not unloaded. The simplification here is that we dont have to write any new userspace code to manage the ABE EQUs and treat them as regular alsamixer controls which makes the integration and testing easier in this case.
That's the case for essentially all blobs right now (nobody got round to fixing the ABI limit of 512 bytes!). Are we saying we want to use this infrastructure for all blobs? If that's the case then we definitely need to support multiple files per device...