timestamps: Rename timestamps to make names more consistent
This patch aims to make timestamps more consistent in naming, to follow one pattern. Until now there were many naming patterns: - TS_START_*/TS_END_* - TS_BEFORE_*/TS_AFTER_* - TS_*_START/TS_*_END This change also aims to indicate, that these timestamps can be used to create time-ranges, e.g. from TS_BOOTBLOCK_START to TS_BOOTBLOCK_END. Signed-off-by: Jakub Czapiga <jacz@semihalf.com> Change-Id: I533e32392224d9b67c37e6a67987b09bf1cf51c6 Reviewed-on: https://review.coreboot.org/c/coreboot/+/62019 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Tim Wawrzynczak <twawrzynczak@chromium.org> Reviewed-by: Yu-Ping Wu <yupingso@google.com> Reviewed-by: Raul Rangel <rrangel@chromium.org>
This commit is contained in:
committed by
Felix Held
parent
e96ade6981
commit
ad6157ebdf
@@ -166,7 +166,7 @@ int intel_early_me_init_done(u8 status)
|
||||
"ME: ME is reporting as disabled, "
|
||||
"so not waiting for a response.\n");
|
||||
} else {
|
||||
timestamp_add_now(TS_ME_INFORM_DRAM_WAIT);
|
||||
timestamp_add_now(TS_ME_INFORM_DRAM_START);
|
||||
udelay(100);
|
||||
millisec = 0;
|
||||
do {
|
||||
@@ -177,7 +177,7 @@ int intel_early_me_init_done(u8 status)
|
||||
millisec++;
|
||||
} while ((((hfs & 0xf0) >> 4) != ME_HFS_BIOS_DRAM_ACK)
|
||||
&& (millisec <= 5000));
|
||||
timestamp_add_now(TS_ME_INFORM_DRAM_DONE);
|
||||
timestamp_add_now(TS_ME_INFORM_DRAM_END);
|
||||
}
|
||||
|
||||
me_fws2 = pci_read_config32(PCH_ME_DEV, PCI_ME_GMES);
|
||||
|
Reference in New Issue
Block a user