From: Peter Robinson <pbrobinson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Peter Robinson <pbrobinson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH v2] spi: make architecture specific hardware depend on the associated hardware
Date: Sun, 20 Nov 2016 17:55:05 +0000 [thread overview]
Message-ID: <20161120175505.2910-1-pbrobinson@gmail.com> (raw)
There's not much point enabling hardware specific hardware drivers if the
actual SoC architecture platforms aren't enabled as they're not much use
with out it.
Signed-off-by: Peter Robinson <pbrobinson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
---
drivers/spi/Kconfig | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
v1->v2:
- Add COMPILE_TEST to changes missing the option
diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
index b799547..69730ac 100644
--- a/drivers/spi/Kconfig
+++ b/drivers/spi/Kconfig
@@ -188,6 +188,7 @@ config SPI_BUTTERFLY
config SPI_CADENCE
tristate "Cadence SPI controller"
+ depends on ARCH_ZYNQ || ARCH_ZYNQMP || COMPILE_TEST
help
This selects the Cadence SPI controller master driver
used by Xilinx Zynq and ZynqMP.
@@ -224,7 +225,7 @@ config SPI_DW_PCI
config SPI_DW_MID_DMA
bool "DMA support for DW SPI controller on Intel MID platform"
- depends on SPI_DW_PCI && DW_DMAC_PCI
+ depends on (X86 || COMPILE_TEST) && SPI_DW_PCI && DW_DMAC_PCI
config SPI_DW_MMIO
tristate "Memory-mapped io interface driver for DW SPI core"
@@ -499,6 +500,7 @@ config SPI_PXA2XX_PCI
config SPI_ROCKCHIP
tristate "Rockchip SPI controller driver"
+ depends on ARCH_ROCKCHIP || COMPILE_TEST
help
This selects a driver for Rockchip SPI controller.
@@ -650,7 +652,7 @@ config SPI_TEGRA20_SLINK
config SPI_THUNDERX
tristate "Cavium ThunderX SPI controller"
- depends on PCI && 64BIT && (ARM64 || COMPILE_TEST)
+ depends on PCI && 64BIT && (ARCH_THUNDER || COMPILE_TEST)
help
SPI host driver for the hardware found on Cavium ThunderX
SOCs.
@@ -680,7 +682,7 @@ config SPI_XCOMM
config SPI_XILINX
tristate "Xilinx SPI controller common module"
- depends on HAS_IOMEM
+ depends on HAS_IOMEM && (ARCH_ZYNQ || ARCH_ZYNQMP || COMPILE_TEST)
select SPI_BITBANG
help
This exposes the SPI controller IP from the Xilinx EDK.
@@ -715,7 +717,7 @@ config SPI_XTENSA_XTFPGA
config SPI_ZYNQMP_GQSPI
tristate "Xilinx ZynqMP GQSPI controller"
- depends on SPI_MASTER && HAS_DMA
+ depends on SPI_MASTER && HAS_DMA && (ARCH_ZYNQMP || COMPILE_TEST)
help
Enables Xilinx GQSPI controller driver for Zynq UltraScale+ MPSoC.
--
2.9.3
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2016-11-20 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-20 17:55 Peter Robinson [this message]
[not found] ` <20161120175505.2910-1-pbrobinson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-11-20 18:13 ` [PATCH v2] spi: make architecture specific hardware depend on the associated hardware Lars-Peter Clausen
2016-11-21 19:24 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161120175505.2910-1-pbrobinson@gmail.com \
--to=pbrobinson-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).