avb: add support for named persistent values

AVB 2.0 spec. revision 1.1 introduces support for named persistent values
that must be tamper evident and allows AVB to store arbitrary key-value
pairs [1].

Introduce implementation of two additional AVB operations
read_persistent_value()/write_persistent_value() for retrieving/storing
named persistent values.

Correspondent pull request in the OP-TEE OS project repo [2].

[1]: https://android.googlesource.com/platform/external/avb/+/android-9.0.0_r22
[2]: https://github.com/OP-TEE/optee_os/pull/2699

Reviewed-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Sam Protsenko <semen.protsenko@linaro.org>
Signed-off-by: Igor Opaniuk <igor.opaniuk@gmail.com>
This commit is contained in:
Igor Opaniuk
2019-04-09 15:38:14 +02:00
committed by Tom Rini
parent b85d155199
commit fc1fe01b08
7 changed files with 351 additions and 22 deletions

View File

@@ -45,4 +45,20 @@
*/
#define TA_AVB_CMD_WRITE_LOCK_STATE 3
/*
* Reads a persistent value corresponding to the given name.
*
* in params[0].u.memref: persistent value name
* out params[1].u.memref: read persistent value buffer
*/
#define TA_AVB_CMD_READ_PERSIST_VALUE 4
/*
* Writes a persistent value corresponding to the given name.
*
* in params[0].u.memref: persistent value name
* in params[1].u.memref: persistent value buffer to write
*/
#define TA_AVB_CMD_WRITE_PERSIST_VALUE 5
#endif /* __TA_AVB_H */