[alsa-devel] [PATCH] ASoC: Allow imx-pcm-{dma, fiq}.c to be modules
This is required so we can build the imx sound support when ALSA itself is a loadable module.
Signed-off-by: Arnd Bergmann arnd@arndb.de Cc: alsa-devel@alsa-project.org Cc: Mark Brown broonie@kernel.org Cc: Fabio Estevam fabio.estevam@freescale.com
diff --git a/sound/soc/fsl/Kconfig b/sound/soc/fsl/Kconfig index aa43854..805b83e 100644 --- a/sound/soc/fsl/Kconfig +++ b/sound/soc/fsl/Kconfig @@ -109,11 +109,11 @@ config SND_SOC_IMX_SSI tristate
config SND_SOC_IMX_PCM_FIQ - bool + tristate select FIQ
config SND_SOC_IMX_PCM_DMA - bool + tristate select SND_SOC_GENERIC_DMAENGINE_PCM
config SND_SOC_IMX_AUDMUX diff --git a/sound/soc/fsl/imx-pcm.h b/sound/soc/fsl/imx-pcm.h index 67f656c..0e3619e 100644 --- a/sound/soc/fsl/imx-pcm.h +++ b/sound/soc/fsl/imx-pcm.h @@ -32,7 +32,7 @@ imx_pcm_dma_params_init_data(struct imx_dma_data *dma_data, dma_data->peripheral_type = IMX_DMATYPE_SSI; }
-#ifdef CONFIG_SND_SOC_IMX_PCM_DMA +#if IS_ENABLED(CONFIG_SND_SOC_IMX_PCM_DMA) int imx_pcm_dma_init(struct platform_device *pdev); void imx_pcm_dma_exit(struct platform_device *pdev); #else @@ -46,7 +46,7 @@ static inline void imx_pcm_dma_exit(struct platform_device *pdev) } #endif
-#ifdef CONFIG_SND_SOC_IMX_PCM_FIQ +#if IS_ENABLED(CONFIG_SND_SOC_IMX_PCM_FIQ) int imx_pcm_fiq_init(struct platform_device *pdev); void imx_pcm_fiq_exit(struct platform_device *pdev); #else
On Fri, Jul 05, 2013 at 05:45:15PM +0200, Arnd Bergmann wrote:
This is required so we can build the imx sound support when ALSA itself is a loadable module.
Is this actually OK with the FIQ APIs?
On Friday 05 July 2013, Mark Brown wrote:
On Fri, Jul 05, 2013 at 05:45:15PM +0200, Arnd Bergmann wrote:
This is required so we can build the imx sound support when ALSA itself is a loadable module.
Is this actually OK with the FIQ APIs?
I don't know. Why wouldn't it?
Other users of the same interfaces (mx1_camera, spi-s3c24xx) can also be modules, so I wouldn't expect a fundamental issue.
Arnd
On Fri, Jul 05, 2013 at 10:55:10PM +0200, Arnd Bergmann wrote:
On Friday 05 July 2013, Mark Brown wrote:
Is this actually OK with the FIQ APIs?
I don't know. Why wouldn't it?
It was the only reason I could think of why that'd have been done.
Other users of the same interfaces (mx1_camera, spi-s3c24xx) can also be modules, so I wouldn't expect a fundamental issue.
OK.
On Friday 05 July 2013, Mark Brown wrote:
On Fri, Jul 05, 2013 at 10:55:10PM +0200, Arnd Bergmann wrote:
On Friday 05 July 2013, Mark Brown wrote:
Is this actually OK with the FIQ APIs?
I don't know. Why wouldn't it?
It was the only reason I could think of why that'd have been done.
I looked in the log and found this part has been patched a couple of times already, going back and forth between "bool" and "tristate", always to fix build errors.
Please hold back for now, I'll try to reproduce on the bug on the current torvalds tree first. I know it was broken in linux-next as of a few weeks ago, but something else may have changed in the meantime.
Arnd
participants (2)
-
Arnd Bergmann -
Mark Brown