search for: dma_declare_coherent_memori

Hi Amit and Rusty, I've been looking into the possibility of using the Virtio Console Driver together with the remoteproc framework to communicate with ST-Ericsson modem over shared memory. It seems like Virtio Console would be a good fit, except for a issue with buffer allocation. Due to HW limitations the STE-Modem cannot access kernel memory (no IOMMU and limited address range). Instead

Hi Amit and Rusty, I've been looking into the possibility of using the Virtio Console Driver together with the remoteproc framework to communicate with ST-Ericsson modem over shared memory. It seems like Virtio Console would be a good fit, except for a issue with buffer allocation. Due to HW limitations the STE-Modem cannot access kernel memory (no IOMMU and limited address range). Instead

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

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