linux/drivers/staging/android
Laura Abbott 204f672255 staging: android: ion: Use CMA APIs directly
When CMA was first introduced, its primary use was for DMA allocation
and the only way to get CMA memory was to call dma_alloc_coherent. This
put Ion in an awkward position since there was no device structure
readily available and setting one up messed up the coherency model.
These days, CMA can be allocated directly from the APIs. Switch to using
this model to avoid needing a dummy device. This also mitigates some of
the caching problems (e.g. dma_alloc_coherent only returning uncached
memory).

Signed-off-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-04-18 20:41:12 +02:00
..
ion staging: android: ion: Use CMA APIs directly 2017-04-18 20:41:12 +02:00
uapi staging: android: ion: Remove old platform support 2017-04-08 12:36:11 +02:00
ashmem.c staging: android: ashmem: lseek failed due to no FMODE_LSEEK. 2017-04-08 12:13:11 +02:00
ashmem.h
Kconfig staging, android: remove lowmemory killer from the tree 2017-03-09 13:47:03 +01:00
Makefile staging, android: remove lowmemory killer from the tree 2017-03-09 13:47:03 +01:00
TODO staging/android: remove Sync Framework tasks from TODO 2016-12-07 11:41:16 +01:00