Skip to contentSkip to conversation

sound: soc: tegra: remove Kconfig dependency on TEGRA20_APB_DMA

PATCH In review Francesco Lavra 2 participants 3 messages Nov 26, 2025

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 sound: soc: tegra: remove Kconfig dependency on TEGRA20_APB_DMA

The ALSA SoC driver for Tegra runs also on SoCs without the Tegra20 APB DMA controller (e.g. Tegra234).

Fixes 09614acd87e6 ("arm64: tegra: APE sound card for Jetson AGX Orin")
---
 sound/soc/tegra/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/tegra/Kconfig +1 -1
index 71203a9197ed..9dbd589879fb 100644
@@ -3,7 +3,7 @@ menu "Tegra"
 
 config SND_SOC_TEGRA
 	tristate "SoC Audio for the Tegra System-on-Chip"
-	depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST
+	depends on ARCH_TEGRA || COMPILE_TEST
 	depends on COMMON_CLK
 	depends on RESET_CONTROLLER
 	select REGMAP_MMIO
Signature · 1 line
2.39.5
maintainer
#1 lore raw
Quoted 2 lines · Francesco Lavra

The ALSA SoC driver for Tegra runs also on SoCs without the Tegra20 APB DMA controller (e.g. Tegra234).

Please submit patches using subject lines reflecting the style for the subsystem, this makes it easier for people to identify relevant patches. Look at what existing commits in the area you're changing are doing and make sure your subject lines visually resemble what they're doing. There's no need to resubmit to fix this alone.

Quoted 1 line
Fixes 09614acd87e6 ("arm64: tegra: APE sound card for Jetson AGX Orin")

This is adding support for extra platforms, it's not a fix.

maintainer
#2 lore raw
In reply to Francesco Lavra
Quoted 4 lines · Francesco Lavra

The ALSA SoC driver for Tegra runs also on SoCs without the Tegra20 APB DMA controller (e.g. Tegra234).

Applied to

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

Thanks!

[1/1] sound: soc: tegra: remove Kconfig dependency on TEGRA20_APB_DMA

      commit: bcf016aa87fb448cea24fa25e02ccebce06b5a56

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