Lines Matching +full:master +full:- +full:level

5 -------------------
24 .. code-block:: c
30 		if (vdev->id.num >= USER_BUS_MAX)
41 dev->bridge->num.
49 -------------------
53 succeeds, a non-zero value should be returned. A zero return value indicates
59 The driver can request ownership of one or more master windows
66 bus cycle types required in 'cycle'. Master windows add a further set of
73 transfers to be provided in the route attributes. This is typically VME-to-MEM
74 and/or MEM-to-VME, though some hardware can support VME-to-VME and MEM-to-MEM
84 Master windows
85 --------------
87 Master windows provide access from the local processor[s] out onto the VME bus.
92 Master window configuration
95 Once a master window has been assigned :c:func:`vme_master_set` can be used to
102 Master window access
106 :c:func:`vme_master_write` used to write to configured master windows.
109 do a read-modify-write transaction. Parts of a VME window can also be mapped
114 -------------
152 ------------
154 The VME DMA transfer provides the ability to run link-list DMA transfers. The
155 API introduces the concept of DMA lists. Each DMA list is a link-list which can
193  - PCI source or destination: :c:func:`vme_dma_pci_attribute`
194  - VME source or destination: :c:func:`vme_dma_vme_attribute`
195  - Pattern source: :c:func:`vme_dma_pattern_attribute`
209 ----------
212 level and status ID combinations and for the generation of VME interrupts with
213 specific VME level and status IDs.
220 :c:func:`vme_irq_free` to free a specific VME level and status ID combination.
227 .. code-block:: c
229 	void callback(int level, int statid, void *priv);
236 at a given VME level and VME status ID.
240 -----------------
273 .. code-block:: c
279 --------------
285 -------------
291 -------
293 .. kernel-doc:: drivers/staging/vme_user/vme.h
296 .. kernel-doc:: drivers/staging/vme_user/vme.c