Displaying 5 results from an estimated 5 matches for "of_device_dma_coherent_tbl".
2017 Feb 01
3
[PATCH] virtio: Try to untangle DMA coherency
...7 @@ int of_dma_get_range(struct device_node *np, u64 *dma_addr, u64 *paddr, u64 *siz
}
EXPORT_SYMBOL_GPL(of_dma_get_range);
+/*
+ * DMA from some device types is always cache-coherent, and in some unfortunate
+ * cases the "dma-coherent" property is not used.
+ */
+static const char *of_device_dma_coherent_tbl[] = {
+ /*
+ * Virtio MMIO devices are assumed to be cache-coherent when accessing
+ * main memory. Neither QEMU nor kvmtool emit "dma-coherent" properties
+ * for their generated virtio MMIO device nodes, and the binding
+ * documentation doesn't mention them either. When using t...
2017 Feb 01
3
[PATCH] virtio: Try to untangle DMA coherency
...7 @@ int of_dma_get_range(struct device_node *np, u64 *dma_addr, u64 *paddr, u64 *siz
}
EXPORT_SYMBOL_GPL(of_dma_get_range);
+/*
+ * DMA from some device types is always cache-coherent, and in some unfortunate
+ * cases the "dma-coherent" property is not used.
+ */
+static const char *of_device_dma_coherent_tbl[] = {
+ /*
+ * Virtio MMIO devices are assumed to be cache-coherent when accessing
+ * main memory. Neither QEMU nor kvmtool emit "dma-coherent" properties
+ * for their generated virtio MMIO device nodes, and the binding
+ * documentation doesn't mention them either. When using t...
2017 Feb 01
0
[PATCH] virtio: Try to untangle DMA coherency
...node *np, u64 *dma_addr, u64 *paddr, u64 *siz
> }
> EXPORT_SYMBOL_GPL(of_dma_get_range);
>
> +/*
> + * DMA from some device types is always cache-coherent, and in some unfortunate
> + * cases the "dma-coherent" property is not used.
> + */
> +static const char *of_device_dma_coherent_tbl[] = {
> + /*
> + * Virtio MMIO devices are assumed to be cache-coherent when accessing
> + * main memory. Neither QEMU nor kvmtool emit "dma-coherent" properties
> + * for their generated virtio MMIO device nodes, and the binding
> + * documentation doesn't mention...
2017 Feb 01
4
[PATCH] virtio: Try to untangle DMA coherency
By forcing on DMA API usage for ARM systems, we have inadvertently
kicked open a hornets' nest in terms of cache-coherency. Namely that
unless the virtio device is explicitly described as capable of coherent
DMA by firmware, the DMA APIs on ARM and other DT-based platforms will
assume it is non-coherent. This turns out to cause a big problem for the
likes of QEMU and kvmtool, which generate
2017 Feb 01
4
[PATCH] virtio: Try to untangle DMA coherency
By forcing on DMA API usage for ARM systems, we have inadvertently
kicked open a hornets' nest in terms of cache-coherency. Namely that
unless the virtio device is explicitly described as capable of coherent
DMA by firmware, the DMA APIs on ARM and other DT-based platforms will
assume it is non-coherent. This turns out to cause a big problem for the
likes of QEMU and kvmtool, which generate