Lines Matching refs:DMA

7 Most of the Slave DMA controllers have the same general principles of
10 They have a given number of channels to use for the DMA transfers, and
19 DMA-eligible devices to the controller itself. Whenever the device
20 will want to start a transfer, it will assert a DMA request (DRQ) by
23 A very simple DMA controller would only take into account a single
34 is why most if not all of the DMA controllers can adjust this, using a
37 Moreover, some DMA controllers, whenever the RAM is used as a source
45 Our theoretical DMA controller would then only be able to do transfers
53 quite simple DMA controller that doesn't support it, and we'll have to
54 implement it in software, or we have a more advanced DMA controller,
63 or the first item of the list to one channel of the DMA controller,
68 your hardware. Each DMA controller will require a different structure,
76 whenever you're willing to use DMA.
83 DMA Support in Linux
86 Historically, DMA controller drivers have been implemented using the
182       called on a regular basis through the DMA controller interrupt
343     - it's a DMA transaction ID that will increment over time.
362       dma_unmap_sg() in between 2 transfers, because the DMA'd data wasn't used,