The Axiado DB-H SPI controller is only present on Axiado AX3000 SoCs.
Hence add a dependency on ARCH_AXIADO, to prevent asking the user about
this driver when configuring a kernel without Axiado SoC Family support.

Fixes: e75a6b00ad7962a7 ("spi: axiado: Add driver for Axiado SPI DB controller")
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
 drivers/spi/Kconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
index 9e089df33a87868f..8995ea8d2c6b6c8c 100644
--- a/drivers/spi/Kconfig
+++ b/drivers/spi/Kconfig
@@ -216,6 +216,7 @@ config SPI_AXI_SPI_ENGINE
 config SPI_AXIADO
 	tristate "Axiado DB-H SPI controller"
 	depends on SPI_MEM
+	depends on ARCH_AXIADO || COMPILE_TEST
 	help
 	  Enable support for the SPI controller present on Axiado AX3000 SoCs.
 
-- 
2.43.0

On Tue, 27 Jan 2026 20:08:31 +0100, Geert Uytterhoeven wrote:
> The Axiado DB-H SPI controller is only present on Axiado AX3000 SoCs.
> Hence add a dependency on ARCH_AXIADO, to prevent asking the user about
> this driver when configuring a kernel without Axiado SoC Family support.
> 
> 

Applied to

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

Thanks!

[1/1] spi: SPI_AXIADO should depend on ARCH_AXIADO
      commit: e540be7d56d740144b1bd6f220b61ffe2f3830d4

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