All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] mx6cuboxi: fix 4GB ddr memory detection
Date: Thu, 7 Jun 2018 10:43:03 -0300	[thread overview]
Message-ID: <CAOMZO5BFmnN8s+Z2sHqa5WzdWhcQRsYtDsvDuW_wDAWe1L3bmg@mail.gmail.com> (raw)
In-Reply-To: <b26ecc27cd034d1115670e877705b1652bea3277.1528377457.git.baruch@tkos.co.il>

On Thu, Jun 7, 2018 at 10:17 AM, Baruch Siach <baruch@tkos.co.il> wrote:
> From: Jon Nettleton <jon@solid-run.com>
>
> The soms with 4GB ddr have a rowaddr of 16 not 15, this allows
> the detection mechanism to properly identify them as 4GB.
> However these soms can be populated with whatever amount of
> memory the customer requests therefor we need a ram stride test.
> We can not use the get_ram_size() function because not all 4GB's
> of DDR is addressable on a 32-bit architecture.  Therefore instead
> we use a memory stride of 128MB's and look for the address that
> the memory wraps.  This function is used for all som types to
> catch most memory configurations.
>
> This is a revised version of Rabeeh Khoury's original code.
>
> Signed-off-by: Jon Nettleton <jon@solid-run.com>
> Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>

Reviewed-by: Fabio Estevam <fabio.estevam@nxp.com>

  reply	other threads:[~2018-06-07 13:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-07 13:17 [U-Boot] [PATCH 1/2] mx6cuboxi: consolidate board detection and add som revision checking Baruch Siach
2018-06-07 13:17 ` [U-Boot] [PATCH 2/2] mx6cuboxi: fix 4GB ddr memory detection Baruch Siach
2018-06-07 13:43   ` Fabio Estevam [this message]
2018-06-07 13:42 ` [U-Boot] [PATCH 1/2] mx6cuboxi: consolidate board detection and add som revision checking Fabio Estevam

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=CAOMZO5BFmnN8s+Z2sHqa5WzdWhcQRsYtDsvDuW_wDAWe1L3bmg@mail.gmail.com \
    --to=festevam@gmail.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.