diff options
| author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2020-02-14 10:40:19 +0300 |
|---|---|---|
| committer | Peng Fan <peng.fan@nxp.com> | 2020-02-19 16:27:30 +0300 |
| commit | 9d86b89c590832c9bcb1c69d5ccdecdf731f97ae (patch) | |
| tree | f742792fc5c973819dac194426231f05e25e4ecd /arch/m68k | |
| parent | 950c5968672a22a65790534234d1106bd1303652 (diff) | |
| download | u-boot-9d86b89c590832c9bcb1c69d5ccdecdf731f97ae.tar.xz | |
dma-mapping: move dma_map_(un)single() to <linux/dma-mapping.h>
The implementation of dma_map_single() and dma_unmap_single() is
exactly the same for all the architectures that support them.
Factor them out to <linux/dma-mapping.h>, and make all drivers to
include <linux/dma-mapping.h> instead of <asm/dma-mapping.h>.
If we need to differentiate them for some architectures, we can
move the generic definitions to <asm-generic/dma-mapping.h>.
Add some comments to the helpers. The concept is quite similar to
the DMA-API of Linux kernel. Drivers are agnostic about what is
going on behind the scene. Just call dma_map_single() before the
DMA, and dma_unmap_single() after it.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'arch/m68k')
0 files changed, 0 insertions, 0 deletions