public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lokesh Vutla <lokeshvutla@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 13/14] ARM: AM43xx: GP_EVM: Add support for DDR3
Date: Wed, 13 Nov 2013 14:18:15 +0530	[thread overview]
Message-ID: <52833CCF.2060709@ti.com> (raw)
In-Reply-To: <527A4A0D.7040309@ti.com>

Hi Vaibhav,
On Wednesday 06 November 2013 07:24 PM, Lokesh Vutla wrote:
> On Wednesday 06 November 2013 06:32 PM, Vaibhav Bedia wrote:
>> On Mon, Nov 4, 2013 at 11:20 PM, Lokesh Vutla <lokeshvutla@ti.com> wrote:
>>> GP EVM has 1GB DDR3 attached(Part no: MT47H128M16RT-187E:C).
>>> Adding details for the same.
>>> Below is the brief description of DDR3 init sequence(SW leveling):
>>> -> Enable VTT regulator
>>> -> Configure VTP
>>> -> Configure DDR IO settings
>>> -> Disable initialization and refreshes until EMIF registers are programmed.
>>> -> Program Timing registers
>>> -> Program leveling registers
>>> -> Program PHY control and Temp alert and ZQ config registers.
>>
>> Temp alert? Is that really relevant here?
> Yes, Need to configure all the emif registers before accessing SDRAM.
>>
>>> -> Enable initialization and refreshes and configure SDRAM CONFIG register
>>>
>>> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
>>> ---
>>>  arch/arm/cpu/armv7/am33xx/emif4d5.c         |    8 ++-
>>>  arch/arm/include/asm/arch-am33xx/ddr_defs.h |   10 ++-
>>>  board/ti/am43xx/board.c                     |   89 ++++++++++++++++++++++++++-
>>>  3 files changed, 101 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/arch/arm/cpu/armv7/am33xx/emif4d5.c b/arch/arm/cpu/armv7/am33xx/emif4d5.c
>>> index eea1fa3..8bac0f2 100644
>>> --- a/arch/arm/cpu/armv7/am33xx/emif4d5.c
>>> +++ b/arch/arm/cpu/armv7/am33xx/emif4d5.c
>>> @@ -120,7 +120,7 @@ static void configure_mr(u32 base, u32 cs)
>>>
>>>  void do_sdram_init(const struct ctrl_ioregs *ioregs,
>>>                    const struct emif_regs *regs,
>>> -                  const u32 *ext_phy_ctrl_const_regs)
>>> +                  const u32 *ext_phy_ctrl_const_regs, u32 sdram_type)
>>>  {
>>>         struct emif_reg_struct *emif = (struct emif_reg_struct *)EMIF1_BASE;
>>>
>>> @@ -178,6 +178,8 @@ void do_sdram_init(const struct ctrl_ioregs *ioregs,
>>>         writel(regs->sdram_config, &emif->emif_sdram_config);
>>>         writel(regs->ref_ctrl, &emif->emif_sdram_ref_ctrl);
>>>
>>> -       configure_mr(EMIF1_BASE, 0);
>>> -       configure_mr(EMIF1_BASE, 1);
>>> +       if (sdram_type == EMIF_SDRAM_TYPE_LPDDR2) {
>>> +               configure_mr(EMIF1_BASE, 0);
>>> +               configure_mr(EMIF1_BASE, 1);
>>> +       }
>>>  }
>>> diff --git a/arch/arm/include/asm/arch-am33xx/ddr_defs.h b/arch/arm/include/asm/arch-am33xx/ddr_defs.h
>>> index 1880415..796e9df 100644
>>> --- a/arch/arm/include/asm/arch-am33xx/ddr_defs.h
>>> +++ b/arch/arm/include/asm/arch-am33xx/ddr_defs.h
>>> @@ -134,6 +134,14 @@
>>>  #define  LPDDR2_DATA2_IOCTRL_VALUE   0x20000294
>>>  #define  LPDDR2_DATA3_IOCTRL_VALUE   0x20000294
>>>
>>> +#define  DDR3_ADDRCTRL_WD0_IOCTRL_VALUE 0x00000000
>>> +#define  DDR3_ADDRCTRL_WD1_IOCTRL_VALUE 0x00000000
>>> +#define  DDR3_ADDRCTRL_IOCTRL_VALUE   0x84
>>> +#define  DDR3_DATA0_IOCTRL_VALUE   0x84
>>> +#define  DDR3_DATA1_IOCTRL_VALUE   0x84
>>> +#define  DDR3_DATA2_IOCTRL_VALUE   0x84
>>> +#define  DDR3_DATA3_IOCTRL_VALUE   0x84
>>> +
>>>  /**
>>>   * Configure DMM
>>>   */
>>> @@ -333,5 +341,5 @@ void config_ddr(unsigned int pll, unsigned int ioctrl,
>>>
>>>  void do_sdram_init(const struct ctrl_ioregs *ioregs,
>>>                    const struct emif_regs *emif_regs,
>>> -                  const u32 *ext_phy_ctrl_const_regs);
>>> +                  const u32 *ext_phy_ctrl_const_regs, u32 ddr_type);
>>>  #endif  /* _DDR_DEFS_H */
>>> diff --git a/board/ti/am43xx/board.c b/board/ti/am43xx/board.c
>>> index 83d184d..a943b45 100644
>>> --- a/board/ti/am43xx/board.c
>>> +++ b/board/ti/am43xx/board.c
>>> @@ -140,6 +140,57 @@ const u32 ext_phy_ctrl_const_base_lpddr2[EMIF_EXT_PHY_CTRL_CONST_REG] = {
>>>         0x08102040
>>>  };
>>>
>>> +const struct ctrl_ioregs ioregs_ddr3 = {
>>> +       .cm0ioctl               = DDR3_ADDRCTRL_IOCTRL_VALUE,
>>> +       .cm1ioctl               = DDR3_ADDRCTRL_WD0_IOCTRL_VALUE,
>>> +       .cm2ioctl               = DDR3_ADDRCTRL_WD1_IOCTRL_VALUE,
>>> +       .dt0ioctl               = DDR3_DATA0_IOCTRL_VALUE,
>>> +       .dt1ioctl               = DDR3_DATA0_IOCTRL_VALUE,
>>> +       .dt2ioctrl              = DDR3_DATA0_IOCTRL_VALUE,
>>> +       .dt3ioctrl              = DDR3_DATA0_IOCTRL_VALUE,
>>> +       .emif_sdram_config_ext  = 0x0043,
>>> +};
>>> +
>>> +const struct emif_regs ddr3_emif_regs_400Mhz = {
>>> +       .sdram_config                   = 0x638413B2,
>>> +       .ref_ctrl                       = 0x00000C30,
>>> +       .sdram_tim1                     = 0xEAAAD4DB,
>>> +       .sdram_tim2                     = 0x266B7FDA,
>>> +       .sdram_tim3                     = 0x107F8678,
>>> +       .read_idle_ctrl                 = 0x00050000,
>>> +       .zq_config                      = 0x50074BE4,
>>> +       .temp_alert_config              = 0x0,
>>> +       .emif_ddr_phy_ctlr_1            = 0x0E084007,
>>> +       .emif_ddr_ext_phy_ctrl_1        = 0x08020080,
>>> +       .emif_ddr_ext_phy_ctrl_2        = 0x00400040,
>>> +       .emif_ddr_ext_phy_ctrl_3        = 0x00400040,
>>> +       .emif_ddr_ext_phy_ctrl_4        = 0x00400040,
>>> +       .emif_ddr_ext_phy_ctrl_5        = 0x00400040
>>> +};
>>> +
>>> +const u32 ext_phy_ctrl_const_base_ddr3[EMIF_EXT_PHY_CTRL_CONST_REG] = {
>>> +       0x00400040,
>>> +       0x00350035,
>>> +       0x00350035,
>>> +       0x00350035,
>>> +       0x00350035,
>>> +       0x00350035,
>>> +       0x00000000,
>>> +       0x00000000,
>>> +       0x00000000,
>>> +       0x00000000,
>>> +       0x00000000,
>>> +       0x00340034,
>>> +       0x00340034,
>>> +       0x00340034,
>>> +       0x00340034,
>>> +       0x00340034,
>>> +       0x0,
>>> +       0x0,
>>> +       0x40000000,
>>> +       0x08102040
>>> +};
>>> +
>>>  const struct dpll_params *get_dpll_ddr_params(void)
>>>  {
>>>         if (board_is_eposevm())
>>> @@ -189,10 +240,44 @@ void set_mux_conf_regs(void)
>>>         enable_board_pin_mux();
>>>  }
>>>
>>> +static void enable_vtt_regulator(void)
>>> +{
>>> +       u32 temp;
>>> +
>>> +       /*GPIO_VTTEN - GPIO0_21 PINMUX Setup*/
>>> +       writel(0x20009, CTRL_BASE + 0x0A60);
>>> +
>>> +       writel(0x40002, PRCM_BASE + 0x2B68);
>>> +
>>> +       /* Poll if module is functional */
>>> +       while ((readl(PRCM_BASE + 0x2B68) & 0x30000) != 0x0)
>>> +               ;
>>> +
>>> +       while ((readl(PRCM_BASE + 0x2B00) & 0x100) != 0x100)
>>> +               ;
>>> +
>>> +       /* enable module */
>>> +       writel(0x0, GPIO0_BASE + 0x0130);
>>> +
>>> +       /*enable output for GPIO0_21*/
>>> +       writel((1 << 22), GPIO0_BASE + 0x0194);
>>> +       temp = readl(GPIO0_BASE + 0x0134);
>>> +       temp = temp & ~(1 << 22);
>>> +       writel(temp, GPIO0_BASE + 0x0134);
>>
>> That's a lot of direct register writes :P
> He he.. Completely missed it. Thanks for pointing it out.
> LL update it..:)
>>
>> Can't you use some proper APIs for doing the pinmux, enabling the modules
>> and controlling the GPIO?
>>
>>> +}
>>> +
>>>  void sdram_init(void)
>>>  {
>>> -       do_sdram_init(&ioregs_lpddr2, &emif_regs_lpddr2,
>>> -                     ext_phy_ctrl_const_base_lpddr2);
>>> +       if (board_is_eposevm()) {
>>> +               do_sdram_init(&ioregs_lpddr2, &emif_regs_lpddr2,
>>> +                             ext_phy_ctrl_const_base_lpddr2,
>>> +                             EMIF_SDRAM_TYPE_LPDDR2);
>>> +       } else {
>>> +               enable_vtt_regulator();
>>
>> Hmm there must a smarter way of finding out whether the VTT regulator
>> is present or not? You can always have DDR3 setups which don't use
>> the regulator. Why not get this added to the EEPROM?
I checked with hardware folks. There is no register or some way to tell
if VTT is present. It is not added in EEPROM also and I have no answer why it
is not added in EEPROM..:(
It is specific to boards using DDR3. So its good to have it in board files as I did it here
instead of adding this check in emif file.

Thanks and regards,
Lokesh
> Hmm.. I am not sure. LL check it and update in V2.
> 
> Thanks and regards,
> Lokesh
>>
>> Regards,
>> Vaibhav
>>
> 

  parent reply	other threads:[~2013-11-13  8:48 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05  4:20 [U-Boot] [PATCH 00/14] ARM: AM43xx: Update support for AM4372 SoC Lokesh Vutla
2013-11-05  4:20 ` [U-Boot] [PATCH 01/14] ARM: AM43xx: Update the base addresses of modules Lokesh Vutla
2013-11-06 12:28   ` Vaibhav Bedia
2013-11-06 13:12     ` Lokesh Vutla
2013-11-05  4:20 ` [U-Boot] [PATCH 02/14] ARM: AM43xx: Adapt to ti_armv7_common.h config file Lokesh Vutla
2013-11-06 12:34   ` Vaibhav Bedia
2013-11-06 13:18     ` Lokesh Vutla
2013-11-05  4:20 ` [U-Boot] [PATCH 03/14] ARM: AM43xx: Add L2 Support Lokesh Vutla
2013-11-05  4:20 ` [U-Boot] [PATCH 04/14] ARM: AM43xx: Add extra ENV settings Lokesh Vutla
2013-11-05  4:20 ` [U-Boot] [PATCH 05/14] ARM: AM43XX: board: add support for reading onboard EEPROM Lokesh Vutla
2013-11-06 12:38   ` Vaibhav Bedia
2013-11-06 13:25     ` Lokesh Vutla
2013-11-06 16:39       ` Vaibhav Bedia
2013-11-06 21:37         ` Tom Rini
2013-11-07 20:56           ` Vaibhav Bedia
2013-11-07 21:06             ` Tom Rini
2013-11-07 21:16               ` Vaibhav Bedia
2013-11-05  4:20 ` [U-Boot] [PATCH 06/14] ARM: AM43XX: Add CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG support Lokesh Vutla
2013-11-05  4:20 ` [U-Boot] [PATCH 07/14] ARM: AM43xx: Select clk source for Timer2 Lokesh Vutla
2013-11-06 12:40   ` Vaibhav Bedia
2013-11-07 13:43     ` Lokesh Vutla
2013-11-07 21:01       ` Vaibhav Bedia
2013-11-08 10:00         ` Lokesh Vutla
2013-11-05  4:20 ` [U-Boot] [PATCH 08/14] ARM: AM43xx: Update Current Booting devices list Lokesh Vutla
2013-11-05  4:20 ` [U-Boot] [PATCH 09/14] ARM: AM43xx: mux: Update mux data Lokesh Vutla
2013-11-06 12:43   ` Vaibhav Bedia
2013-11-06 13:32     ` Lokesh Vutla
2013-11-06 16:41       ` Vaibhav Bedia
2013-11-07  8:27         ` Lokesh Vutla
2013-11-05  4:20 ` [U-Boot] [PATCH 10/14] ARM: AM43xx: clocks: Update DPLL details for EPOS EVM Lokesh Vutla
2013-11-06 12:48   ` Vaibhav Bedia
2013-11-06 13:36     ` Lokesh Vutla
2013-11-05  4:20 ` [U-Boot] [PATCH 11/14] ARM: AM43xx: clocks: Add DPLL data for GP EVM Lokesh Vutla
2013-11-06 12:48   ` Vaibhav Bedia
2013-11-05  4:20 ` [U-Boot] [PATCH 12/14] ARM: AM43xx: EPOS_EVM: Add support for LPDDR2 Lokesh Vutla
2013-11-06 12:57   ` Vaibhav Bedia
2013-11-06 13:45     ` Lokesh Vutla
2013-11-06 16:44       ` Vaibhav Bedia
2013-11-06 21:26         ` Tom Rini
2013-11-05  4:20 ` [U-Boot] [PATCH 13/14] ARM: AM43xx: GP_EVM: Add support for DDR3 Lokesh Vutla
2013-11-06 13:02   ` Vaibhav Bedia
2013-11-06 13:54     ` Lokesh Vutla
2013-11-06 16:47       ` Vaibhav Bedia
2013-11-13  8:48       ` Lokesh Vutla [this message]
2013-11-13 14:08         ` Vaibhav Bedia
2013-11-13 16:08           ` Sekhar Nori
2013-11-13 17:50             ` Vaibhav Bedia
2013-11-14 14:21               ` Tom Rini
2013-11-14 14:18           ` Tom Rini
2013-11-05  4:21 ` [U-Boot] [PATCH 14/14] ARM: AM43xx: Add Maintainer Lokesh Vutla

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=52833CCF.2060709@ti.com \
    --to=lokeshvutla@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