linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* [RFC PATCH] ARM: mxc: Select ARCH_HAS_HOLES_MEMORYMODEL
@ 2011-09-16  0:29 Fabio Estevam
  2011-09-19  9:26 ` Sascha Hauer
  0 siblings, 1 reply; 2+ messages in thread
From: Fabio Estevam @ 2011-09-16  0:29 UTC (permalink / raw)
  To: linux-arm-kernel

Select ARCH_HAS_HOLES_MEMORYMODELfor ARCH_MXC so that the non-contiguous memory block
can be handled correctly.

An example of such system is MX35PDK that has a total of 256MB dividedin 
two RAM banks:128MB at CS0 and another 128MB at CS1. On MX35 each chip select 
can address up to 256MB, so this configuration leaves a 128MB 'hole' in the 
memory map that needs to be handled properly.

Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
---
 arch/arm/Kconfig |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 5ebc5d9..29bbd1d 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -397,6 +397,7 @@ config ARCH_MXC
 	select CLKSRC_MMIO
 	select GENERIC_IRQ_CHIP
 	select HAVE_SCHED_CLOCK
+	select ARCH_HAS_HOLES_MEMORYMODEL
 	help
 	  Support for Freescale MXC/iMX-based family of processors
 
-- 
1.6.0.4

^ permalink raw reply related	[flat|nested] 2+ messages in thread

* [RFC PATCH] ARM: mxc: Select ARCH_HAS_HOLES_MEMORYMODEL
  2011-09-16  0:29 [RFC PATCH] ARM: mxc: Select ARCH_HAS_HOLES_MEMORYMODEL Fabio Estevam
@ 2011-09-19  9:26 ` Sascha Hauer
  0 siblings, 0 replies; 2+ messages in thread
From: Sascha Hauer @ 2011-09-19  9:26 UTC (permalink / raw)
  To: linux-arm-kernel

On Thu, Sep 15, 2011 at 09:29:41PM -0300, Fabio Estevam wrote:
> Select ARCH_HAS_HOLES_MEMORYMODELfor ARCH_MXC so that the non-contiguous memory block
> can be handled correctly.
> 
> An example of such system is MX35PDK that has a total of 256MB dividedin 
> two RAM banks:128MB at CS0 and another 128MB at CS1. On MX35 each chip select 
> can address up to 256MB, so this configuration leaves a 128MB 'hole' in the 
> memory map that needs to be handled properly.

Why exactly do we need this? I remember a custom i.MX25 board which also
has a memory hole, but I can't remember adding ARCH_HAS_HOLES_MEMORYMODEL
for it.

Sascha

> 
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
>  arch/arm/Kconfig |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index 5ebc5d9..29bbd1d 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -397,6 +397,7 @@ config ARCH_MXC
>  	select CLKSRC_MMIO
>  	select GENERIC_IRQ_CHIP
>  	select HAVE_SCHED_CLOCK
> +	select ARCH_HAS_HOLES_MEMORYMODEL
>  	help
>  	  Support for Freescale MXC/iMX-based family of processors
>  
> -- 
> 1.6.0.4
> 
> 

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-09-19  9:26 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-09-16  0:29 [RFC PATCH] ARM: mxc: Select ARCH_HAS_HOLES_MEMORYMODEL Fabio Estevam
2011-09-19  9:26 ` Sascha Hauer

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).