Documentation/driver-api/men-chameleon-bus.rst

30 ----------------------
34 based devices.
37 -----------------------------------------
39 The current implementation is limited to PCI and PCIe based carrier devices
43 - Multi-resource MCB devices like the VME Controller or M-Module carrier.
44 - MCB devices that need another MCB device, like SRAM for a DMA Controller's
46 - A per-carrier IRQ domain for carrier devices that have one (or more) IRQs
47   per MCB device like PCIe based carriers with MSI or MSI-X support.
54 - The MEN Chameleon Bus itself,
55 - drivers for MCB Carrier Devices and
56 - the parser for the Chameleon table.
59 -----------------
62 called Chameleon FPGA device found on some hardware produced my MEN Mikro
63 Elektronik GmbH. These devices are multi-function devices implemented in a
64 single FPGA and usually attached via some sort of PCI or PCIe link. Each
65 FPGA contains a header section describing the content of the FPGA. The
67 BAR, size in the FPGA, interrupt number and some other properties currently
71 ---------------
74 Chameleon FPGA is attached to. Some IP Core drivers may need to interact with
83 ------
101 ----------------
109 ----
112 MCB bus. If a carrier device driver implements the ->get_irq() callback
121 --------------------
124 device ids which identify the IP Core inside the FPGA. The driver structure
136 		.name = "foo-bar",
145 ---------------------
155 -----------------------