Skip to content
Snippets Groups Projects
Select Git revision
  • v2020.01-ktn
  • caam_hab_mx8m
  • pmic_pca9450
  • feature_swupdate
  • wip_swupdate_env
  • master default protected
  • v2020.01-rc1
  • v2019.10
  • v2019.10-rc4
  • v2019.10-rc3
  • v2019.10-rc2
  • v2019.10-rc1
  • v2019.07
  • v2019.07-rc4
  • v2019.07-rc3
  • v2019.07-rc2
  • v2019.07-rc1
  • v2019.04
  • v2019.04-rc4
  • v2019.04-rc3
  • v2019.04-rc2
  • v2019.04-rc1
  • v2019.01
  • v2019.01-rc3
  • v2019.01-rc2
  • v2019.01-rc1
26 results
Search by author
  • Any Author
  • Florian Mayer Florian Mayer fmayer
1 author
  1. Mar 04, 2015
    • Stephen Warren's avatar
      ARM: tegra: move common config defines centrally · 026baff7
      Stephen Warren authored 
      
All boards need CONFIG_BOARD_EARLY_INIT_F, and many actively need
CONFIG_BOARD_LATE_INIT. Move both of these into tegra-common.h so that
board config headers don't need to repeatedly define them.

Later commits will add new code in board_late_init() which applies to
all boards, so CONFIG_BOARD_LATE_INIT should be enabled for all Tegra
boards.

Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
Signed-off-by: default avatarTom Warren <twarren@nvidia.com>
      026baff7
    • Stephen Warren's avatar
      ARM: tegra: support large RAM sizes · 56519c4f
      Stephen Warren authored 
      
Some systems have so much RAM that the end of RAM is beyond 4GB. An
example would be a Tegra124 system (where RAM starts at 2GB physical)
that has more than 2GB of RAM.

In this case, we want gd->ram_size to represent the actual RAM size, so
that the actual RAM size is passed to the OS. This is useful if the OS
implements LPAE, and can actually use the "extra" RAM.

However, we can't use get_ram_size() to verify the actual amount of RAM
present on such systems, since some of the RAM can't be accesses, which
confuses that function. Avoid calling get_ram_size() when the RAM size
is too large for it to work correctly. It's never actually needed anyway,
since there's no reason for the BCT to report the wrong RAM size.

In systems with >=4GB RAM, we still need to clip the reported RAM size
since U-Boot uses a 32-bit variable to represent the RAM size in bytes.

Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
Signed-off-by: default avatarTom Warren <twarren@nvidia.com>
      56519c4f
    • Stephen Warren's avatar
      ARM: tegra: fix variable naming in query_sdram_size() · 3a2cab51
      Stephen Warren authored 
      
size_mb is used to hold a value that's sometimes KB, sometimes MB,
and sometimes bytes. Use separate correctly named variables to avoid
confusion here. Also fix indentation of a conditional statement.

Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
Signed-off-by: default avatarTom Warren <twarren@nvidia.com>
      3a2cab51
    • Stephen Warren's avatar
      common: board: support systems with where RAM ends beyond 4GB · 1e4d11a5
      Stephen Warren authored 
      
Some systems have so much RAM that the end of RAM is beyond 4GB. An
example would be a Tegra124 system (where RAM starts at 2GB physical)
that has more than 2GB of RAM.

In this case, we can gd->ram_size to represent the actual RAM size, so
that the actual RAM size is passed to the OS. This is useful if the OS
implements LPAE, and can actually use the "extra" RAM.

However, U-Boot does not implement LPAE and so must deal with 32-bit
physical addresses. To this end, we enhance board_get_usable_ram_top() to
detect the "over-sized" case, and limit the relocation addres so that it
fits into 32-bits of physical address space.

Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
Signed-off-by: default avatarTom Warren <twarren@nvidia.com>
      1e4d11a5
  3. Mar 01, 2015
  5. Feb 25, 2015
  7. Feb 24, 2015
  9. Feb 23, 2015
  11. Feb 22, 2015
  13. Feb 21, 2015