Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Peter Barada <peterb@logicpd.com>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Problems with 2.6.29-rc8 and SDRAM on LDP
Date: Sun, 22 Mar 2009 12:41:21 -0400	[thread overview]
Message-ID: <1237740082.23022.9.camel@blackhole> (raw)

I'm basing a port of 2.6.29-rc8 (khilmans's PM branch) off of the LDP
configuration, and in arch/arm/mach-omap2/board-ldp, the call to
init_common_hw passes in four NULLs which cause the kernel to oops on
startup in omap2_sdrc_get_params, most likely because there is no
sdrc_params for it to sift through.

I tried to use the mt46j32m32lfc_sdrc_params(as in omap3beagle.c), but
that dies after the message "Reprogramming the SDRC" with a unhandled
fault, but no traceback.  I think this may be due to the OMAP2520LV SOM
board I'm using has a MT29C2G24MAKLAJG-6 IT instead of the MT46J32M32LFC
part, and SDRAM is all mucked up.

I assume that I have to create a sdram-mt29c262maklajg.h file that
contains the sdrc_params to use, but can anyone explain the differences
between the 5 entries in the array it would contain?  I know they are
tied to OPP levels, but "rate" seems to go down as the OPP level goes
up.  This doesn't make sense to me as I'd expect the rate to go up with
OPP level.  What am I missing?

-- 
Peter Barada <peterb@logicpd.com>

             reply	other threads:[~2009-03-22 16:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-22 16:41 Peter Barada [this message]
2009-03-23  6:38 ` Problems with 2.6.29-rc8 and SDRAM on LDP Paul Walmsley
2009-03-23  7:02   ` Paul Walmsley
2009-03-23 14:43   ` Peter Barada

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=1237740082.23022.9.camel@blackhole \
    --to=peterb@logicpd.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