From: Giorgio Dal Molin <giorgio.nicole@arcor.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: problems with am335x_sdram_size()
Date: Fri, 2 Mar 2018 15:11:06 +0100 (CET) [thread overview]
Message-ID: <272060361.5564.1519999866645@mail.vodafone.de> (raw)
In-Reply-To: <20180302072606.nn5o4mj7zbe4pyna@pengutronix.de>
Hi,
> On March 2, 2018 at 8:26 AM Sascha Hauer <s.hauer@pengutronix.de> wrote:
>
>
> On Thu, Mar 01, 2018 at 03:23:33PM +0100, Giorgio Dal Molin wrote:
> > Hi,
> >
> > working with the TI AM335x Evaluation Module I noticed that the function
> > am335x_sdram_size() always returns 0 instead of the computed sdram size.
> >
> > I could trace back the problem to the fact that the function does its
> > computation based on the value of the register CM_EMIF_SDRAM_CONFIG
> > (addr. 0x44e10110), but this register is not written to by the function
> > am33xx_config_sdram() and just returns its initial value (0).
> > The datasheet says CM_EMIF_SDRAM_CONFIG should have the same value as
> > AM33XX_EMIF4_0_REG(SDRAM_CONFIG) (addr. 0x4c000008)
>
> CM_EMIF_SDRAM_CONFIG is written when regs->zq_config is set and if it's
> set then indeed the same value is written there as also written to
> AM33XX_EMIF4_0_REG(SDRAM_CONFIG).
>
aaah, I'm blind !
I've added a line at the end of am33xx_config_sdram() that's
exactly the same as the one a couple of lines before.
I was so happy to have solved my problem that I've no more
double checked if the register was already configured somewhere else.
So, now I've also defined regs->zq_config in my lowlevel.c and everything works.
The datasheet says:
The CONTROL_EMIF_SDRAM_CONFIG register exports SDRAM configuration information
to the EMIF after resuming from low power scenarios.
This register should be loaded with the same value as SDRAM_CONFIG during DDR
initialization.
so I think we should initialize it unconditionally, not only if !regs->zq_config.
Doing this it should be the same which one we use in am335x_sdram_size() to
compute the sdram size even if I would prefer to use AM33XX_EMIF4_0_REG(SDRAM_CONFIG)
for clarity.
giorgio
> >
> > To conclude, to fix the problem with am335x_sdram_size() you can either
> > use AM33XX_EMIF4_0_REG(SDRAM_CONFIG) instead of CM_EMIF_SDRAM_CONFIG
> > in am335x_sdram_size().
> >
> > or
> >
> > initialize CM_EMIF_SDRAM_CONFIG in am33xx_config_sdram() with the same value
> > as AM33XX_EMIF4_0_REG(SDRAM_CONFIG) (regs->sdram_config)
>
> I'm fine with either way. Maybe the datasheet gives us a hint which way
> to choose? Why is CM_EMIF_SDRAM_CONFIG only written when regs->zq_config
> is set? Is this correct?
>
> Sascha
>
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2018-03-02 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 14:23 Giorgio Dal Molin
2018-03-02 7:26 ` Sascha Hauer
2018-03-02 14:11 ` Giorgio Dal Molin [this message]
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=272060361.5564.1519999866645@mail.vodafone.de \
--to=giorgio.nicole@arcor.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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