From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/7] OMAP5: EMIF: Add support for DDR3 device
Date: Tue, 22 May 2012 08:39:30 -0700 [thread overview]
Message-ID: <4FBBB332.2040409@ti.com> (raw)
In-Reply-To: <CAJ7qFScyB0T2AOsZtiWSaS6H3RLs5ThKEk=HSZoEJqpLdT2Eiw@mail.gmail.com>
On 05/22/2012 08:27 AM, R, Sricharan wrote:
>>>>> - ? ? if (!in_sdram)
>>>>> - ? ? ? ? ? ? lpddr2_init(base, regs);
>>>>> + ? ? if (!in_sdram) {
>>>>> + ? ? ? ? ? ? if (omap_revision() != OMAP5432_ES1_0)
>>>>> + ? ? ? ? ? ? ? ? ? ? lpddr2_init(base, regs);
>>>>> + ? ? ? ? ? ? else
>>>>> + ? ? ? ? ? ? ? ? ? ? ddr3_init(base, regs);
>>>>> + ? ? }
>>>>
>>>> In omap4+ land do we have any other way of telling which family we're
>>>> on? ?I ask since I'm preparing to add DDR3 support to am33xx and I'd
>>>> like to switch it over to the common emif framework as well.
>>>>
>>> I think the SDRAM_TYPE[31:29] EMIF_SDRAM_CONFIG
>>> register should tell the connected device at reset.
>>> I will cross confirm this on the board and tell.
>>
>> OK. I can't find the omap5430 TRM quickly but on the am335x one,
>> SDRAM_TYPE is 3 for DDR3, 2 for DDR2 and 1 for LPDDR1 and 0 for DDR1.
>
> ah, this is what is there on OMAP5.
> 3 for DDR3
> 4 for LPDDR2-S4,
> 5 for LPDDR2-S2
4/5 are listed as reserved here :( http://www.ti.com/lit/pdf/spruh73
> Atleast DDR3 encoding is same. So we can differentiate bw DDR3 and 2
> in same way.
> Is the reset value set correctly on am335x according to the device connected?
I'll have to do some checking as the code doesn't check that today.
--
Tom
next prev parent reply other threads:[~2012-05-22 15:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 10:03 [U-Boot] [PATCH 0/7] OMAP5: Add support for OMAP5432 SOC Lokesh Vutla
2012-05-22 10:03 ` [U-Boot] [PATCH 1/7] OMAP5: Adding correct Control id code for OMAP5430 Lokesh Vutla
2012-05-22 10:24 ` R, Sricharan
2012-05-22 10:03 ` [U-Boot] [PATCH 2/7] OMAP5: ADD chip detection for OMAP5432 SOC Lokesh Vutla
2012-05-22 10:03 ` [U-Boot] [PATCH 3/7] OMAP5: Configure the io settings for omap5432 uevm board Lokesh Vutla
2012-05-22 10:03 ` [U-Boot] [PATCH 4/7] OMAP5: ADD precalculated timings for ddr3 Lokesh Vutla
2012-05-22 10:31 ` R, Sricharan
2012-05-22 10:03 ` [U-Boot] [PATCH 5/7] OMAP5: EMIF: Add support for DDR3 device Lokesh Vutla
2012-05-22 14:41 ` Tom Rini
2012-05-22 14:58 ` R, Sricharan
2012-05-22 15:18 ` Tom Rini
2012-05-22 15:27 ` R, Sricharan
2012-05-22 15:39 ` Tom Rini [this message]
2012-05-23 12:22 ` R, Sricharan
2012-05-23 16:55 ` Tom Rini
2012-05-24 6:45 ` R, Sricharan
2012-05-24 13:46 ` Tom Rini
2012-05-22 10:03 ` [U-Boot] [PATCH 6/7] OMAP5: DPLL core lock for OMAP5432 Lokesh Vutla
2012-05-22 10:36 ` R, Sricharan
2012-05-22 10:03 ` [U-Boot] [PATCH 7/7] OMAP5: Change voltages for omap5432 Lokesh Vutla
2012-05-25 15:04 ` [U-Boot] [PATCH 0/7] OMAP5: Add support for OMAP5432 SOC 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=4FBBB332.2040409@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.