diff options
author | Jens Wiklander <[email protected]> | 2024-08-14 17:35:55 +0200 |
---|---|---|
committer | Ulf Hansson <[email protected]> | 2024-08-26 13:16:20 +0200 |
commit | 1e9046e3a154608f63ce79edcb01e6afd6b10c7c (patch) | |
tree | d28d75fe3fe337b158531e2b2930bf1231cedd78 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | 0579ac48d30f8bea0c83e92fd508efc879bbe96e (diff) |
rpmb: add Replay Protected Memory Block (RPMB) subsystem
A number of storage technologies support a specialised hardware
partition designed to be resistant to replay attacks. The underlying
HW protocols differ but the operations are common. The RPMB partition
cannot be accessed via standard block layer, but by a set of specific
RPMB commands. Such a partition provides authenticated and replay
protected access, hence suitable as a secure storage.
The initial aim of this patch is to provide a simple RPMB driver
interface which can be accessed by the optee driver to facilitate early
RPMB access to OP-TEE OS (secure OS) during the boot time.
A TEE device driver can claim the RPMB interface, for example, via
rpmb_interface_register() or rpmb_dev_find_device(). The RPMB driver
provides a callback to route RPMB frames to the RPMB device accessible
via rpmb_route_frames().
The detailed operation of implementing the access is left to the TEE
device driver itself.
Signed-off-by: Tomas Winkler <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Signed-off-by: Shyam Saini <[email protected]>
Signed-off-by: Jens Wiklander <[email protected]>
Reviewed-by: Linus Walleij <[email protected]>
Tested-by: Manuel Traut <[email protected]>
Reviewed-by: Ulf Hansson <[email protected]>
Reviewed-by: Greg Kroah-Hartman <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Ulf Hansson <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions