public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] ddr cfg: DRAM_RESET needs 0x00020030
Date: Sat, 20 Jul 2013 18:01:56 +0200	[thread overview]
Message-ID: <51EAB474.9070007@denx.de> (raw)
In-Reply-To: <20130719215049.GO18359@bill-the-cat>

Hi Tom,

Am 19/07/2013 23:50, schrieb Tom Rini:
> On Fri, Jul 19, 2013 at 02:34:55PM -0700, Troy Kisky wrote:

>> On 7/19/2013 2:00 PM, Fabio Estevam wrote:
>>> Hi Troy,
>>>
>>> On Wed, Jul 17, 2013 at 4:46 PM, Troy Kisky
>>> <troy.kisky@boundarydevices.com> wrote:
>>>> The old value of 0x000e0030 will cause ethernet
>>>> timeout issues on the sabrelite and possibly other
>>>> boards using the KSZ9021.
>>>> I have no explanation as to why.
>>>>
>>>> But this is a correct change, the TRM will be updated
>>>> to show that 00b is the only valid setting for bits
>>>> 19-18 of DRAM_RESET.
>>>>
>>>> My thanks go to Liu Hui(Jason) for this information.
>>>>
>>>> Signed-off-by: Troy Kisky <troy.kisky@boundarydevices.com>
>>> Should this go into 2013.07?
>>>
>>
>> If not too late. It only affect Nitrogen6x, at least until Sabrelite
>> is combined with it.
>> And Sabrelite is already using this value.
> 
> Whose acks should I wait for on this?

Acked-by: Stefano Babic <sbabic@denx.de>

  parent reply	other threads:[~2013-07-20 16:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17 19:46 [U-Boot] [PATCH 1/1] ddr cfg: DRAM_RESET needs 0x00020030 Troy Kisky
2013-07-19 21:00 ` Fabio Estevam
2013-07-19 21:34   ` Troy Kisky
2013-07-19 21:50     ` Tom Rini
2013-07-19 22:04       ` Fabio Estevam
2013-07-20 16:01       ` Stefano Babic [this message]
2013-07-20 16:14         ` Tom Rini
2013-07-19 21:54 ` Fabio Estevam
2013-07-22  6:27 ` Dirk Behme

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=51EAB474.9070007@denx.de \
    --to=sbabic@denx.de \
    --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