From: Alexei Colin <acolin@isi.edu>
To: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Russell King <linux@armlinux.org.uk>,
Arnd Bergmann <arnd@arndb.de>
Cc: Alex Bounine <alex.bou9@gmail.com>,
Barry Wood <barry.wood@idt.com>,
John Paul Walters <jwalters@isi.edu>,
Alexei Colin <acolin@isi.edu>
Subject: [PATCH] arm: enable RapidIO config options in Kconfig
Date: Tue, 24 Jul 2018 09:41:26 -0400 [thread overview]
Message-ID: <20180724134122.86718-1-acolin@isi.edu> (raw)
ARM SoCs with a PCI bus offer the RapiodIO config menu; SoCs with
RapidIO IP blocks but without a PCI bus, need to add "select
HAS_RAPIDIO" to the Kconfig entry for that SoC (e.g. ARCH_*).
HAS_RAPIDIO was chosen over HAVE_RAPIDIO to be consistent with
other architectures which already define this flag (powerpc).
Signed-off-by: Alexei Colin <acolin@isi.edu>
---
Tested that kernel builds with RapidIO subsystem and switch drivers enabled.
Maintainers for RapidIO subsystem CCed.
Sending a similar patch to ARM64 maintainers shortly.
arch/arm/Kconfig | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 843edfd000be..d6267ab33cb5 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -1274,6 +1274,22 @@ config PCI_HOST_ITE8152
source "drivers/pci/Kconfig"
+config HAS_RAPIDIO
+ bool
+ default n
+
+config RAPIDIO
+ tristate "RapidIO support"
+ depends on HAS_RAPIDIO || PCI
+ help
+ This feature enables support for RapidIO high-performance
+ packet-switched interconnect.
+
+ If you say Y here, the kernel will include drivers and
+ infrastructure code to support RapidIO interconnect devices.
+
+source "drivers/rapidio/Kconfig"
+
source "drivers/pcmcia/Kconfig"
endmenu
--
2.18.0
next reply other threads:[~2018-07-24 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 13:41 Alexei Colin [this message]
2018-07-24 13:48 ` [PATCH] arm: enable RapidIO config options in Kconfig Arnd Bergmann
2018-07-24 14:02 ` Russell King - ARM Linux
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=20180724134122.86718-1-acolin@isi.edu \
--to=acolin@isi.edu \
--cc=alex.bou9@gmail.com \
--cc=arnd@arndb.de \
--cc=barry.wood@idt.com \
--cc=jwalters@isi.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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).