diff options
author | 2014-11-20 10:42:40 +0000 | |
---|---|---|
committer | 2014-12-04 12:41:51 +0000 | |
commit | 2e2a7817fdb6304f8c95c29dae0c93e2727240f4 (patch) | |
tree | 88735f6ed6157a9b2329d35c3d9576a10b4c9ff7 /arch/arm64 | |
parent | arm: introduce is_device_dma_coherent (diff) | |
download | linux-2e2a7817fdb6304f8c95c29dae0c93e2727240f4.tar.gz linux-2e2a7817fdb6304f8c95c29dae0c93e2727240f4.tar.bz2 linux-2e2a7817fdb6304f8c95c29dae0c93e2727240f4.zip |
xen/arm: use is_device_dma_coherent
Use is_device_dma_coherent to check whether we need to issue cache
maintenance operations rather than checking on the existence of a
particular dma_ops function for the device.
This is correct because coherent devices don't need cache maintenance
operations - arm_coherent_dma_ops does not set the hooks that we
were previously checking for existance.
Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
Diffstat (limited to 'arch/arm64')
0 files changed, 0 insertions, 0 deletions