public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Chin Liang See <clsee@altera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/9] arm: socfpga: Adding handoff for SDRAM ctrlcfg.extratime1
Date: Tue, 20 Sep 2016 17:13:46 +0800	[thread overview]
Message-ID: <1474362826.2220.1.camel@altera.com> (raw)
In-Reply-To: <806f7ce3-41b2-b96d-8f35-9b6f613870c8@denx.de>

On Tue, 2016-09-20 at 09:52 +0200, Marek Vasut wrote:
> On 09/20/2016 07:37 AM, Chin Liang See wrote:
> > On Mon, 2016-09-19 at 20:52 +0200, Marek Vasut wrote:
> > > On 09/19/2016 12:12 PM, Chin Liang See wrote:
> > > > On Mon, 2016-09-19 at 16:24 +0200, Marek Vasut wrote:
> > > > > On 09/15/2016 09:27 AM, Chin Liang See wrote:
> > > > > > Adding new handoff for SDRAM ctrcfg.extratime1 which is
> > > > > > required for stabil LPDDR2 operation
> > > > > 
> > > > > ... stable ...
> > > > > 
> > > > > Isn't SoCDK using DDR3 DRAM ?
> > > > 
> > > > Yah, you are right where we won't need this patch and others
> > > > except
> > > > #1
> > > > one. Should I send v2 which only have first patch?
> > > 
> > > Then should this register be set to zero on SoCDK ?
> > 
> > Not required as the default value is zero.
> 
> OK, if we can avoid the ifdef(s)
> 

Removing the ifdef would requiring the patch against all socfpga
boards. As commented by you earlier, all our boards are using DDR3 and
this patch for LPDDR2 would not applicable then.

Thanks
Chin Liang

  reply	other threads:[~2016-09-20  9:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15  7:27 [U-Boot] [PATCH 2/9] arm: socfpga: Adding handoff for SDRAM ctrlcfg.extratime1 Chin Liang See
2016-09-19 14:24 ` Marek Vasut
2016-09-19 10:12   ` Chin Liang See
2016-09-19 18:52     ` Marek Vasut
2016-09-20  5:37       ` Chin Liang See
2016-09-20  7:52         ` Marek Vasut
2016-09-20  9:13           ` Chin Liang See [this message]
2016-09-21  1:19             ` Marek Vasut

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=1474362826.2220.1.camel@altera.com \
    --to=clsee@altera.com \
    --cc=u-boot@lists.denx.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