linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: prabhakar.lad@ti.com (Prabhakar Lad)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: relax conditions required for enabling Contiguous Memory Allocator
Date: Mon, 20 Aug 2012 16:59:57 +0530	[thread overview]
Message-ID: <50321FB5.90507@ti.com> (raw)
In-Reply-To: <1345443372-3824-1-git-send-email-m.szyprowski@samsung.com>

Hi Marek,

Thanks for the patch.

On Monday 20 August 2012 11:46 AM, 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>

  Reported-by: Prabhakar Lad <prabhakar.lad@ti.com>
  Tested-by: Prabhakar Lad <prabhakar.lad@ti.com>

Thx,
--Prabhakar

> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> ---
>  arch/arm/Kconfig |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index e91c7cd..6ef75e2 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -6,7 +6,7 @@ config ARM
>  	select HAVE_DMA_API_DEBUG
>  	select HAVE_IDE if PCI || ISA || PCMCIA
>  	select HAVE_DMA_ATTRS
> -	select HAVE_DMA_CONTIGUOUS if (CPU_V6 || CPU_V6K || CPU_V7)
> +	select HAVE_DMA_CONTIGUOUS if MMU
>  	select HAVE_MEMBLOCK
>  	select RTC_LIB
>  	select SYS_SUPPORTS_APM_EMULATION
> 

  reply	other threads:[~2012-08-20 11:29 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 [this message]
2012-08-20 20:01 ` Arnd Bergmann
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=50321FB5.90507@ti.com \
    --to=prabhakar.lad@ti.com \
    --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).