[PATCH v2] arm: make FORCE_MAX_ZONEORDER configurable for TI AM33XX

2012-09-25 Thread yegorslists
From: Yegor Yefremov yegorsli...@googlemail.com

FORCE_MAX_ZONEORDER of 12 is needed to allocation more than 4MB
of consistent DMA memory (da8xx frame buffer driver).

Signed-off-by: Dejan Gacnik dejan.gac...@gmail.com
Signed-off-by: Yegor Yefremov yegorsli...@googlemail.com
---
Changes:
v2: fix SA breakage

 arch/arm/Kconfig |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 2f88d8d..b5f242e 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -1766,8 +1766,8 @@ config HW_PERF_EVENTS
 source mm/Kconfig
 
 config FORCE_MAX_ZONEORDER
-   int Maximum zone order if ARCH_SHMOBILE
-   range 11 64 if ARCH_SHMOBILE
+   int Maximum zone order if ARCH_SHMOBILE || SOC_AM33XX
+   range 11 64 if ARCH_SHMOBILE || SOC_AM33XX
default 9 if SA
default 11
help
-- 
1.7.7

--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH v2] arm: make FORCE_MAX_ZONEORDER configurable for TI AM33XX

2012-09-25 Thread Russell King - ARM Linux
On Tue, Sep 25, 2012 at 10:26:30AM +0200, yegorsli...@googlemail.com wrote:
 From: Yegor Yefremov yegorsli...@googlemail.com
 
 FORCE_MAX_ZONEORDER of 12 is needed to allocation more than 4MB
 of consistent DMA memory (da8xx frame buffer driver).

Okay, so the patch description says This needs to be 12 on this platform.

  config FORCE_MAX_ZONEORDER
 - int Maximum zone order if ARCH_SHMOBILE
 - range 11 64 if ARCH_SHMOBILE
 + int Maximum zone order if ARCH_SHMOBILE || SOC_AM33XX
 + range 11 64 if ARCH_SHMOBILE || SOC_AM33XX

but you leave it up to the user to select something that may not be
suitable.  Wouldn't _just_ adding:

default 12 if SOC_AM33XX

after the range, and making no other changes be good enough and match
what the patch description says?
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH v2] arm: make FORCE_MAX_ZONEORDER configurable for TI AM33XX

2012-09-25 Thread Yegor Yefremov
On 25.09.2012 10:32, Russell King - ARM Linux wrote:
 On Tue, Sep 25, 2012 at 10:26:30AM +0200, yegorsli...@googlemail.com wrote:
 From: Yegor Yefremov yegorsli...@googlemail.com

 FORCE_MAX_ZONEORDER of 12 is needed to allocation more than 4MB
 of consistent DMA memory (da8xx frame buffer driver).
 
 Okay, so the patch description says This needs to be 12 on this platform.
 
  config FORCE_MAX_ZONEORDER
 -int Maximum zone order if ARCH_SHMOBILE
 -range 11 64 if ARCH_SHMOBILE
 +int Maximum zone order if ARCH_SHMOBILE || SOC_AM33XX
 +range 11 64 if ARCH_SHMOBILE || SOC_AM33XX
 
 but you leave it up to the user to select something that may not be
 suitable.  Wouldn't _just_ adding:
 
   default 12 if SOC_AM33XX
 
 after the range, and making no other changes be good enough and match
 what the patch description says?

You're right. As we don't allocate anything, but increase the possible size, it 
shouldn't break anything. Tony is it O.K. with you?

Patch sent.

Yegor

--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH v2] arm: make FORCE_MAX_ZONEORDER configurable for TI AM33XX

2012-09-25 Thread Tony Lindgren
* Yegor Yefremov yegor_s...@visionsystems.de [120925 01:47]:
 On 25.09.2012 10:32, Russell King - ARM Linux wrote:
  On Tue, Sep 25, 2012 at 10:26:30AM +0200, yegorsli...@googlemail.com wrote:
  From: Yegor Yefremov yegorsli...@googlemail.com
 
  FORCE_MAX_ZONEORDER of 12 is needed to allocation more than 4MB
  of consistent DMA memory (da8xx frame buffer driver).
  
  Okay, so the patch description says This needs to be 12 on this platform.
  
   config FORCE_MAX_ZONEORDER
  -  int Maximum zone order if ARCH_SHMOBILE
  -  range 11 64 if ARCH_SHMOBILE
  +  int Maximum zone order if ARCH_SHMOBILE || SOC_AM33XX
  +  range 11 64 if ARCH_SHMOBILE || SOC_AM33XX
  
  but you leave it up to the user to select something that may not be
  suitable.  Wouldn't _just_ adding:
  
  default 12 if SOC_AM33XX
  
  after the range, and making no other changes be good enough and match
  what the patch description says?
 
 You're right. As we don't allocate anything, but increase the possible size, 
 it shouldn't break anything. Tony is it O.K. with you?

Sure.

Tony
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html