[U-Boot] [PATCH] keystone2: use detected ddr3a size

[Tom Rini <trini@konsulko.com>]

On Mon, Jun 15, 2015 at 08:48:01AM -0400, Vitaly Andrianov wrote:

> KS2 u-boot detects the ddr3a size installed to EVM. The detected size can
> be used instead of environment variable. Because the ddr3 configuration is
> done before relocation we cannot use a global variable to pass the
> ddr3_size to ft_board_setup(). Instead we have to use the global data
> structure.
> 
> Because KS2 u-boot works in 32 bit address space the existing ram_size
> global data filed cannot be used. The maximum, which the get_ram_size()
> can detect is 2GB only. This patch creates the ddr3_size filed in the
> arch_global_data structure, which is used for that purpose.
> 
> Signed-off-by: Vitaly Andrianov <vitalya@ti.com>

So we've got a few possibilities here, yes?  Since we have the ability
to change the DDR modules on the board and read the sizes in the SPD
information U-Boot is the place where the board can find out if we have
say 1GB or 2GB of memory and thus has to be the one to correctly
populate the device tree.  So the "fix" that we're talking about for
Calxeda can't be applied here.

But this also brings up http://patchwork.ozlabs.org/patch/281094/ (and
the follow-up of http://patchwork.ozlabs.org/patch/291219/ and
http://patchwork.ozlabs.org/patch/291247/) where no, we have a problem
that we need to fix.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150615/611e746c/attachment.sig>