From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dma_declare_coherent_memory: push ioremap() up to caller
Date: Fri, 24 Dec 2010 13:02:00 +0000 [thread overview]
Message-ID: <20101224130200.GG20587@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <201012240020.37208.jkrzyszt@tis.icnet.pl>
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.
next prev parent reply other threads:[~2010-12-24 13:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 23:20 [PATCH] dma_declare_coherent_memory: push ioremap() up to caller Janusz Krzysztofik
2010-12-23 23:54 ` Russell King - ARM Linux
2010-12-24 0:02 ` Paul Mundt
2010-12-24 1:08 ` Janusz Krzysztofik
2010-12-24 1:58 ` Paul Mundt
2010-12-24 13:02 ` Russell King - ARM Linux [this message]
2010-12-24 13:55 ` Janusz Krzysztofik
2010-12-24 15:41 ` Russell King - ARM Linux
2010-12-24 23:24 ` Janusz Krzysztofik
2010-12-26 17:45 ` Guennadi Liakhovetski
2010-12-27 10:29 ` Janusz Krzysztofik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101224130200.GG20587@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).