1# SPDX-License-Identifier: GPL-2.0
2menuconfig VME_BUS
3	bool "VME bridge support"
4	depends on PCI
5	help
6	  Enable support for VME (VersaModular Eurocard bus) bridge modules.
7	  The bridge allows connecting VME devices to systems with existing
8	  interfaces (like USB or PCI) by means of translating VME protocol
9	  operations.
10
11	  Note that this only enables the bridge framework. You'll also
12	  likely want to enable driver for specific bridge device you have
13	  to actually use it. If unsure, say N.
14
15if VME_BUS
16
17comment "VME Bridge Drivers"
18
19config VME_TSI148
20	tristate "Tundra TSI148 VME bridge support"
21	depends on HAS_DMA
22	help
23	 If you say Y here you get support for the Tundra TSI148 VME-to-PCI/X
24	 bridge chip (and pin-compatible clones).
25
26	 TSI148 is a high-performant, 2eSST and VME64-compliant VME-to-PCI/X
27	 interconnect bridge with support for PCI and PCI-X bus interface.
28	 It is primarily used in industrial and embedded systems.
29
30	 To compile this driver as a module, say M - the module will be
31	 called vme_tsi148. If unsure, say N.
32
33config VME_FAKE
34	tristate "Fake"
35	help
36	 If you say Y here you get support for the fake VME bridge. This
37	 provides a virtualised VME Bus for devices with no VME bridge. This
38	 is mainly useful for VME development (in the absence of VME
39	 hardware).
40
41comment "VME Device Drivers"
42
43config VME_USER
44	tristate "VME user space access driver"
45	help
46	  If you say Y here you want to be able to access a limited number of
47	  VME windows in a manner at least semi-compatible with the interface
48	  provided with the original driver at <http://www.vmelinux.org/>.
49
50	  To compile this driver as a module, choose M here. The module will
51	  be called vme_user. If unsure, say N.
52
53endif
54