staging: android: ion: Use CMA APIs directly

Browse source

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>

...

This commit is contained in:

Laura Abbott 2017-04-18 11:27:05 -07:00 • committed by Greg Kroah-Hartman

parent e4231bcda7

commit 204f672255

4 changed files with 39 additions and 72 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

7

drivers/staging/android/ion/Kconfig

View file

3

drivers/staging/android/ion/Makefile

View file

97

drivers/staging/android/ion/ion_cma_heap.c

View file

4

drivers/staging/android/ion/ion_heap.c

View file