summaryrefslogtreecommitdiff
path: root/Android.mk
diff options
context:
space:
mode:
authorAndrey Pronin <apronin@chromium.org>2018-03-22 17:45:20 -0700
committerchrome-bot <chrome-bot@chromium.org>2018-03-27 14:58:10 -0700
commit3ee5c7d8adf5d78d6864c73bf4f33b95f04a7979 (patch)
tree0b6506791bb56bcae5f99a4c90ce0b50209cca9f /Android.mk
parentd3ec8f8116b167f58d76f0c798ae1b4d14aec389 (diff)
downloadvboot-3ee5c7d8adf5d78d6864c73bf4f33b95f04a7979.tar.gz
firmware: tpm2_lite: propagate actual errors
Propagate the actual error - a non-successful response code from the tpm or communication/serializing failure - to the caller of the Tlcl functions in TPM 2.0 case. Currently, the callers only have special processing for the error codes from TCG TPM 1.2 range, which are never returned in case of communication or serialization failures or from the actual TPM 2.0. (The only case of mapping TPM 2.0 error codes to TPM_E_BADINDEX is preserved in this CL.) Thus, changing the actual values returned from the functions won't change any current behavior in the calling layers. This CL is a preparatory work for adding special processing for communication errors in mount-encrypted. BUG=chromium:702724 BRANCH=none TEST=build; test that tpmc getvf, tpmc read still work. Change-Id: I96b20e7285e83f0038abc01e4b7175c938867e7d Signed-off-by: Andrey Pronin <apronin@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/977225 Reviewed-by: Vadim Bendebury <vbendeb@chromium.org>
Diffstat (limited to 'Android.mk')
0 files changed, 0 insertions, 0 deletions