use the generic dma-noncoherent code for openrisc
Hi Openrisc maintainers,
can you review these patches to switch openrisc to use the generic dma-noncoherent code? All the requirements are in mainline already and we've switched various architectures over to it already.
PATCH 1/4 openrisc: remove the sync_single_for_cpu DMA operation
openrisc does all the required cache maintainance at dma map time, and none at unmap time. It thus has to implement sync_single_for_device to match the map cace for buffer reuse, but there is no point in doing another invalidation in the sync_single_cpu_case, which in terms of cache maintainance is equivalent to the unmap case.
--- arch/openrisc/kernel/dma.c | 15 --------------- 1 file changed, 15 deletions(-)
arch/openrisc/kernel/dma.c +0 -15
@@ -208,20 +208,6 @@ or1k_unmap_sg(struct device *dev, struct scatterlist *sg, } } -static void -or1k_sync_single_for_cpu (struct device *dev, -dma_addr_t dma_handle,size_t size, -enum dma_data_direction dir) -{ -unsigned long cl; -dma_addr_t addr = dma_handle; -struct cpuinfo_or1k *cpuinfo = &cpuinfo_or1k[smp_processor_id ()]; - -/* Invalidate the dcache for the requested range */ -for (cl = addr; cl < addr + size; cl += cpuinfo->dcache_block_size) -mtspr (SPR_DCBIR , cl); -} - static void or1k_sync_single_for_device(struct device *dev, dma_addr_t dma_handle, size_t size,
@@ -243,7 +229,6 @@ const struct dma_map_ops or1k_dma_map_ops = { .unmap_page = or1k_unmap_page, .map_sg = or1k_map_sg, .unmap_sg = or1k_unmap_sg, - .sync_single_for_cpu = or1k_sync_single_for_cpu, .sync_single_for_device = or1k_sync_single_for_device, };EXPORT_SYMBOL (or1k_dma_map_ops);
Signature · 1 line
2.18.0
PATCH 2/4 openrisc: remove the no-op unmap_page and unmap_sg DMA operations
In reply to Christoph Hellwig--- arch/openrisc/kernel/dma.c | 23 ----------------------- 1 file changed, 23 deletions(-)
arch/openrisc/kernel/dma.c +0 -23
@@ -171,14 +171,6 @@ or1k_map_page(struct device *dev, struct page *page,return addr; } -static void -or1k_unmap_page (struct device *dev,dma_addr_t dma_handle, -size_t size,enum dma_data_direction dir, -unsigned long attrs) -{ -/* Nothing special to do here... */ -} - static int or1k_map_sg(struct device *dev, struct scatterlist *sg, int nents, enum dma_data_direction dir,
@@ -195,19 +187,6 @@ or1k_map_sg(struct device *dev, struct scatterlist *sg,return nents; } -static void -or1k_unmap_sg (struct device *dev,struct scatterlist *sg, -int nents,enum dma_data_direction dir, -unsigned long attrs) -{ -struct scatterlist *s; -int i; - -for_each_sg (sg, s, nents, i) { -or1k_unmap_page (dev,sg_dma_address (s),sg_dma_len (s), dir,0 ); - } -} - static void or1k_sync_single_for_device(struct device *dev, dma_addr_t dma_handle, size_t size,
@@ -226,9 +205,7 @@ const struct dma_map_ops or1k_dma_map_ops = { .alloc = or1k_dma_alloc, .free = or1k_dma_free, .map_page = or1k_map_page, - .unmap_page = or1k_unmap_page, .map_sg = or1k_map_sg, - .unmap_sg = or1k_unmap_sg, .sync_single_for_device = or1k_sync_single_for_device, };EXPORT_SYMBOL (or1k_dma_map_ops);
Signature · 1 line
2.18.0
PATCH 3/4 openrisc: fix cache maintainance the the sync_single_for_device DMA operation
In reply to Christoph HellwigThe cache maintaince in the sync_single_for_device operation should be equivalent to the map_page operation to facilitate reusing buffers. Fix the openrisc implementation by moving the cache maintaince performed in map_page into the sync_single method, and calling that from map_page.
--- arch/openrisc/kernel/dma.c | 42 +++++++++++++++++--------------------- 1 file changed, 19 insertions(+), 23 deletions(-)
arch/openrisc/kernel/dma.c +19 -23
@@ -133,19 +133,15 @@ or1k_dma_free(struct device *dev, size_t size, void *vaddr,free_pages_exact (vaddr, size); } -static dma_addr_t -or1k_map_page (struct device *dev,struct page *page, -unsigned long offset,size_t size, -enum dma_data_direction dir, -unsigned long attrs) +static void +or1k_sync_single_for_device (struct device *dev, +dma_addr_t dma_handle,size_t size, +enum dma_data_direction dir) {unsigned long cl; -dma_addr_t addr =page_to_phys (page) + offset; +dma_addr_t addr = dma_handle;struct cpuinfo_or1k *cpuinfo = &cpuinfo_or1k[smp_processor_id ()]; -if (attrs &DMA_ATTR_SKIP_CPU_SYNC ) -return addr; -switch (dir) {case DMA_TO_DEVICE :/* Flush the dcache for the requested range */
@@ -168,6 +164,20 @@ or1k_map_page(struct device *dev, struct page *page,break ; } +} + +static dma_addr_t +or1k_map_page (struct device *dev,struct page *page, +unsigned long offset,size_t size, +enum dma_data_direction dir, +unsigned long attrs) +{ +unsigned long cl; +dma_addr_t addr =page_to_phys (page) + offset; +struct cpuinfo_or1k *cpuinfo = &cpuinfo_or1k[smp_processor_id ()]; + +if (!(attrs &DMA_ATTR_SKIP_CPU_SYNC )) +or1k_sync_single_for_device (dev, addr, size, dir);return addr; }
@@ -187,20 +197,6 @@ or1k_map_sg(struct device *dev, struct scatterlist *sg,return nents; } -static void -or1k_sync_single_for_device (struct device *dev, -dma_addr_t dma_handle,size_t size, -enum dma_data_direction dir) -{ -unsigned long cl; -dma_addr_t addr = dma_handle; -struct cpuinfo_or1k *cpuinfo = &cpuinfo_or1k[smp_processor_id ()]; - -/* Flush the dcache for the requested range */ -for (cl = addr; cl < addr + size; cl += cpuinfo->dcache_block_size) -mtspr (SPR_DCBFR , cl); -} -const struct dma_map_ops or1k_dma_map_ops = { .alloc = or1k_dma_alloc, .free = or1k_dma_free,
Signature · 1 line
2.18.0
PATCH 4/4 openrisc: use generic dma_noncoherent_ops
In reply to Christoph HellwigSwitch to the generic noncoherent direct mapping implementation.
--- arch/openrisc/Kconfig | 2 + arch/openrisc/include/asm/Kbuild | 1 + arch/openrisc/include/asm/dma-mapping.h | 35 ------------- arch/openrisc/kernel/dma.c | 65 ++++--------------------- 4 files changed, 12 insertions(+), 91 deletions(-) delete mode 100644 arch/openrisc/include/asm/dma-mapping.h
arch/openrisc/Kconfig +2 -0
@@ -6,6 +6,8 @@ config OPENRISC def_bool y + select ARCH_HAS_SYNC_DMA_FOR_DEVICE + select DMA_NONCOHERENT_OPS select OF select OF_EARLY_FLATTREE select IRQ_DOMAIN
arch/openrisc/include/asm/Kbuild +1 -0
@@ -7,6 +7,7 @@ generic-y += current.h generic-y += device.h generic-y += div64.h generic-y += dma.h +generic-y += dma-mapping.h generic-y += emergency-restart.h generic-y += exec.h generic-y += extable.h
arch/openrisc/include/asm/dma-mapping.h deleted +0 -35
@@ -1,35 +0,0 @@ -/* -* OpenRISC Linux -* -* Linux architectural port borrowing liberally from similar works of -* others. All original copyrights apply as per the original source -* declaration. -* -* OpenRISC implementation: -* Copyright (C) 2010-2011 Jonas Bonn <[email protected]> -* -* This program is free software; you can redistribute it and/or modify -* it under the terms of the GNU General Public License as published by -* the Free Software Foundation; either version 2 of the License, or -* (at your option) any later version. -*/ - -#ifndef __ASM_OPENRISC_DMA_MAPPING_H -#define __ASM_OPENRISC_DMA_MAPPING_H - -/* -* See Documentation/DMA-API-HOWTO.txt and -* Documentation/DMA-API.txt for documentation. -*/ - -#include <linux/dma-debug.h> -#include <linux/dma-mapping.h> - -extern const struct dma_map_ops or1k_dma_map_ops; - -static inline const struct dma_map_ops *get_arch_dma_ops (struct bus_type *bus) -{ -return &or1k_dma_map_ops; -} - -#endif /* __ASM_OPENRISC_DMA_MAPPING_H */
arch/openrisc/kernel/dma.c +9 -56
95 lines not on this page · raw message
Signature · 1 line
2.18.0
Stafford Horne
maintainerQuoted 5 lines · Christoph Hellwig
Hi Openrisc maintainers,
can you review these patches to switch openrisc to use the generic dma-noncoherent code? All the requirements are in mainline already and we've switched various architectures over to it already.
Hi Christoph,
Thanks for this, these look good to me. I don't know much about the dma infrastructure in the kernel to tell the truth, but the patches do maintain the original cache flushing and invalidation core logic and I don't see any problems.
I have applied these and ran my regular tests, but I don't really have any DMA hardware so the testing doesn't mean much.
For upstreaming, do you want me to send these through the openrisc tree, or do you want to send with the dma tree?
-Stafford
Quoted 2 lines · Stafford Horne
For upstreaming, do you want me to send these through the openrisc tree, or do you want to send with the dma tree?
Feel free to merge them through the openrisc tree.