Lines Matching refs:MCB

17    4 Writing an MCB driver
28 Chameleon Bus (called MCB throughout this document).
34 implementation and does by no means describe the complete possibilities of MCB
44 - Multi-resource MCB devices like the VME Controller or M-Module carrier.
45 - MCB devices that need another MCB device, like SRAM for a DMA Controller's
48   per MCB device like PCIe based carriers with MSI or MSI-X support.
53 MCB is divided into 3 functional blocks:
56 - drivers for MCB Carrier Devices and
69 not handled by the MCB implementation.
77 device). To provide abstraction from the real hardware bus, an MCB carrier
78 device provides callback methods to translate the driver's MCB function calls
89 possible future variant. While parsing the table's entries new MCB devices
92 MCB devices are registered at the MCB and thus at the driver core of the
99 per MCB device. But this is likely going to change in the future.
104 Each MCB device has exactly one memory resource, which can be requested from
105 the MCB bus. This memory resource is the physical address of the MCB device
112 Each MCB device has exactly one IRQ resource, which can be requested from the
113 MCB bus. If a carrier device driver implements the ->get_irq() callback
118 Writing an MCB driver
124 Each MCB driver has a structure to identify the device driver as well as
148 When a driver is loaded and the MCB devices it services are found, the MCB
150 from the system, the MCB core will call the driver's remove callback method::
160 module at the MCB core::