Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759463Ab3D3DCp (ORCPT ); Mon, 29 Apr 2013 23:02:45 -0400 Received: from mail-pd0-f182.google.com ([209.85.192.182]:46974 "EHLO mail-pd0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759266Ab3D3DCo (ORCPT ); Mon, 29 Apr 2013 23:02:44 -0400 From: Damian Hobson-Garcia To: linux-kernel@vger.kernel.org Cc: msalter@redhat.com, linux-c6x-dev@linux-c6x.org, Damian Hobson-Garcia Subject: [PATCH v2 2/4] c6x: Provide default implementation for dma_{alloc,free}_attrs Date: Tue, 30 Apr 2013 12:02:34 +0900 Message-Id: <1367290954-10496-1-git-send-email-dhobsong@igel.co.jp> X-Mailer: git-send-email 1.7.5.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1454 Lines: 34 Most architectures that define CONFIG_HAVE_DMA, have implementations for both dma_alloc_attrs() and dma_free_attrs(). All achitectures that do not define CONFIG_HAVE_DMA also have both of these definitions provided by dma-mapping-broken.h. Add default implementations for these functions on c6x. Signed-off-by: Damian Hobson-Garcia --- arch/c6x/include/asm/dma-mapping.h | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/arch/c6x/include/asm/dma-mapping.h b/arch/c6x/include/asm/dma-mapping.h index 88bd0d8..8947605 100644 --- a/arch/c6x/include/asm/dma-mapping.h +++ b/arch/c6x/include/asm/dma-mapping.h @@ -89,6 +89,9 @@ extern void dma_free_coherent(struct device *, size_t, void *, dma_addr_t); #define dma_alloc_noncoherent(d, s, h, f) dma_alloc_coherent((d), (s), (h), (f)) #define dma_free_noncoherent(d, s, v, h) dma_free_coherent((d), (s), (v), (h)) +#define dma_alloc_attrs(d, s, h, f, a) dma_alloc_coherent(d, s, h, f) +#define dma_free_attrs(d, s, h, f, a) dma_free_coherent(d, s, h, f) + /* Not supported for now */ static inline int dma_mmap_coherent(struct device *dev, struct vm_area_struct *vma, void *cpu_addr, -- 1.7.5.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/