summaryrefslogtreecommitdiff
path: root/src/soc/nvidia/tegra124/cbmem.c
diff options
context:
space:
mode:
authorAaron Durbin <adurbin@chromium.org>2014-08-08 13:23:22 -0500
committerPatrick Georgi <pgeorgi@google.com>2015-03-27 08:03:15 +0100
commit2152e85e12413532f2c5d4281267c0a5f604211c (patch)
tree28d5f67bd352ffd934589cf365b6a5ec223f3f71 /src/soc/nvidia/tegra124/cbmem.c
parent9ecafd967c4232b9b38dda9ce663bb33777a2828 (diff)
tegra132: never recover cbmem from romstage
Tegra132 has 2 different paths for booting and resuming from sleep. The boot path uses the typical bootblock, romstage, and ramstage. However, the resume path is completely orthogonal. cbmem_initialize() attempts to recover the cbmem area, but that functionality should not be used from romstage because tegra132 is by definition in a fresh boot if it is executing romstage. Therefore, use cbmem_initialize_empty() so that cbmem is always initialized from scratch on each boot. BUG=chrome-os-partner:31239 BRANCH=None TEST=Built and ran on ryu. Was able to enter recovery and stay in recovery without entering a reboot loop. Change-Id: I0453c15e57a873a7ce7a63190dceafb75e4c9342 Signed-off-by: Patrick Georgi <pgeorgi@chromium.org> Original-Commit-Id: 28ebc092e6721552c18db03e7578424c23a64b64 Original-Change-Id: I2016146fdc3aea493a78bab31ea8c8cbd78935c5 Original-Signed-off-by: Aaron Durbin <adurbin@chromium.org> Original-Reviewed-on: https://chromium-review.googlesource.com/211424 Original-Reviewed-by: Furquan Shaikh <furquan@chromium.org> Reviewed-on: http://review.coreboot.org/8990 Tested-by: build bot (Jenkins) Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
Diffstat (limited to 'src/soc/nvidia/tegra124/cbmem.c')
0 files changed, 0 insertions, 0 deletions