From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: relax conditions required for enabling Contiguous Memory Allocator
Date: Mon, 20 Aug 2012 20:01:23 +0000 [thread overview]
Message-ID: <201208202001.23443.arnd@arndb.de> (raw)
In-Reply-To: <1345443372-3824-1-git-send-email-m.szyprowski@samsung.com>
On Monday 20 August 2012, Marek Szyprowski wrote:
> Contiguous Memory Allocator requires only paging and MMU enabled not
> particular CPU architectures, so there is no need for strict dependency
> on CPU type. This enables to use CMA on some older ARM v5 systems which
> also might need large contiguous blocks for the multimedia processing hw
> modules.
>
> Reported-by: Prabhakar Lad <prabhakar.csengg@gmail.com>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
The patch looks simple, but I want a better explanation for it.
When we went through all possible cases, we decided that:
* ARMv6+ need CMA to avoid the double mapping problem.
* ARMv4/v5 cannot generally use CMA because it doesn't work
together with DMABOUNCE. I don't remember if it was the
only problem, but I definitely remember this was intentional.
* We want a common kernel for all ARMv6+ eventually, and a
separate kernel for all ARMv4/v5 ones.
If the reasoning has changed, please try to explain the full
situation. On a related topic, what happened to the idea that
ARMv6+ is broken without CMA? I noticed that it's optional
now.
Arnd
next prev parent reply other threads:[~2012-08-20 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 6:16 [PATCH] ARM: relax conditions required for enabling Contiguous Memory Allocator Marek Szyprowski
2012-08-20 11:29 ` Prabhakar Lad
2012-08-20 20:01 ` Arnd Bergmann [this message]
2012-08-21 12:12 ` Russell King - ARM Linux
2012-08-21 14:47 ` Marek Szyprowski
2012-08-21 14:46 ` Marek Szyprowski
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=201208202001.23443.arnd@arndb.de \
--to=arnd@arndb.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.