History log of /rk3399_ARM-atf/plat/arm/board/tc/tc_dpe.h (Results 1 – 3 of 3)
Revision Date Author Comments
# a5b97052 05-Jul-2024 Manish V Badarkhe <manish.badarkhe@arm.com>

Merge changes from topic "dpe_target_locality" into integration

* changes:
feat(tc): provide target_locality info of AP FW components
refactor(tc): rename DPE header


# 3201faf3 14-Jun-2024 Tamas Ban <tamas.ban@arm.com>

feat(tc): provide target_locality info of AP FW components

The target_locality attribute is meant to specify that
a certain SW component is expected to run and thereby
send DPE commands from a given

feat(tc): provide target_locality info of AP FW components

The target_locality attribute is meant to specify that
a certain SW component is expected to run and thereby
send DPE commands from a given security domain. The DPE
service must be capable of determining the locality of
a client on his own. RSE determines the client's locality
based on the MHU channel used for communication.

If the expected locality (specified by the parent component)
is not matching with the determined locality by DPE
service then command fails.

The goal is to protect against spoofing when a
context_handle is stolen and used by a component
that should not have access.

Signed-off-by: Tamas Ban <tamas.ban@arm.com>
Change-Id: I96d255de231611cfed10eef4335a47b91c2c94de

show more ...


# 4f5beb56 14-Jun-2024 Tamas Ban <tamas.ban@arm.com>

refactor(tc): rename DPE header

The new name is more generic. The goal to add here
all platform dependent defines / data / config which
is DPE related.

Signed-off-by: Tamas Ban <tamas.ban@arm.com>

refactor(tc): rename DPE header

The new name is more generic. The goal to add here
all platform dependent defines / data / config which
is DPE related.

Signed-off-by: Tamas Ban <tamas.ban@arm.com>
Change-Id: I5b521932c45d8a9c43ea2344dde83c210801cfee

show more ...