summaryrefslogtreecommitdiff
path: root/drivers/vme/bridges/Kconfig
diff options
context:
space:
mode:
authorMartyn Welch <martyn@welchs.me.uk>2016-07-07 19:51:52 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2016-08-31 13:21:12 +0200
commit658bcdae9c6755806e66b33e29d56b33a3ff421a (patch)
treebe7eda98fa75bf301f94f03de1c5c995710641af /drivers/vme/bridges/Kconfig
parent050c3d52cc7810d9d17b8cd231708609af6876ae (diff)
vme: Adding Fake VME driver
This patch introduces a fake VME bridge driver. This driver currently emulates a subset of the VME bridge functionality. This allows some VME subsystem development and even some VME device driver development to be carried out in the absence of a proper VME bus. Signed-off-by: Martyn Welch <martyn@welchs.me.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/vme/bridges/Kconfig')
-rw-r--r--drivers/vme/bridges/Kconfig8
1 files changed, 8 insertions, 0 deletions
diff --git a/drivers/vme/bridges/Kconfig b/drivers/vme/bridges/Kconfig
index f6d854584906..f6ddc3715401 100644
--- a/drivers/vme/bridges/Kconfig
+++ b/drivers/vme/bridges/Kconfig
@@ -13,3 +13,11 @@ config VME_TSI148
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).