On Wed, Feb 19, 2014 at 01:50:32PM +0000, Liam Girdwood wrote:
On Wed, 2014-02-19 at 21:25 +0900, Mark Brown wrote:
The more usual thing to do here is to only request the firmware when the device is actually being used (in this case on open). This also allows the firmware to be replaced easily at runtime which is helpful too. It seems like this is still an improvement though so I've applied it.
Fwiw, we need to load the FW at probe time since it will contain the FW topology for the SST drivers. The next phase for the SST FW is to use the ASoC firmware loader for DAPM, Kcontrols + DAI links (Vinod is working on patch for DAI links iirc, I will be back to the fw loader next week if all goes to plan). The good news is that the ASoC FW loader can also unload FW so we should be able to re-load FW at runtime too :)
I had thought the firmware loader would be able to cope with the firmware getting loaded and unloaded at runtime, several of the potential users actively want to be able to switch firmwares?