arm-trusted-firmware/plat/arm/board/tc/tc_dpe.h
Tamas Ban 3201faf356 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
2024-07-03 15:03:20 +02:00

53 lines
2.8 KiB
C

/*
* Copyright (c) 2024, Arm Limited. All rights reserved.
*
* SPDX-License-Identifier: BSD-3-Clause
*/
#ifndef TC_DPE_H
#define TC_DPE_H
/*
* The certificate structure on the TC platform:
* - The arrows indicate the parent/child relationships (who loads who).
* - The boxes indicate the certificates.
*
* AP FW Cert.
* +--------------------------------+
* | |
* Plat Cert. | +->SPx | Hyper Cert.
* +--------------------------+ | +->SP1 | +--------------------+
* RoT Cert. | | | +->TOS_FW_CONF | | |
* +------------+ | +->SCP_BL1 +-----+-----+-->FW_CONF +->AP_BL32 | | +->PVMFW |
* | | | | | | | | | | | |
* | RSE_BL1_2--+-----+-->RSE_BL2------->AP_BL1--+-----+------------->AP_BL2------------+-----+-->AP_BL33 |
* | | | | | | | | | | | |
* +------------+ | +->RSE_S +-----+-----+-->TB_FW_CONF +->AP_BL31 | | +->HYPERVISOR |
* | +->RSE_NS | | +->SCP_BL2 | | |
* | | | +->HW_CONF | | |
* +--------------------------+ | +---------------+-----+-->NT_FW_CONF |
* | | | |
* +--------------------------------+ +--------------------+
*/
#define DPE_AP_FW_CERT_ID 0x300 /* Includes: FW_CONF - SP1 */
#define DPE_HYPERVISOR_CERT_ID 0x400 /* Includes: AP_BL33 - PVMFW */
/* Common definition */
#define DPE_CERT_ID_SAME_AS_PARENT 0xFFFFFFFF
/*
* Target Locality:
* The goal is to specify that a certain component is expected to run and
* thereby send DPE commands from a given security domain. RSE is capable of
* of distinguishing the client's locality based on the MHU channel used for
* communication.
* Defines here must match with RSE side:
*/
#define LOCALITY_NONE -1
/* #define LOCALITY_RSE_S 0 */ /* Not applicable on AP side */
/* #define LOCALITY_RSE_NS 1 */ /* Not applicable on AP side */
#define LOCALITY_AP_S 2
#define LOCALITY_AP_NS 3
#endif /* TC_DPE_H */