aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/staging/vme_user/Kconfig
diff options
context:
space:
mode:
Diffstat (limited to 'drivers/staging/vme_user/Kconfig')
-rw-r--r--drivers/staging/vme_user/Kconfig40
1 files changed, 40 insertions, 0 deletions
diff --git a/drivers/staging/vme_user/Kconfig b/drivers/staging/vme_user/Kconfig
new file mode 100644
index 000000000000..c8eabf8f40f1
--- /dev/null
+++ b/drivers/staging/vme_user/Kconfig
@@ -0,0 +1,40 @@
+# SPDX-License-Identifier: GPL-2.0
+menuconfig VME_BUS
+ bool "VME bridge support"
+ depends on STAGING && PCI
+ help
+ If you say Y here you get support for the VME bridge Framework.
+
+if VME_BUS
+
+comment "VME Bridge Drivers"
+
+config VME_TSI148
+ tristate "Tempe"
+ depends on HAS_DMA
+ help
+ If you say Y here you get support for the Tundra TSI148 VME bridge
+ chip.
+
+config VME_FAKE
+ tristate "Fake"
+ help
+ If you say Y here you get support for the fake VME bridge. This
+ provides a virtualised VME Bus for devices with no VME bridge. This
+ is mainly useful for VME development (in the absence of VME
+ hardware).
+
+comment "VME Device Drivers"
+
+config VME_USER
+ tristate "VME user space access driver"
+ depends on STAGING && VME_BUS
+ help
+ If you say Y here you want to be able to access a limited number of
+ VME windows in a manner at least semi-compatible with the interface
+ provided with the original driver at <http://www.vmelinux.org/>.
+
+ To compile this driver as a module, choose M here. The module will
+ be called vme_user. If unsure, say N.
+
+endif