mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: barebox@lists.infradead.org,
	Maxime Ripard <maxime.ripard@free-electrons.com>,
	jimwall@q.com, brian@crystalfontz.com
Subject: Re: [PATCH v2] cfa10036: Retrieve the RAM size at runtime
Date: Sat, 30 Mar 2013 11:39:00 +0100	[thread overview]
Message-ID: <20130330103900.GV1906@pengutronix.de> (raw)
In-Reply-To: <1364395236-539-1-git-send-email-alexandre.belloni@free-electrons.com>

On Wed, Mar 27, 2013 at 03:40:36PM +0100, Alexandre Belloni wrote:
> The cfa-10036 comes in two flavours, with either 128MB or 256MB of RAM
> on it.
> 
> Since it's not stored anywhere, we need to runtime detect it by
> introducing the cfa10036_get_ram_size function.
> 
> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>

Applied, thanks.

> Cc: Maxime Ripard <maxime.ripard@free-electrons.com>
> ---
> changes since v1:
>   - stripped cfa10036_get_ram_size as suggested by Sacha
>   - I'm not too happy about the v5_mmu_cache_flush definition and call but that
> 	has to be done, else we are not reading the modified value, even on 128MB
> 	boards.

So your data cache works. That's good news ;)

Sascha

> 
> 
>  arch/arm/boards/crystalfontz-cfa10036/cfa10036.c |   18 +++++++++++++++++-
>  1 file changed, 17 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/arm/boards/crystalfontz-cfa10036/cfa10036.c b/arch/arm/boards/crystalfontz-cfa10036/cfa10036.c
> index 1bc20cf..a37b089 100644
> --- a/arch/arm/boards/crystalfontz-cfa10036/cfa10036.c
> +++ b/arch/arm/boards/crystalfontz-cfa10036/cfa10036.c
> @@ -90,9 +90,25 @@ static struct i2c_gpio_platform_data i2c_gpio_pdata = {
>  	.udelay			= 5,		/* ~100 kHz */
>  };
>  
> +void v5_mmu_cache_flush(void);
> +long cfa10036_get_ram_size(void)
> +{
> +	volatile u32 *base = (void *)IMX_MEMORY_BASE;
> +	volatile u32 *ofs = base + SZ_128M / sizeof(u32);
> +
> +	*base = *ofs = 0xdeadbeef;
> +	*ofs = 0xbaadcafe;
> +
> +	v5_mmu_cache_flush();
> +	if (*base == 0xbaadcafe)
> +		return SZ_128M;
> +	else
> +		return SZ_256M;
> +}
> +
>  static int cfa10036_mem_init(void)
>  {
> -	arm_add_mem_device("ram0", IMX_MEMORY_BASE, 128 * 1024 * 1024);
> +	arm_add_mem_device("ram0", IMX_MEMORY_BASE, cfa10036_get_ram_size());
>  
>  	return 0;
>  }
> -- 
> 1.7.10.4
> 
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
> 

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

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      parent reply	other threads:[~2013-03-30 10:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 14:40 Alexandre Belloni
2013-03-29 14:21 ` Maxime Ripard
2013-03-30 10:39 ` Sascha Hauer [this message]

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=20130330103900.GV1906@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=barebox@lists.infradead.org \
    --cc=brian@crystalfontz.com \
    --cc=jimwall@q.com \
    --cc=maxime.ripard@free-electrons.com \
    /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