[PATCH] ASoC: img: Imagination Technologies sound should depend on MIPS

[PATCH] ASoC: img: Imagination Technologies sound should depend on MIPS

[Geert Uytterhoeven]

Before, all Imagination sound symbols were gated by the SND_SOC_IMG
symbol, offering the user a simple option to hide them all.  After the
removal of this gate symbol, all symbols are exposed to the user, even
when configuring a kernel for a non-Imagination platform.
Fix this by adding a dependency on MIPS, to prevent asking the user
about these drivers when configuring a kernel for a different
architecture.

Fixes: b13f7eef9ff82e01 ("ASoC: img: Standardize ASoC menu")
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
 sound/soc/img/Kconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/sound/soc/img/Kconfig b/sound/soc/img/Kconfig
index 9a4cba6fdb505d69..22b75a8144a18170 100644
--- a/sound/soc/img/Kconfig
+++ b/sound/soc/img/Kconfig
@@ -1,5 +1,6 @@
 # SPDX-License-Identifier: GPL-2.0-only
 menu "Imagination Technologies"
+	depends on MIPS || COMPILE_TEST
 
 config SND_SOC_IMG_I2S_IN
 	tristate "Imagination I2S Input Device Driver"
-- 
2.43.0

Re: [PATCH] ASoC: img: Imagination Technologies sound should depend on MIPS

[Mark Brown]

On Tue, 08 Jul 2025 17:47:29 +0200, Geert Uytterhoeven wrote:
> Before, all Imagination sound symbols were gated by the SND_SOC_IMG
> symbol, offering the user a simple option to hide them all.  After the
> removal of this gate symbol, all symbols are exposed to the user, even
> when configuring a kernel for a non-Imagination platform.
> Fix this by adding a dependency on MIPS, to prevent asking the user
> about these drivers when configuring a kernel for a different
> architecture.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: img: Imagination Technologies sound should depend on MIPS
      commit: 68e4dadacb7faa393b532b41bbf99a2dbfec3b1b

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark