public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Orjan Friberg <of@flatfrog.com>
To: linux-omap@vger.kernel.org
Subject: OMAP 3730 200 MHz SDRAM config
Date: Mon, 7 Mar 2011 15:46:16 +0100	[thread overview]
Message-ID: <4D74EFB8.9030406@flatfrog.com> (raw)

Hi,

I'm looking at configuring an OMAP 3730 board for 200 MHz SDRAM.

I've been looking at the kernel code (arch/arm/mach-omap2) the last
couple of days to try and figure out what I need to do.  We're basing 
ourselves off of the Beagleboard, so I tried copying the 200 MHz Hynix 
SDRAM entry for Beagleboard-xM but that didn't help: it still 
(re)programs the SDRC clock to 166 MHz.

* Does the kernel at all use or depend on the boot loader's SDRAM
config?  (I'm using u-boot with a prepended configuration header.)

* Does the SDRAM setup/clocking depend on the MPU rate at all?  I.e. do
I need to boot Linux in 1 GHz to be able to set 200 MHz SDRC clock?

The clock config is a bit convoluted, so I'd appreciate any help.


Thanks,
Orjan



Appendix:

I'm using a program (user-mode app) called 'bandwidth' (which has an ARM
port):
http://home.comcast.net/~fbui/bandwidth.html for measurements.

With big (several MB) sequential writes I get ~1170 MB/s.  The
theoretical max for a 166 MHz is 166*2 * 4 bytes = 1328 MB/s, so we're
almost at 90%.  We're not the only process accessing memory, and maybe
there's some loss due to SDRAM refresh etc.

-- 
Orjan Friberg
FlatFrog Laboratories AB

             reply	other threads:[~2011-03-07 14:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07 14:46 Orjan Friberg [this message]
     [not found] ` <6B47CFCE-FBCF-4CED-A1AB-E43C619FD174@mac.com>
2011-03-07 15:33   ` OMAP 3730 200 MHz SDRAM config Orjan Friberg

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=4D74EFB8.9030406@flatfrog.com \
    --to=of@flatfrog.com \
    --cc=linux-omap@vger.kernel.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