public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher denx <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm, am33xx: update for siemens am335x based boards
Date: Tue, 16 Jun 2015 14:51:18 +0200	[thread overview]
Message-ID: <55801BC6.8050006@denx.de> (raw)
In-Reply-To: <27E9275BC1C8554E840881B19B62BE421996AF@DENBGAT9EI1MSX.ww902.siemens.net>

Hello Samuel,

Am 16.06.2015 um 14:08 schrieb Egli, Samuel:
> Hi Heiko,
>
> I noticed a little discrepancy concerning delay for DDR3. During
> last rebase to v2015.04 I observed that delay needs to be
> increased to boot successfully. Somehow some timing behavior
> changed since v2014.04.
>
> I set it to udelay(2000) and it works fine again. Please
> update your patch.

Ups... Ok, I send an updated v2 patch.
Thanks!

bye,
Heiko
>
> Sam
>
>
>> -----Original Message-----
>> From: Heiko Schocher [mailto:hs at denx.de]
>> Sent: Montag, 15. Juni 2015 14:55
>> To: u-boot at lists.denx.de
>> Cc: Heiko Schocher; Egli, Samuel; Tom Rini
>> Subject: [PATCH] arm, am33xx: update for siemens am335x based boards
>> [...]
>> @@ -193,6 +196,11 @@ struct ctrl_ioregs draco_ddr3_ioregs = {
>>
>> 	config_ddr(DDR_PLL_FREQ, &draco_ddr3_ioregs, &draco_ddr3_data,
>> 		   &draco_ddr3_cmd_ctrl_data, &draco_ddr3_emif_reg_data, 0);
>> +
>> +	/* For Samsung 2Gbit RAM we need this delay otherwise config fails
>> after
>> +	 * soft reset.
>> +	 */
>> +	udelay(1000);
>> }
>> [...]
>

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

      reply	other threads:[~2015-06-16 12:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 12:54 [U-Boot] [PATCH] arm, am33xx: update for siemens am335x based boards Heiko Schocher
2015-06-15 15:18 ` Tom Rini
2015-06-16 12:08 ` Egli, Samuel
2015-06-16 12:51   ` Heiko Schocher denx [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=55801BC6.8050006@denx.de \
    --to=hs@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