search for: dma_declare_coherent_memory

Displaying 4 results from an estimated 4 matches for "dma_declare_coherent_memory".

2012 Jun 01
2
Question regarding Virtio Console and Remoteproc
...this I cannot use kmalloc() for buffer allocation, but I have to allocate buffers from the memory region shared with the modem. In remoteproc this is solved by using dma_alloc_coherent() for all memory to be shared with the modem. This works fine for me, because I can pass the IPC memory region to dma_declare_coherent_memory() so dma_alloc_coherent() will allocate from this memory region. I think I can solve this issue in Virtio Console by changing calls to kmalloc() to something like: if (virtio_has_feature(vdev, VIRTIO_CONSOLE_USE_DMA_MEM)) { dma_addr_t dma; buf = dma_alloc_coherent(dev, size, &dma, GFP_K...
2012 Jun 01
2
Question regarding Virtio Console and Remoteproc
...this I cannot use kmalloc() for buffer allocation, but I have to allocate buffers from the memory region shared with the modem. In remoteproc this is solved by using dma_alloc_coherent() for all memory to be shared with the modem. This works fine for me, because I can pass the IPC memory region to dma_declare_coherent_memory() so dma_alloc_coherent() will allocate from this memory region. I think I can solve this issue in Virtio Console by changing calls to kmalloc() to something like: if (virtio_has_feature(vdev, VIRTIO_CONSOLE_USE_DMA_MEM)) { dma_addr_t dma; buf = dma_alloc_coherent(dev, size, &dma, GFP_K...
2007 Jul 09
21
mthca use of dma_sync_single is bogus
It seems the problems running mthca in a Xen domU have uncovered a bug in mthca: mthca uses dma_sync_single in mthca_arbel_write_mtt_seg() and mthca_arbel_map_phys_fmr() to sync the MTTs that get written. However, Documentation/DMA-API.txt says: void dma_sync_single(struct device *dev, dma_addr_t dma_handle, size_t size, enum dma_data_direction direction) synchronise a single
2020 Aug 19
39
a saner API for allocating DMA addressable pages
Hi all, this series replaced the DMA_ATTR_NON_CONSISTENT flag to dma_alloc_attrs with a separate new dma_alloc_pages API, which is available on all platforms. In addition to cleaning up the convoluted code path, this ensures that other drivers that have asked for better support for non-coherent DMA to pages with incurring bounce buffering over can finally be properly supported. I'm still a