[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101224130200.GG20587@n2100.arm.linux.org.uk>
Date: Fri, 24 Dec 2010 13:02:00 +0000
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Janusz Krzysztofik <jkrzyszt@....icnet.pl>
Cc: linux-arch@...r.kernel.org, Greg Kroah-Hartman <gregkh@...e.de>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Arnd Bergmann <arnd@...db.de>,
Dan Williams <dan.j.williams@...el.com>,
linux-sh@...r.kernel.org, Paul Mundt <lethal@...ux-sh.org>,
Sascha Hauer <kernel@...gutronix.de>,
linux-usb@...r.kernel.org,
David Brownell <dbrownell@...rs.sourceforge.net>,
linux-media@...r.kernel.org,
Guennadi Liakhovetski <g.liakhovetski@....de>,
linux-scsi@...r.kernel.org,
"James E.J. Bottomley" <James.Bottomley@...e.de>,
Catalin Marinas <catalin.marinas@....com>
Subject: Re: [PATCH] dma_declare_coherent_memory: push ioremap() up to
caller
On Fri, Dec 24, 2010 at 12:20:32AM +0100, Janusz Krzysztofik wrote:
> The patch tries to implement a solution suggested by Russell King,
> http://lists.infradead.org/pipermail/linux-arm-kernel/2010-December/035264.html.
> It is expected to solve video buffer allocation issues for at least a
> few soc_camera I/O memory less host interface drivers, designed around
> the videobuf_dma_contig layer, which allocates video buffers using
> dma_alloc_coherent().
>
> Created against linux-2.6.37-rc5.
>
> Tested on ARM OMAP1 based Amstrad Delta with a WIP OMAP1 camera patch,
> patterned upon two mach-mx3 machine types which already try to use the
> dma_declare_coherent_memory() method for reserving a region of system
> RAM preallocated with another dma_alloc_coherent(). Compile tested for
> all modified files except arch/sh/drivers/pci/fixups-dreamcast.c.
Another note: with the pair of patches I've sent to the linux-arm-kernel
list earlier today changing the DMA coherent allocator to steal memory
from the system at boot.
This means there's less need to pre-allocate DMA memory - if there's
sufficient contiguous space in the DMA region to satisfy the allocation,
then the allocation will succeed. It's also independent of the maximum
page size from the kernel's memory allocators too.
So I suspect that mach-mx3 (and others) no longer need to do their own
pre-allocation anymore if both of these patches go in.
--
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