summaryrefslogtreecommitdiff
path: root/include/tpm_vendor_cmds.h
diff options
context:
space:
mode:
authorVadim Bendebury <vbendeb@chromium.org>2016-12-27 10:19:40 -0800
committerchrome-bot <chrome-bot@chromium.org>2017-01-05 23:47:07 -0800
commit02c5bb8392545f99b609943dfe1d92d9f2ffa4ae (patch)
tree19d43da4f0e9b7f52118193c124f73139e7f7287 /include/tpm_vendor_cmds.h
parent5659d103a669ada5fd173f7b801ed7b0a1066881 (diff)
downloadchrome-ec-02c5bb8392545f99b609943dfe1d92d9f2ffa4ae.tar.gz
cr50: vendor command to enable nvmem commits
TPM NVMEM commits are reenabled as soon as the system boots into Chrome OS. However, sometimes the device does not boot into Chrome OS, in which case it is necessary to be able to reinstate NVMEM commits explicitly. The new vendor command will provide this functionality. BRANCH=none BUG=chrome-os-partner:59873 TEST=added code to depthcharge to issue the new vendor command if the system falls into recovery mode, verify that commits are re-instated once the command is issued. Change-Id: I3c06b27175751dc2c095911441935eee62ed9c50 Reviewed-on: https://chromium-review.googlesource.com/424064 Commit-Ready: Vadim Bendebury <vbendeb@chromium.org> Tested-by: Vadim Bendebury <vbendeb@chromium.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Diffstat (limited to 'include/tpm_vendor_cmds.h')
-rw-r--r--include/tpm_vendor_cmds.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/tpm_vendor_cmds.h b/include/tpm_vendor_cmds.h
index 4e49455369..f81abf70d0 100644
--- a/include/tpm_vendor_cmds.h
+++ b/include/tpm_vendor_cmds.h
@@ -32,6 +32,7 @@ enum vendor_cmd_cc {
VENDOR_CC_SYSINFO = 18,
VENDOR_CC_IMMEDIATE_RESET = 19,
VENDOR_CC_INVALIDATE_INACTIVE_RW = 20,
+ VENDOR_CC_COMMIT_NVMEM = 21,
LAST_VENDOR_COMMAND = 65535,
};