From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/7] ARM: OMAP4+: emif: Detect SDRAM from SDRAM config register
Date: Thu, 31 Jan 2013 11:29:58 -0500 [thread overview]
Message-ID: <510A9C06.6030102@ti.com> (raw)
In-Reply-To: <1359611525-19017-2-git-send-email-r.sricharan@ti.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/31/2013 12:51 AM, R Sricharan wrote:
> From: Lokesh Vutla <lokeshvutla@ti.com>
>
> Now SDRAM initialization is done on the basis of omap revision.
> Instead this should be done on basis of SDRAM type read from
> EMIF_SDRAM_CONFIG register. This will be helpful to avoid
> unnessecary cpu checks for new boards
>
> Signed-off-by: R Sricharan <r.sricharan@ti.com> Signed-off-by:
> Lokesh Vutla <lokeshvutla@ti.com>
Does this mean the ROM is already doing some basic EMIF programming
here? I swear I looked down this path before, when I wanted to share
this code with am33xx and the problem is that while the registers
aren't reset on warm boot, on cold boot they always come up in a
default value, for both DDR2 and DDR3.
Or are you able to get by as the platforms come up with different
default values?
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRCpwGAAoJENk4IS6UOR1WpawP/jJE1GjmUCSDyC5yFyF2nRc2
gMxvIOni2Dl/y8EbvQyRMkJunzjHLxHmUqQLXLsauAalyx2xnBQ3WRhYNFR7G5jX
vOlvsn4h5L2FdQL97/5pnsKNxdgXACw2HSidIFDGQ5/o9e53Tn3ZU7BN8bYaNEep
AS7vF/ewOIbPlcavf4ov7DoICLpp8RMGPOQ+7yHAsEWfPnH3ZlfLNcUjxKzNTVpU
PGeNbka50rliEaSTbNFklpy3E09O3kNvskk6TdGnRPL6/+CR2Z9jAqeVOSGnZYTr
fagd9hlBB5HTfdBm8l2f2RRAce+t0lbvxl5wjqo+Wo+HZkf+c3/QBNe8jeDRblF5
OOixfQGq92LuqpF+HWlwnmV7R5TyF9CbuHRuDLGMux7h3YT4dsLuvUasRIAhKyUp
NyMgdw5Ytn39kE5CT3jjYbqhiYk6O1Wo1GO6xoP2N7Zn4SqK7tkX62YDPkBw8B/v
3yI5TMmuy/tTqSUsP3xevk6yf8uPFDZwNX1yIbWBmm3acX8kShIAZsXWPC42V3Pc
h3RbgBpTAU7XE9kFOSK5epk6OlipjiEdlo9Auh35yZ976bwmQsfdT5eFzLSsBO+g
f9c9KZPgg/oC82vMPOZ479a4DqapuLCdR3wTtgxaycvhqLDVSxoKbgZSyE6RAuSt
bXLDlFS0Lx4jqAuCWnE4
=l/qE
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-01-31 16:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 5:51 [U-Boot] [PATCH 0/7] ARM: OMAP4+: Cleanup clocks, control and emif code R Sricharan
2013-01-31 5:51 ` [U-Boot] [PATCH 1/7] ARM: OMAP4+: emif: Detect SDRAM from SDRAM config register R Sricharan
2013-01-31 16:29 ` Tom Rini [this message]
2013-02-01 6:30 ` R Sricharan
2013-02-01 14:37 ` Tom Rini
2013-01-31 5:52 ` [U-Boot] [PATCH 2/7] ARM: OMAP4+: Change the PRCM structure prototype common for all Socs R Sricharan
2013-01-31 16:40 ` Tom Rini
2013-02-01 6:47 ` R Sricharan
2013-01-31 5:52 ` [U-Boot] [PATCH 3/7] ARM: OMAP4+: Cleanup the clocks layer R Sricharan
2013-01-31 16:42 ` Tom Rini
2013-01-31 5:52 ` [U-Boot] [PATCH 4/7] ARM: OMAP4+: Clean up the pmic code R Sricharan
2013-01-31 17:01 ` Tom Rini
2013-02-01 6:49 ` R Sricharan
2013-01-31 5:52 ` [U-Boot] [PATCH 5/7] ARM: OMAP4+: Cleanup emif specific files R Sricharan
2013-01-31 17:03 ` Tom Rini
2013-01-31 5:52 ` [U-Boot] [PATCH 6/7] ARM: OMAP4+: Make control module register structure generic R Sricharan
2013-01-31 17:05 ` Tom Rini
2013-01-31 5:52 ` [U-Boot] [PATCH 7/7] ARM: OMAP5: Clean up iosettings code R Sricharan
2013-01-31 17:06 ` Tom Rini
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=510A9C06.6030102@ti.com \
--to=trini@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