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>

1 files changed, 3 insertions, 3 deletions

diff --git a/src/drivers/vpd/vpd.c b/src/drivers/vpd/vpd.c
index 396097c9d9..32ec0a04e3 100644
--- a/src/drivers/vpd/vpd.c
+++ b/src/drivers/vpd/vpd.c
@@ -126,7 +126,7 @@ static void cbmem_add_cros_vpd(int is_recovery)
 {
 	struct vpd_cbmem *cbmem;
 
-	timestamp_add_now(TS_START_COPYVPD);
+	timestamp_add_now(TS_COPYVPD_START);
 
 	init_vpd_rdevs();
 
@@ -154,7 +154,7 @@ static void cbmem_add_cros_vpd(int is_recovery)
 			printk(BIOS_ERR, "Couldn't read RO VPD\n");
 			cbmem->ro_size = ro_size = 0;
 		}
-		timestamp_add_now(TS_END_COPYVPD_RO);
+		timestamp_add_now(TS_COPYVPD_RO_END);
 	}
 
 	if (rw_size) {
@@ -163,7 +163,7 @@ static void cbmem_add_cros_vpd(int is_recovery)
 			printk(BIOS_ERR, "Couldn't read RW VPD\n");
 			cbmem->rw_size = rw_size = 0;
 		}
-		timestamp_add_now(TS_END_COPYVPD_RW);
+		timestamp_add_now(TS_COPYVPD_RW_END);
 	}
 
 	init_vpd_rdevs_from_cbmem();