public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Pihet <jpihet@mvista.com>
To: Paul Walmsley <paul@pwsan.com>,
	"Syed Mohammed, Khasim" <khasim@ti.com>,
	"Kridner, Jason" <jdk@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>
Subject: Re: Beagleboard rev C memory timings & suspend/resume
Date: Fri, 8 May 2009 10:13:02 +0200	[thread overview]
Message-ID: <200905081013.02445.jpihet@mvista.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0905071316160.17514@utopia.booyaka.com>

On Thursday 07 May 2009 21:18:41 Paul Walmsley wrote:
> Hello Jean,
>
> one other suggestion.  You mentioned that you had self-refresh working on
> another OMAP3430 board with two SDRAM chip-selects.  You might consider
> dumping the SDRC registers from that board, and dumping the SDRC registers
> on Beagle rev C, and comparing.  It could be that the bootloader on your
> other board is setting some important bit.
The comparison gives the following:
- the timings are slightly different but given that the parts are not the same 
I do not think it is a problem
- the fields FIXEDDELAY and MODEFIXEDDELAYINITLAT are set in SDRC_DLLA_CTRL, 
the register value is 0x2600000A. Does that affect the 166MHz operation?
- the field DEEPPD of SDRC_MCFG_p is set to 0. That setting could affect the 
suspend/resume
- the MUX scheme is different: ADDRMUXLEGACY is set to 0
- the field BANKALLOCATION of SDRC_MCFG_p is set to 0 instead of 2

I tried to change those fields on the Beagleboard but still suspending for 
more than 10sec corrupts the memory.

> - Paul

Regards,
Jean

  reply	other threads:[~2009-05-08  8:13 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-29 13:53 Beagleboard rev C memory timings & suspend/resume Jean Pihet
2009-05-06 23:39 ` Paul Walmsley
2009-05-07 11:18   ` Jean Pihet
2009-05-07 16:44     ` Jean Pihet
2009-05-07 18:59       ` Paul Walmsley
2009-05-08  7:05         ` Jean Pihet
2009-05-08 22:43           ` Paul Walmsley
2009-05-11 19:10             ` Jean Pihet
2009-05-11 20:27               ` Paul Walmsley
2009-05-26 13:27                 ` [RFC][PATCH] OMAP3: add support for 2 SDRAM chip selects (was: Re: Beagleboard rev C memory timings & suspend/resume) Jean Pihet
2009-06-02 23:40                   ` Paul Walmsley
2009-06-03  7:03                     ` Jean Pihet
2009-06-05 15:35                     ` Jean Pihet
2009-06-05 18:10                       ` Paul Walmsley
2009-06-08  7:37                         ` Tero.Kristo
2009-06-08  8:59                         ` Jean Pihet
2009-06-08 14:59                           ` Kevin Hilman
2009-06-08 17:08                             ` Jean Pihet
2009-06-08 17:23                               ` [RFC][PATCH] OMAP3: add support for 2 SDRAM chip selects Kevin Hilman
2009-06-09  8:14                                 ` Tero.Kristo
2009-06-09  8:23                                   ` Jean Pihet
2009-06-09  8:29                                     ` Tero.Kristo
2009-06-09  7:26                           ` [RFC][PATCH] OMAP3: add support for 2 SDRAM chip selects (was: Re: Beagleboard rev C memory timings & suspend/resume) Paul Walmsley
2009-06-05 19:14                       ` Paul Walmsley
2009-06-06 10:50                         ` Grazvydas Ignotas
2009-06-08  9:02                           ` Jean Pihet
2009-06-08 11:01                             ` Grazvydas Ignotas
2009-06-08 17:11                               ` Jean Pihet
2009-06-08 17:28                                 ` [RFC][PATCH] OMAP3: add support for 2 SDRAM chip selects Kevin Hilman
2009-05-07 19:18     ` Beagleboard rev C memory timings & suspend/resume Paul Walmsley
2009-05-08  8:13       ` Jean Pihet [this message]
2009-05-08 22:51         ` Paul Walmsley

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=200905081013.02445.jpihet@mvista.com \
    --to=jpihet@mvista.com \
    --cc=jdk@ti.com \
    --cc=khasim@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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