Skip to contentSkip to conversation

spi: tegra114: remove Kconfig dependency on TEGRA20_APB_DMA

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

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 spi: tegra114: remove Kconfig dependency on TEGRA20_APB_DMA

This driver runs also on Tegra SoCs without a Tegra20 APB DMA controller (e.g. Tegra234).
Remove the Kconfig dependency on TEGRA20_APB_DMA; in addition, amend the help text to reflect the fact that this driver works on SoCs different from Tegra114.

Fixes bb9667d8187b ("arm64: tegra: Add SPI device tree nodes for Tegra234")
---
 drivers/spi/Kconfig | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/spi/Kconfig +2 -2
index 891729c9c564..9f20cb75bb85 100644
@@ -1170,10 +1170,10 @@ config SPI_TEGRA210_QUAD
 
 config SPI_TEGRA114
 	tristate "NVIDIA Tegra114 SPI Controller"
-	depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST
+	depends on ARCH_TEGRA || COMPILE_TEST
 	depends on RESET_CONTROLLER
 	help
-	  SPI driver for NVIDIA Tegra114 SPI Controller interface. This controller
+	  SPI controller driver for NVIDIA Tegra114 and later SoCs. This controller
 	  is different than the older SoCs SPI controller and also register interface
 	  get changed with this controller.
 
Signature · 1 line
2.39.5
maintainer
#1 lore raw
Quoted 8 lines · Francesco Lavra

This driver runs also on Tegra SoCs without a Tegra20 APB DMA controller (e.g. Tegra234).
Remove the Kconfig dependency on TEGRA20_APB_DMA; in addition, amend the help text to reflect the fact that this driver works on SoCs different from Tegra114.

[...]

Applied to

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

Thanks!

[1/1] spi: tegra114: remove Kconfig dependency on TEGRA20_APB_DMA

      commit: 3dcf44ab56e1d3ca3532083c0d5390b758e45b45

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