summaryrefslogtreecommitdiff
path: root/src/vboot
diff options
context:
space:
mode:
authorFurquan Shaikh <furquan@chromium.org>2017-01-26 15:33:01 -0800
committerMartin Roth <martinroth@google.com>2017-01-30 17:45:36 +0100
commit775765eaf30a6e3cef6e49f4119967a09841c214 (patch)
treeb5e2874d2d47fac4209ce8f9a00ee8626b931c92 /src/vboot
parentf8ab456a6328fa2a8f592d6ec7185015305c75ea (diff)
vboot: Add mock functions for recovery space read/write
For the boards that intend to use mock tpm and have recovery mrc cache support enabled, provide mock functions to read and write mrc hash space. Reading MRC hash space returns TPM_SUCCESS as later checks take care of comparing the hash value and retraining if hash comparison fails. Thus, in case of mock tpm, device would always end up doing the memory retraining in recovery mode. BUG=chrome-os-partner:62413 BRANCH=None TEST=Verified that eve builds with mock tpm selected. Change-Id: I7817cda7821fadeea0e887cb9860804256dabfd9 Signed-off-by: Furquan Shaikh <furquan@chromium.org> Reviewed-on: https://review.coreboot.org/18248 Tested-by: build bot (Jenkins) Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
Diffstat (limited to 'src/vboot')
-rw-r--r--src/vboot/secdata_mock.c10
1 files changed, 10 insertions, 0 deletions
diff --git a/src/vboot/secdata_mock.c b/src/vboot/secdata_mock.c
index 9c966d9bbd..31fa5980c4 100644
--- a/src/vboot/secdata_mock.c
+++ b/src/vboot/secdata_mock.c
@@ -41,3 +41,13 @@ uint32_t antirollback_lock_space_rec_hash(void)
{
return TPM_SUCCESS;
}
+
+uint32_t antirollback_read_space_rec_hash(uint8_t *data, uint32_t size)
+{
+ return TPM_SUCCESS;
+}
+
+uint32_t antirollback_write_space_rec_hash(const uint8_t *data, uint32_t size)
+{
+ return TPM_SUCCESS;
+}