From: Sricharan R <r.sricharan@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: OMAP5: DDR3: Change io settings
Date: Thu, 17 Oct 2013 12:29:53 +0530 [thread overview]
Message-ID: <525F8AE9.8060000@ti.com> (raw)
In-Reply-To: <912A29987EAE174BA6CF187D7CDFA9CE237C1093@DLEE08.ent.ti.com>
Hi Brad,
On Thursday 17 October 2013 08:05 AM, Griffis, Brad wrote:
> First, Sricharan, thanks for putting together these patches and getting them posted so quickly. I approve of the code but wanted to comment on the commit message. Our previous (internal) thread had a hodge podge of issues, so I think there was some confusion there. In particular this comment was not 100% accurate:
>
>> 1) The first change from 0x64656465 to 0x64646464 removes the weak pull
>> on the DQ lines. Otherwise the DQ line was not staying at Vref when IDLE (retreats
>> to ground) and because of this there were extra transitions and noise.
> It removes the weak pullup, yes. However, the DQ line not staying at VREF during IDLE was a different thing altogether and is not affected by this change. That's actually something that is hard-coded as part of the integration of the PHY into the SoC and is not configurable...
>
> This particular pullup affects both DQS and nDQS. We don't want to pull differential signals in the same direction. So, bottom line, disabling that weak pullup will improve the signal integrity. (I think I would leave the commit message at that.)
>
>> 2) The second change was to enable internal VREF_DQ_OUT which otherwise was at 0V.
> The above description is entirely accurate and I would agree is suitable for the commit message. Here's a bit more detail for the archives...
>
> On the uEVM there are 4 DDR3 devices. The VREF for 2 of the devices is powered by the OMAP's VREF_CA_OUT pins. The VREF on the other 2 devices is powered by the OMAP's VREF_DQ_OUT pins. So the net effect here is that only half of the DDR3 devices were being supplied a VREF! This was clearly a mistake. This patch improves the robustness of the interface and was specifically seen to cure corruption observed at high temperatures on some boards.
Thanks for the accurate explanation, i will reword it with your suggestions above.
Regards,
Sricharan
next prev parent reply other threads:[~2013-10-17 6:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 10:10 [U-Boot] [PATCH] ARM: OMAP5: DDR3: Change io settings Sricharan R
2013-10-16 11:34 ` Enric Balletbo Serra
2013-10-16 12:33 ` Tom Rini
2013-10-16 13:23 ` Sricharan R
2013-10-16 13:38 ` Enric Balletbo Serra
[not found] ` <912A29987EAE174BA6CF187D7CDFA9CE237C1093@DLEE08.ent.ti.com>
2013-10-17 6:59 ` Sricharan R [this message]
2013-10-17 9:12 ` Enric Balletbo Serra
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=525F8AE9.8060000@ti.com \
--to=r.sricharan@ti.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