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
@ -62,14 +62,14 @@ static bool extract(struct region *region, struct fit_image_node *node)
|
||||
true_size = node->size;
|
||||
break;
|
||||
case CBFS_COMPRESS_LZMA:
|
||||
timestamp_add_now(TS_START_ULZMA);
|
||||
timestamp_add_now(TS_ULZMA_START);
|
||||
true_size = ulzman(node->data, node->size, dst, region->size);
|
||||
timestamp_add_now(TS_END_ULZMA);
|
||||
timestamp_add_now(TS_ULZMA_END);
|
||||
break;
|
||||
case CBFS_COMPRESS_LZ4:
|
||||
timestamp_add_now(TS_START_ULZ4F);
|
||||
timestamp_add_now(TS_ULZ4F_START);
|
||||
true_size = ulz4fn(node->data, node->size, dst, region->size);
|
||||
timestamp_add_now(TS_END_ULZ4F);
|
||||
timestamp_add_now(TS_ULZ4F_END);
|
||||
break;
|
||||
default:
|
||||
return true;
|
||||
@ -240,5 +240,5 @@ void fit_payload(struct prog *payload, void *data)
|
||||
return;
|
||||
}
|
||||
|
||||
timestamp_add_now(TS_START_KERNEL);
|
||||
timestamp_add_now(TS_KERNEL_START);
|
||||
}
|
||||
|
Reference in New Issue
Block a user