public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [[PATCH v2]pandaboard: 1/1] Modification of Elpida DDR2 RAM for Pandaboard-ES Rev B3
Date: Thu, 14 Nov 2013 11:32:51 -0500	[thread overview]
Message-ID: <5284FB33.6090005@ti.com> (raw)
In-Reply-To: <CAOf5uwktJGLM9rjvW+SjoWnbXzvqzKeKCZc1Ww5HTyvROQZ0qA@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/14/2013 11:28 AM, Michael Trimarchi wrote:
> Hi
> 
> On Thu, Nov 14, 2013 at 5:19 PM, Tom Rini <trini@ti.com> wrote:
> On 11/14/2013 05:06 AM, Hardik wrote:
>>>> From: Hardik Patel <hardik.patel@volansystech.com>
>>>>
>>>> Signed-off-by: Hardik Patel <hardik.patel@volansystech.com>
>>>> ---
>>>>  arch/arm/cpu/armv7/omap4/sdram_elpida.c |    2 +-
>>>>  board/ti/panda/panda.c                  |   24 ++++++++++++++++++++++++
>>>>  2 files changed, 25 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/arch/arm/cpu/armv7/omap4/sdram_elpida.c b/arch/arm/cpu/armv7/omap4/sdram_elpida.c
>>>> index e4c8316..9fbdeea 100644
>>>> --- a/arch/arm/cpu/armv7/omap4/sdram_elpida.c
>>>> +++ b/arch/arm/cpu/armv7/omap4/sdram_elpida.c
>>>> @@ -123,7 +123,7 @@ static void emif_get_reg_dump_sdp(u32 emif_nr, const struct emif_regs **regs)
>>>>               *regs = &emif_regs_elpida_200_mhz_2cs;
>>>>       else if (omap4_rev == OMAP4430_ES2_3)
>>>>               *regs = &emif_regs_elpida_400_mhz_1cs;
>>>> -     else if (omap4_rev < OMAP4470_ES1_0)
>>>> +     else if (omap4_rev < OMAP4470_ES1_0 && !is_panda_es_rev_b3())
>>>>               *regs = &emif_regs_elpida_400_mhz_2cs;
>>>>       else
>>>>               *regs = &emif_regs_elpida_400_mhz_1cs;
>>>> diff --git a/board/ti/panda/panda.c b/board/ti/panda/panda.c
>>>> index c104024..5a7f80a 100644
>>>> --- a/board/ti/panda/panda.c
>>>> +++ b/board/ti/panda/panda.c
>>>> @@ -122,6 +122,30 @@ int get_board_revision(void)
>>>>       return board_id;
>>>>  }
>>>>
>>>> +/*
>>>> +* Routine: is_panda_es_rev_b3
>>>> +* Description: Detect if we are running on B3 version of ES panda board,
>>>> +*              This can be done by reading the level of GPIO 171
>>>> +*              and checking the processor revisions.
>>>> +*              GPIO171: 1 => Panda ES Rev B3
>>>> +*/
>>>> +u8 is_panda_es_rev_b3(void)
>>>> +{
>>>> +        int processor_rev = omap_revision();
>>>> +        int ret = 0;
>>>> +
>>>> +        if ((processor_rev >= OMAP4460_ES1_0 &&
>>>> +             processor_rev <= OMAP4460_ES1_1)) {
>>>> +
>>>> +                /* Setup the mux for the common board ID pins (gpio 171) */
>>>> +                writew((IEN | M3), (*ctrl)->control_padconf_core_base + UNIPRO_TX0);
>>>> +
>>>> +                /* if processor_rev is panda ES and GPIO171 is 1, it is rev b3 */
>>>> +                ret = gpio_get_value(PANDA_BOARD_ID_2_GPIO);
>>>> +        }
>>>> +        return ret;
>>>> +}
>>>> +
>>>>  /**
>>>>   * @brief misc_init_r - Configure Panda board specific configurations
>>>>   * such as power configurations, ethernet initialization as phase2 of
> 
> This isn't right.  What I was saying is that board/ti/panda/panda.c
> needs to provide its own emif_get_reg_dump function, which will (as
> designed) override the current one from
> arch/arm/cpu/armv7/omap4/sdram_elpida.c
> 
> 
>> Any problem to have visibility of emif_regs array of lpddr?

Things that need exposing so that we can do what was intended before
should be exposed, in <asm/arch-omap4/sys_proto.h> I think.

- -- 
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJShPszAAoJENk4IS6UOR1W2TMP/RzK77vL75h5HYP23RKP/CWx
i7A/xbStKYT8ozh2s1IyHsKohVmnFmIh6lIa4cTYMzrqQBIJxnw9NB1p73qRFPFS
M8Bwx0QS3IU9Wqybk2w1x26Ymm65NWcAQ9SvPh4EBCpdnu1JnJoaceekw1fp55Pb
B+H/44Xr5D57F4R0DAuLqT2Kc6uoMf69X6I/DU7CuxhcceoMAMaFrZq+WrLAqIeY
M5qsCTsyOIQdzV4pheR9gH7F6dbzlA9uee2lshIP0yN5JJmWkZc1CjMR0SsStSpy
RKFJuNOgv32v7CGwvyA/HAk6KdKy5VSWUhHT/+1B3fMzIZhxypOlL90Vbz2Zlh5N
J5E5RNWsQaBJnVaEpo/4wWOTWmq/L5+lQLyJVPUkZFGocHgRBT8gqkcREe/+mSKx
DaxX4mLNlCvooMrNSakPPZHtPHXnVieMAvhdKDDdhLRKHAST+1hZD/ztBD63bwcJ
eSvGBe6SDv/K/mScU9eeNtJzVYs6O1VZm9sqgJBPhgUTN/Mfv7NbZVF3m4rMpkeB
PbQ/eSzxERBxeiInrPh2Ns62oDxCXTodOw5qy+jUQ72WPI/3zMNRHaBbyXTNn9nZ
NAj4XSex3tiQUpJYw21wbshEuCz4/Lo5LBWXeksdg0bfSxWX9jG/mpkOE6NACSyE
7TeL/tTeum0zVByyfhjG
=ZmUi
-----END PGP SIGNATURE-----

  reply	other threads:[~2013-11-14 16:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-25 15:42 [U-Boot] [[PATCH]pandaboard: 0/1] Modification of Elpida DDR2 RAM for Pandaboard-ES Rev B3 Hardik
2013-10-25 15:42 ` [U-Boot] [[PATCH]pandaboard: 1/1] " Hardik
2013-10-28 12:51   ` Dan Murphy
2013-10-28 13:04     ` Tom Rini
2013-10-29 14:17       ` Hardik Patel
2013-10-29 15:54         ` Tom Rini
2013-11-14 10:05           ` [U-Boot] [[PATCH v2]pandaboard: 0/1] " Hardik
2013-11-14 10:06           ` Hardik
2013-11-14 10:06           ` [U-Boot] [[PATCH v2]pandaboard: 1/1] " Hardik
2013-11-14 15:29             ` Robert Nelson
2013-11-14 15:41             ` Michael Trimarchi
2013-11-14 16:19             ` Tom Rini
2013-11-14 16:28               ` Michael Trimarchi
2013-11-14 16:32                 ` Tom Rini [this message]
2013-11-14 18:43                   ` Hardik Patel
2013-11-14 18:58                     ` Michael Trimarchi
2013-11-14 19:02                     ` Tom Rini
2013-11-14 19:41             ` Nishanth Menon
2013-11-14 19:49               ` Tom Rini
2013-11-14 20:26               ` Nishanth Menon
2013-11-21  9:17                 ` jmgrimaud
2013-11-27 15:46                 ` [U-Boot] [[PATCH v3]pandaboard: 0/1] ARM:OMAP4+: panda-es: Support Rev B3 Elpida DDR2 RAM Hardik
2013-11-27 15:46                 ` [U-Boot] [[PATCH v3]pandaboard: 1/1] " Hardik
2013-12-04 22:05                   ` [U-Boot] [U-Boot, [PATCH, v3] pandaboard: " 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=5284FB33.6090005@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