diff options
| author | Aaron Durbin <adurbin@chromium.org> | 2015-07-11 13:36:01 -0500 |
|---|---|---|
| committer | Aaron Durbin <adurbin@chromium.org> | 2015-07-14 22:50:37 +0200 |
| commit | 2a983bd50d072815fc5bdcbb9c55f967b5a6f554 (patch) | |
| tree | 514386df3e41cd6d2b8d617c0b825ef41b3e805b | |
| parent | 31540fb7855a17ac82406f8a42d9a3b8115c12bd (diff) | |
timestamps: clarify in ramstage when not to reinit the cache
Commit bd1499d3 fixed a bug to not re-initialize the timestamp
cache in ramstage for EARLY_CBMEM_INIT. However, EARLY_CBMEM_INIT
was not included. Therefore, add this condition. This will result
in base_time being initialized to the passed in timestamp
for !EARLY_CBMEM_INIT platforms.
Change-Id: Ia1d744b3cfd28163f3339f2364efe59f7dcb719b
Signed-off-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-on: http://review.coreboot.org/10884
Tested-by: build bot (Jenkins)
Reviewed-by: Patrick Georgi <pgeorgi@google.com>
| -rw-r--r-- | src/lib/timestamp.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/lib/timestamp.c b/src/lib/timestamp.c index 7ead3831bb..ca25093423 100644 --- a/src/lib/timestamp.c +++ b/src/lib/timestamp.c @@ -202,7 +202,7 @@ void timestamp_init(uint64_t base) /* In the EARLY_CBMEM_INIT case timestamps could have already been * recovered. In those circumstances honor the cache which sits in BSS * as it has already been initialized. */ - if (ENV_RAMSTAGE && + if (ENV_RAMSTAGE && IS_ENABLED(CONFIG_EARLY_CBMEM_INIT) && ts_cache->cache_state != TIMESTAMP_CACHE_UNINITIALIZED) return; |