[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20070131220714.GB8999@flint.arm.linux.org.uk>
Date: Wed, 31 Jan 2007 22:07:14 +0000
From: Russell King <rmk+lkml@....linux.org.uk>
To: Jeff Garzik <jeff@...zik.org>
Cc: ak@...e.de, Andrew Morton <akpm@...l.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86-64: define dma noncoherent API functions
On Wed, Jan 31, 2007 at 07:41:07AM -0500, Jeff Garzik wrote:
> x86-64 is missing these:
>
> Signed-off-by: Jeff Garzik <jeff@...zik.org>
>
> diff --git a/include/asm-x86_64/dma-mapping.h b/include/asm-x86_64/dma-mapping.h
> index be9ec68..49dbab0 100644
> --- a/include/asm-x86_64/dma-mapping.h
> +++ b/include/asm-x86_64/dma-mapping.h
> @@ -63,6 +63,9 @@ static inline int dma_mapping_error(dma_addr_t dma_addr)
> return (dma_addr == bad_dma_address);
> }
>
> +#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)
> +
What are these, and why haven't they been discussed in such places as
linux-arch so that architecture maintainers can comment on them ?
Ditto for the recently added dma_sync_range_whatever functions ?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists