ASoC: Intel: sst-acpi: Request firmware before SST platform driver probing
Subsystems (3)
PATCH v2 1/1 ASoC: Intel: sst-acpi: Request firmware before SST platform driver probing
We originally thought to request SST audio DSP firmware during the SST platform driver initialization. However plain request_firmware doesn't work in driver probe paths if userspace is not ready to handle it. For instance when drivers are built-in.
Implementing asynchronous firmware request in SST platform driver initialization complicates code needlessly since it anyway will fail if firmware is missing.
This is more simple to handle by requesting firmware asynchronously in sst_acpi_probe() and register SST platform only after firmware is loaded.
---
V2:
- Fix leak in sst_acpi_probe that sst_acpi->pdev_mach wasn't unregistered in case of request_firmware_nowait fails
- Test is sst_acpi->pdev_pcm valid before unregistering it in sst_acpi_remove. It can contain not only NULL or valid pointer but an error code too
--- sound/soc/intel/sst-acpi.c | 56 ++++++++++++++++++++++++++++++++-------------- sound/soc/intel/sst-dsp.h | 2 +- 2 files changed, 40 insertions(+), 18 deletions(-)
sound/soc/intel/sst-acpi.c +39 -17
@@ -16,6 +16,7 @@#include <linux/acpi.h> #include <linux/device.h> +#include <linux/firmware.h> #include <linux/module.h> #include <linux/platform_device.h>
@@ -56,6 +57,32 @@ struct sst_acpi_priv {struct sst_acpi_desc *desc; }; +static void sst_acpi_fw_cb (const struct firmware *fw,void *context) +{ +struct platform_device *pdev = context; +struct device *dev = &pdev->dev; +struct sst_acpi_priv *sst_acpi =platform_get_drvdata (pdev); +struct sst_pdata *sst_pdata = &sst_acpi->sst_pdata; +struct sst_acpi_desc *desc = sst_acpi->desc; + + sst_pdata->fw = fw; +if (!fw) { +dev_err (dev,"Cannot load firmware %s\n" , desc->fw_filename); +return ; + } + +/* register PCM and DAI driver */ + sst_acpi->pdev_pcm = +platform_device_register_data (dev, desc->drv_name,-1 , + sst_pdata,sizeof (*sst_pdata)); +if (IS_ERR (sst_acpi->pdev_pcm)) { +dev_err (dev,"Cannot register device %s. Error %d\n" , + desc->drv_name, (int )PTR_ERR (sst_acpi->pdev_pcm)); + } + +return ; +} +static int sst_acpi_probe (struct platform_device *pdev) {const struct acpi_device_id *id;
@@ -79,7 +106,6 @@ static int sst_acpi_probe(struct platform_device *pdev) desc = mach->res_desc; sst_pdata = &sst_acpi->sst_pdata; sst_pdata->id = desc->sst_id; - sst_pdata->fw_filename = desc->fw_filename; sst_acpi->desc = desc;if (desc->resindex_dma_base >=0 ) {
@@ -118,37 +144,33 @@ static int sst_acpi_probe(struct platform_device *pdev) } } -/* register PCM and DAI driver */ - sst_acpi->pdev_pcm = -platform_device_register_data (dev, desc->drv_name,-1 , - sst_pdata,sizeof (*sst_pdata)); -if (IS_ERR (sst_acpi->pdev_pcm)) -return PTR_ERR (sst_acpi->pdev_pcm); - -/* register machine driver */ platform_set_drvdata (pdev, sst_acpi); +/* register machine driver */ sst_acpi->pdev_mach =platform_device_register_data (dev, mach->drv_name,-1 , sst_pdata,sizeof (*sst_pdata)); -if (IS_ERR (sst_acpi->pdev_mach)) { - ret =PTR_ERR (sst_acpi->pdev_mach); - goto sst_err; - } +if (IS_ERR (sst_acpi->pdev_mach)) +return PTR_ERR (sst_acpi->pdev_mach); -return ret; +/* continue SST probing after firmware is loaded */ + ret =request_firmware_nowait (THIS_MODULE , true, desc->fw_filename, + dev,GFP_KERNEL , pdev, sst_acpi_fw_cb); +if (ret) +platform_device_unregister (sst_acpi->pdev_mach); -sst_err: -platform_device_unregister (sst_acpi->pdev_pcm);return ret; }static int sst_acpi_remove (struct platform_device *pdev) {struct sst_acpi_priv *sst_acpi =platform_get_drvdata (pdev); +struct sst_pdata *sst_pdata = &sst_acpi->sst_pdata;platform_device_unregister (sst_acpi->pdev_mach); -platform_device_unregister (sst_acpi->pdev_pcm); +if (!IS_ERR_OR_NULL (sst_acpi->pdev_pcm)) +platform_device_unregister (sst_acpi->pdev_pcm); +release_firmware (sst_pdata->fw);return 0 ; }
sound/soc/intel/sst-dsp.h +1 -1
@@ -152,7 +152,7 @@ struct sst_pdata {int irq;/* Firmware */ -const char *fw_filename; +const struct firmware *fw;/* DMA */ u32 dma_base;
Signature · 1 line
1.8.5.3
Mark Brown
maintainerQuoted 4 lines · Jarkko Nikula
We originally thought to request SST audio DSP firmware during the SST platform driver initialization. However plain
request_firmwaredoesn't work in driver probe paths if userspace is not ready to handle it. For instance when drivers are built-in.
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.
Liam Girdwood
maintainerQuoted 10 lines · Mark Brown
Quoted 4 lines · Jarkko Nikula
We originally thought to request SST audio DSP firmware during the SST platform driver initialization. However plain
request_firmwaredoesn't work in driver probe paths if userspace is not ready to handle it. For instance when drivers are built-in.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 :)
Liam
Mark Brown
maintainerQuoted 7 lines · Liam Girdwood
Quoted 4 lines · Mark Brown
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.
Quoted 6 lines
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?