Lines Matching refs:the

8     1.2 Limitations of the current implementation
19     4.3 Initializing the driver
24   This document describes the architecture and implementation of the MEN
29   This document is intended to be a short overview of the current
30   implementation and does by no means describe the complete possibilities of MCB
33 1.2 Limitations of the current implementation
36   that only use a single memory resource and share the PCI legacy IRQ.  Not
38   - Multi-resource MCB devices like the VME Controller or M-Module carrier.
49   - the parser for the Chameleon table.
57    FPGA contains a header section describing the content of the FPGA. The
58    header lists the device id, PCI BAR, offset from the beginning of the PCI
59    BAR, size in the FPGA, interrupt number and some other properties currently
60    not handled by the MCB implementation.
64    A carrier device is just an abstraction for the real world physical bus the
66    properties of the carrier device (like querying the IRQ number of a PCI
67    device). To provide abstraction from the real hardware bus, an MCB carrier
68    device provides callback methods to translate the driver's MCB function calls
70    implement the get_irq() method which can be translated into a hardware bus
71    query for the IRQ number the device should use.
75    The parser reads the first 512 bytes of a Chameleon device and parses the
76    Chameleon table. Currently the parser only supports the Chameleon v2 variant
77    of the Chameleon table but can easily be adopted to support an older or
78    possible future variant. While parsing the table's entries new MCB devices
79    are allocated and their resources are assigned according to the resource
80    assignment in the Chameleon table. After resource assignment is finished, the
81    MCB devices are registered at the MCB and thus at the driver core of the
87   per MCB device. But this is likely going to change in the future.
92    the MCB bus. This memory resource is the physical address of the MCB device
93    inside the carrier and is intended to be passed to ioremap() and friends. It
94    is already requested from the kernel by calling request_mem_region().
98    Each MCB device has exactly one IRQ resource, which can be requested from the
99    MCB bus. If a carrier device driver implements the ->get_irq() callback
100    method, the IRQ number assigned by the carrier device will be returned,
101    otherwise the IRQ number inside the Chameleon table will be returned. This
109     Each MCB driver has a structure to identify the device driver as well as
110     device ids which identify the IP Core inside the FPGA. The driver structure
112     removal from the system.
133    When a driver is loaded and the MCB devices it services are found, the MCB
134    core will call the driver's probe callback method. When the driver is removed
135    from the system, the MCB core will call the driver's remove callback method.
141 4.3 Initializing the driver
143    When the kernel is booted or your foo driver module is inserted, you have to
145    module at the MCB core.
160    The module_mcb_driver() macro can be used to reduce the above code.