Lines Matching +full:slave +full:- +full:kernel

5 -------------------
7 As with other subsystems within the Linux kernel, VME device drivers register
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
60 (:c:func:`vme_master_request`), slave windows (:c:func:`vme_slave_request`)
64 attributes of the driver in question. For slave windows these attributes are
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
85 --------------
109 do a read-modify-write transaction. Parts of a VME window can also be mapped
113 Slave windows
114 -------------
116 Slave windows provide devices on the VME bus access into mapped portions of the
122 Slave window configuration
125 Once a slave window has been assigned :c:func:`vme_slave_set` can be used to
133 Slave window buffer allocation
144 Slave window access
147 Slave windows map local memory onto the VME bus, the standard methods for
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 ----------
227 .. code-block:: c
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