Searched hist:b1042535dc3ecf287d5d18a8a7f79eebad60b395 (Results 1 – 2 of 2) sorted by relevance
| /optee_os/core/include/tee/ |
| H A D | tee_fs.h | b1042535dc3ecf287d5d18a8a7f79eebad60b395 Fri Nov 29 16:40:58 UTC 2019 Rouven Czerwinski <r.czerwinski@pengutronix.de> rpmb: function to block rpmb write per platform
Often the RPMB should only be written if the platform is in the correct
state where the Hardware Unique Key (HUK) for the platform works
correctly. As an example on imx platforms with HUK derivation from the
OTPMK, the OTPMK is only accessible from the secure or trusted state.
Add a function and weak implementation for platforms to indicate that
the device is in the correct state to allow RPMB key writes.
Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
Reviewed-by: Cedric Neveux <cedric.neveux@nxp.com>
|
| /optee_os/core/tee/ |
| H A D | tee_rpmb_fs.c | b1042535dc3ecf287d5d18a8a7f79eebad60b395 Fri Nov 29 16:40:58 UTC 2019 Rouven Czerwinski <r.czerwinski@pengutronix.de> rpmb: function to block rpmb write per platform
Often the RPMB should only be written if the platform is in the correct
state where the Hardware Unique Key (HUK) for the platform works
correctly. As an example on imx platforms with HUK derivation from the
OTPMK, the OTPMK is only accessible from the secure or trusted state.
Add a function and weak implementation for platforms to indicate that
the device is in the correct state to allow RPMB key writes.
Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
Reviewed-by: Cedric Neveux <cedric.neveux@nxp.com>
|