From: Teresa Gamez <T.Gamez@phytec.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM pcm043: New RAM timings
Date: Mon, 22 Aug 2011 15:49:44 +0200 [thread overview]
Message-ID: <1314020984.5975.8.camel@lws-gamez> (raw)
In-Reply-To: <20110728134345.GX20587@pengutronix.de>
Hello Sascha,
Am Donnerstag, den 28.07.2011, 15:43 +0200 schrieb Sascha Hauer:
> Hi Teresa,
>
> On Thu, Jul 28, 2011 at 03:14:13PM +0200, Teresa Gámez wrote:
> > Update RAM timings with extended row cycle delay.
> >
> > Signed-off-by: Teresa Gámez <t.gamez@phytec.de>
> > ---
> > arch/arm/boards/pcm043/lowlevel.c | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/arch/arm/boards/pcm043/lowlevel.c b/arch/arm/boards/pcm043/lowlevel.c
> > index eff96f9..bbe586b 100644
> > --- a/arch/arm/boards/pcm043/lowlevel.c
> > +++ b/arch/arm/boards/pcm043/lowlevel.c
> > @@ -146,7 +146,7 @@ void __bare_init __naked board_init_lowlevel(void)
> > writel(0x00000304, ESDMISC); /* was 0x00000004 */
> >
> > /* set timing paramters */
> > - writel(0x00255417, ESDCFG0);
> > + writel(0x0025541F, ESDCFG0);
>
> Does this work on all boards or is this an update for newer sdrams?
Sorry for my late answer. The timings are an update for newer sdrams.
But the timings where successfully tested with older sdrams.
I'll resend the patch with a new description.
Teresa
>
> Sascha
>
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2011-08-22 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 13:14 Teresa Gámez
2011-07-28 13:14 ` [PATCH 2/2] ARM pcm043: Use PDR0 to change cpu freq Teresa Gámez
2011-07-28 14:11 ` Marc Kleine-Budde
2011-07-28 13:43 ` [PATCH 1/2] ARM pcm043: New RAM timings Sascha Hauer
2011-08-22 13:49 ` Teresa Gamez [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=1314020984.5975.8.camel@lws-gamez \
--to=t.gamez@phytec.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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