Documentation/driver-api/vme.rst

1 VME Device Drivers
7 As with other subsystems within the Linux kernel, VME device drivers register
8 with the VME subsystem, typically called from the devices init routine.  This is
19 The '.match' function allows control over which VME devices should be registered
43 A function is also provided to unregister the driver from the VME core called
51 Once a driver has registered with the VME core the provided match routine will
57 requesting VME resources.
65 split into the VME address spaces that need to be accessed in 'aspace' and VME
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
87 Master windows provide access from the local processor[s] out onto the VME bus.
109 do a read-modify-write transaction. Parts of a VME window can also be mapped
116 Slave windows provide devices on the VME bus access into mapped portions of the
138 contiguous buffers which will be accessible by the VME bridge. These functions
140 care must be taken to ensure that they are contiguous and accessible by the VME
147 Slave windows map local memory onto the VME bus, the standard methods for
154 The VME DMA transfer provides the ability to run link-list DMA transfers. The
183 	source or destination is in an unsupported VME address space.
190 of source and destination. There are functions to create attributes for PCI, VME
194  - VME source or destination: :c:func:`vme_dma_vme_attribute`
211 The VME API provides functions to attach and detach callbacks to specific VME
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.
235 The function :c:func:`vme_irq_generate` can be used to generate a VME interrupt
236 at a given VME level and VME status ID.
242 The VME API provides the following functionality to configure the location
290 VME API