summaryrefslogtreecommitdiff
path: root/src/lib
diff options
context:
space:
mode:
authorAaron Durbin <adurbin@chromium.org>2015-09-23 19:54:12 -0500
committerAaron Durbin <adurbin@chromium.org>2015-09-24 16:12:44 +0000
commit9796f60c62f57ac512f225809c10b5b09ef80f5a (patch)
tree5d6c3e1d933782bbb03af4ac7a21579f722b5327 /src/lib
parenta40032780fe4da7d95b203fb3d05a25183590952 (diff)
downloadcoreboot-9796f60c62f57ac512f225809c10b5b09ef80f5a.tar.xz
coreboot: move TS_END_ROMSTAGE to one spot
While the romstage code flow is not consistent across all mainboards/chipsets there is only one way of running ramstage from romstage -- run_ramstage(). Move the timestamp_add_now(TS_END_ROMSTAGE) to be within run_ramstage(). BUG=chrome-os-partner:44827 BRANCH=None TEST=Built and booted glados. TS_END_ROMSTAGE still present in timestamp table. Change-Id: I4b584e274ce2107e83ca6425491fdc71a138e82c Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: http://review.coreboot.org/11700 Tested-by: build bot (Jenkins) Reviewed-by: Patrick Georgi <pgeorgi@google.com>
Diffstat (limited to 'src/lib')
-rw-r--r--src/lib/prog_loaders.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/lib/prog_loaders.c b/src/lib/prog_loaders.c
index 2f4a2c118a..e53fca5c0c 100644
--- a/src/lib/prog_loaders.c
+++ b/src/lib/prog_loaders.c
@@ -96,6 +96,8 @@ void run_ramstage(void)
struct prog ramstage =
PROG_INIT(ASSET_RAMSTAGE, CONFIG_CBFS_PREFIX "/ramstage");
+ timestamp_add_now(TS_END_ROMSTAGE);
+
/* Only x86 systems currently take the same firmware path on resume. */
if (IS_ENABLED(CONFIG_ARCH_X86) && IS_ENABLED(CONFIG_EARLY_CBMEM_INIT))
run_ramstage_from_resume(romstage_handoff_find_or_add(),